{"id":3493,"date":"2023-04-03T14:04:19","date_gmt":"2023-04-03T13:04:19","guid":{"rendered":"https:\/\/pmortensen.eu\/world2\/?p=3493"},"modified":"2023-04-21T13:34:19","modified_gmt":"2023-04-21T12:34:19","slug":"integration-of-edit-overflow-into-geany","status":"publish","type":"post","link":"https:\/\/pmortensen.eu\/world2\/2023\/04\/03\/integration-of-edit-overflow-into-geany\/","title":{"rendered":"Integration of Edit Overflow into Geany"},"content":{"rendered":"

Using Edit Overflow<\/a> directly from Geany<\/a> has turned out to be surprisingly useful. If one is unsure about the spelling of a word, select it and press Ctrl<\/em> + 2<\/em>. The word will either 1) Be unchanged (the spelling is correct). 2) Be changed (the spelling is incorrect) 3) Have appended “@!$”<\/em> (Edit Overflow doesn’t have it in its word list).<\/p>\n

This avoids the overhead of using the web interface<\/a> (even if automated by a macro keyboard as there is still the very significant delay). Though the context that the associated URL provides is absent.<\/p>\n

It can also be used for shorthands which are then expanded by Edit Overflow, for example, with a difficult spelling and\/or a long word. Example: Expanding “vulns<\/a>“<\/em> to “vulnerabilities”<\/em>. Text templates can be used for the same purpose, but Edit Overflow has a lot more words<\/a>.<\/p>\n

Installation<\/h2>\n

At the moment, Edit Overflow first needs to be build\/compiled on the system where you want to use it. Set up Geany to invoke Edit Overflow through its command line interface with the text selection in a Geany document, and have a script make the necessary conversions to and from Edit Overflow, similar to the ‘sort’ section<\/a> in the Geany blog post<\/a>.<\/p>\n

Use this Perl one-liner on Linux:<\/p>\n

\r\nperl -e 'while (<>) { my $out = $_; $exe = "\\\/home\\\/mortensen\\\/temp2\\\/2022-03-01\\\/_DotNET_tryout\\\/EditOverflow4\\\/bin\\\/Debug\\\/netcoreapp3.1\\\/EditOverflow3"; my $regExtr = "Corrected word for .+\\\\: (.+)"; my $output = qx\/export LOOKUP=\\"$_\\"; $exe \/; if ($output =~ \/$regExtr\/) { $out = $1; } else { my $output2 = qx\/export LOOKUP=\\"$_\\_\\"; $exe \/; if ($output2 =~ \/$regExtr\/) { $out = $1; } else {$out .= "@!\\$"; } } print "$out"; }'\r\n<\/pre>\n
Configure the $exe part. The path to the Edit Overflow executable probably needs to be changed from the default “\/home\/mortensen\/temp2\/2022-03-01\/_DotNET_tryout\/EditOverflow4\/bin\/Debug\/netcoreapp3.1\/EditOverflow3”<\/em> (this is for a particular build folder location).<\/p>\n
Add it to menu “Edit”<\/em> → “Format”<\/em> → “Send Selection to”<\/em> → “Format”<\/em> → “Set Custom Commands”<\/em>. If it becomes the second item, then Ctrl + 2 will perform the Edit Overflow correction of the selection in a Geany document.<\/p>\n
How does it work?<\/h2>\n
Edit Overflow has a command-line interface. For example, it can export the word list in various formats. And looking up a word in the word list is also supported. The word to be corrected is taken as the environment variable “LOOKUP” (not a command-line parameter; this is in order to avoid the complications with escaping spaces and escaping various special characters). For example, this will look up the misspelling “Javascript”:<\/p>\n
\r\nexport LOOKUP=Javascript\r\n.\/EditOverflow3\r\n<\/pre>\n
where EditOverflow3<\/em> is the name of the Edit Overflow executable and the current directory is where EditOverflow3<\/em> is.<\/p>\n
Thus the script must first take the input from standard input and set up the environment variable “LOOKUP”.<\/p>\n
Output:<\/p>\n
\r\nCorrected word for Javascript: JavaScript\r\n<\/pre>\n
After execution of Edit Overflow, the Perl script extracts the corrected word from that output (Edit Overflow’s output to standard output) by using the regular expression:<\/p>\n
\r\nCorrected word for .+\\\\: (.+)\r\n<\/pre>\n
The Perl script only passes the correct word (“JavaScript” in this example) onto Geany (through the Perl script’s output to standard output); the Perl script acts like a filtering layer, so we get the desired result.<\/p>\n","protected":false},"excerpt":{"rendered":"
Using Edit Overflow directly from Geany has turned out to be surprisingly useful. If one is unsure about the spelling of a word, select it and press Ctrl + 2. The word will either 1) Be unchanged (the spelling is correct). …<\/p>\n
  Integration of Edit Overflow into Geany<\/span> Read More »<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[17,14,18],"tags":[],"_links":{"self":[{"href":"https:\/\/pmortensen.eu\/world2\/wp-json\/wp\/v2\/posts\/3493"}],"collection":[{"href":"https:\/\/pmortensen.eu\/world2\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pmortensen.eu\/world2\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pmortensen.eu\/world2\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/pmortensen.eu\/world2\/wp-json\/wp\/v2\/comments?post=3493"}],"version-history":[{"count":55,"href":"https:\/\/pmortensen.eu\/world2\/wp-json\/wp\/v2\/posts\/3493\/revisions"}],"predecessor-version":[{"id":3616,"href":"https:\/\/pmortensen.eu\/world2\/wp-json\/wp\/v2\/posts\/3493\/revisions\/3616"}],"wp:attachment":[{"href":"https:\/\/pmortensen.eu\/world2\/wp-json\/wp\/v2\/media?parent=3493"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pmortensen.eu\/world2\/wp-json\/wp\/v2\/categories?post=3493"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pmortensen.eu\/world2\/wp-json\/wp\/v2\/tags?post=3493"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}