Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
My apologies for failing to realize that some are a little too thin-skinned to handle blunt criticism without clutching pearls, pooping pants and then censoring my post. I will endeavor to not make such a mistake again.
First off, I write code. The is nothing about some contrived distinction of a so-called "code editor" versus a "text editor." If it's ASCII, it's text. Like other coders, I often use a text editor, NEVER a "code editor."
Sometimes I might want to edit, say, a minified HTML file (no carriage returns). Such files are best worked on using Wrap. Sometimes I want to select text from the cursor at, say, Line 2783 and Column 37 to the end of the same line ...or maybe to somewhere near the end of, say, Line 2793, ten lines below (and maybe that means 2,000 characters). Unlike practically every single GUI text editing tool or container, and unlike major text editing tools specifically for writing code (Eclipse, UltraEdit, Sublime, ColdFusion Builder, Visual Studio, et al), Geany strives to be different for reasons known only to those who apparently confine themselves to their own tiny pond and ignoring the nearly universal conventions shared by the overwhelming majority of text/code editors.
That said, I certainly do not begrudge anyone who wants to indulge ones own specialness and create a text editor as unique their "use cases." But (and call me presumptuous) it seems that even then a goal of any tool is to be used by as many as possible and that the goal certainly is not to alienate and frustrate those who merely ask to make it an option metaphorically for Green to mean Go, "+" to denote Positive, or a trashcan icon to mean Delete.
Some say that a user like me can use key bindings to configure the desired [super conventional] behavior. They are wrong ...or I am wrong. If I am wrong, then please explain precisely how Geany can be configured to achieve the desired end of selecting text from the cursor's position to the end or beginning of the current line and NOT to the previous carriage return (or beginning of file) or to the next carriage return (or end of file).
All I ask is for the option to make the tool behave in a way predictable and expected according to the convention used nearly universally by the overwhelming majority of other text/code editors ...without clutching pearls, censoring comments and blaming the frustrated user for not being as special and unique.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.