Moe editor

Moe editor
gnu.org/software/moe/

Attached: 76FEE2D8-8EC9-4384-B065-C7D37D524FCE.png (300x400, 55K)

Other urls found in this thread:

khmix.sakura.ne.jp/
twitter.com/NSFWRedditVideo

Introduction

GNU moe is a powerful, 8-bit clean, console text editor for ISO-8859 and ASCII character encodings. It has a modeless, user-friendly interface, online help, multiple windows, unlimited undo/redo capability, unlimited line length, unlimited buffers, global search/replace (on all buffers at once), block operations, automatic indentation, word wrapping, file name completion, directory browser, duplicate removal from prompt histories, delimiter matching, text conversion from/to UTF-8, romanization, etc.

Moe can easily edit thousands of files at the same time.

>modeless
Vimlets BTFO

Attached: 1553629337460.gif (540x540, 279K)

How does it compare to emacs

>modeless
dropped

So many derivatives of the word "manlet" don't make sense. "Manlet" means a smaller or lesser man. When you say "vimlet", logically it means "someone who is less of a Vim user". It's an insult somebody who uses Vim would throw at a more primitive Vim user or a non-user. But, inasmuch as you are trying to say anything, you clearly aren't trying to say that. Your primitive mind has only managed to capture a degraded pattern: use the suffix -let to turn a word into an insult. That's it. All other meaning is lost. Your brain's language center is like a 30% JPEG. Who are even the ``people'' who perpetrate this abuse of the language? They don't seem to understand how new words work. Koko knew better than you, and she wasn't even the same species.

cope

Attached: 1563612603026[1].jpg (960x1280, 136K)

seethe

true
wish these retards would go back to discord and never come to this site again

>Moe uses ISO-8859-15 instead of UTF-8 because an 8-bit character set (combined with romanization if needed) can convey meaning safely and more efficiently than UTF-8 can.

>UTF-8 is a great tool for tasks like writing books of mathematics or mixing Greek with Chinese in the same document. But for many other everyday computing and communication tasks, an 8-bit code like ISO-8859-15 is much more practical, efficient and reliable. There is no such thing as an "invalid" or "out of range" ISO-8859-15 character.

>UTF-8 is fine for non-parsable, non-searchable documents that must look "pretty", but not so fine for things like filenames, configuration files or C++ source code. Invalid UTF-8 characters in filenames make archiving and filesystem operations unreliable. UTF-8 greatly hinders parsability (and may even become a security risk) by providing multiple similar-looking variations of basic alphabetic, punctuation, and quoting characters. UTF-8 also makes search difficult and unreliable. For example, searching for a word like "file" in an UTF-8 document may fail if the document uses the compound character 'fi' instead of the string "fi".
Very based