|
Mr Dog posted:vim is ok but it's kinda buggy and apparently the code is a horror show can't be worse than the original vi, which was a bunch of screen editor hacks atop ex (a la teco and emacs), which was a bunch of local hacks atop ed
|
# ? Mar 9, 2016 09:01 |
|
|
# ? Jun 4, 2024 15:56 |
|
Wheany posted:Has anyone made a linux text editor that works normally, ie ctrl-s is save, ctrl-c is copy, ctrl-v is paste, ctrl-z is undo and so on? pico and nano have kind of tried to be that, except pico uses a bunch of DEC TOPS-20 conventions instead of modern (Macintosh) conventions and nano is a version of pico infected with GNU like huitlacoche eschaton fucked around with this message at 09:06 on Mar 9, 2016 |
# ? Mar 9, 2016 09:04 |
|
eschaton posted:pico and nano have kind of tried to be that, except pico uses a bunch of DEC TOPS-20 conventions instead of modern (Macintosh) conventions and nano is a version of pico infected with GNU like huitlacoche ctrl-o ctrl-x ugh jpico is some sort of even more hosed up pico and if some idiot has set it to the default the key commands change when something like git calls it
|
# ? Mar 9, 2016 09:06 |
|
Notorious b.s.d. posted:ed is useful in shell scripts there are approximately 0 situations where it is appropriate to edit a file using a shell script ityool 2016
|
# ? Mar 9, 2016 09:25 |
|
eschaton posted:pico and nano have kind of tried to be that, except pico uses a bunch of DEC TOPS-20 conventions instead of modern (Macintosh) conventions and nano is a version of pico infected with GNU like huitlacoche yes, i'm aware of nano, and it's the closest linux has to a usable text editor, but it uses nonstandard keys, even going as far as acknowledging that the user pressed ctrl-s and instead of saving the file, it complains to the user: "XOFF ignored, mumble mumble"
|
# ? Mar 9, 2016 09:37 |
|
Wheany posted:yes, i'm aware of nano, and it's the closest linux has to a usable text editor, but it uses nonstandard keys, even going as far as acknowledging that the user pressed ctrl-s and instead of saving the file, it complains to the user: "XOFF ignored, mumble mumble" nano is probably the best shell text editor but that poo poo is ridiculously annoying
|
# ? Mar 9, 2016 10:00 |
|
if you want to use a text editor in a terminal, just man up and learn to use vi or emacs imo. you're already using a 1970s user interface anyway, may as well go the whole hog
|
# ? Mar 9, 2016 10:03 |
|
Soricidus posted:if you want to use a text editor in a terminal, just man up and learn to use vi or emacs imo. you're already using a 1970s user interface anyway, may as well go the whole hog it's really 1980s terminal tech at least and tyool 198x had quite usable text mode editors on micro soft disk operating system despite said pos having a considerably more primitive terminal layer. some of them even had mouse based text selection. there isnt any reason why we can't have nice things like that running in a modern unix terminal imo (i mean we all know the reason why we cant, see the thread title, just saying theres no technical barrier, and never was)
|
# ? Mar 9, 2016 10:42 |
|
for some reason I thought vim was originally an editor for the amiga? maybe vim as opposed to vi premiered on the amiga, dunno
|
# ? Mar 9, 2016 12:25 |
|
celeron 300a posted:the other guy to thank is whoever wrote bogofilter, it stopped all my users from complaining about spam. What a godsend. a subtle troll or an actual esr shoutout? you decide!
|
# ? Mar 9, 2016 13:09 |
|
bill joy wrote vi so he could convince scott mcnealy to write sun tools.
|
# ? Mar 9, 2016 13:12 |
|
One time, back in 2001, I went to a professor's office hours for help with a weird corner case bug. He said to bring up my code, so I opened it in pico. He then made fun of me for using an "abomination of a text editor" or something and couldn't navigate around because he kept using vi shortcuts. I still insist the bug was his fault.
|
# ? Mar 9, 2016 16:51 |
|
Origin posted:bill joy wrote vi so he could convince scott mcnealy to write sun tools. nice CPColin posted:One time, back in 2001, I went to a professor's office hours for help with a weird corner case bug. He said to bring up my code, so I opened it in pico. He then made fun of me for using an "abomination of a text editor" or something and couldn't navigate around because he kept using vi shortcuts. he was right yr a fuckin scrub
|
# ? Mar 9, 2016 18:38 |
|
that professors name? ken thompson
|
# ? Mar 9, 2016 18:39 |
|
nah I bet my rear end it was a no name greybeard who thinks too highly of himself
|
# ? Mar 9, 2016 18:52 |
Wheany posted:Has anyone made a linux text editor that works normally, ie ctrl-s is save, ctrl-c is copy, ctrl-v is paste, ctrl-z is undo and so on? I think gedit works like this?
|
|
# ? Mar 9, 2016 18:57 |
|
Symbolic Butt posted:nah I bet my rear end it was a no name greybeard who thinks too highly of himself He was one of the founders of Experts Exchange, if that helps. By the way, back in 2001, I was using the version of EDIT.COM that came with Windows 2000 to do my programming. Good times.
|
# ? Mar 9, 2016 19:01 |
|
Wheany posted:... that works in the terminal, i mean why do people want editors in terminals, i dont get it
|
# ? Mar 9, 2016 19:44 |
|
on the rare occasion you have to access a Linux it would be nice if that Linux had a working text editor. it will probably never happen, tho
|
# ? Mar 9, 2016 19:46 |
|
BobHoward posted:it's really 1980s terminal tech at least and tyool 198x had quite usable text mode editors on micro soft disk operating system despite said pos having a considerably more primitive terminal layer. some of them even had mouse based text selection. there isnt any reason why we can't have nice things like that running in a modern unix terminal imo emacs has mouse based text selection in text mode, just saying
|
# ? Mar 9, 2016 19:47 |
|
Shaggar posted:on the rare occasion you have to access a Linux it would be nice if that Linux had a working text editor. it will probably never happen, tho another great thing about emacs is that it also works very well on microsoft windows, so you can use the same text editor on every platform, all for the low low price of learning a few slightly different keyboard shortcuts
|
# ? Mar 9, 2016 19:48 |
|
emacs is equally bad on all platforms.
|
# ? Mar 9, 2016 19:49 |
|
Soricidus posted:there are approximately 0 situations where it is appropriate to edit a file using a shell script ityool 2016 sed owns fucker
|
# ? Mar 9, 2016 19:55 |
|
Malcolm XML posted:sed owns fucker Fucker is a free man. Slavery is illegal.
|
# ? Mar 9, 2016 20:10 |
|
Soricidus posted:emacs has mouse based text selection in text mode, just saying also in cocoa mode Shaggar posted:emacs is equally bad on all platforms. yeah, i agree that emacs is the best editor on all platforms
|
# ? Mar 9, 2016 20:27 |
|
Soricidus posted:there are approximately 0 situations where it is appropriate to edit a file using a shell script ityool 2016
|
# ? Mar 9, 2016 20:30 |
|
Smythe posted:Fucker is a free man. Slavery is illegal. i chuckled
|
# ? Mar 9, 2016 20:31 |
|
knowing and using vim and emacs is p easy. literally takes like 2 hours to get past the weirdness of learnign one of them. than just write down the weirder stuff and sticky note it on your monitor it just feels dirty and cumbersome using nano b0red fucked around with this message at 21:54 on Mar 9, 2016 |
# ? Mar 9, 2016 21:52 |
|
vim owns
|
# ? Mar 9, 2016 22:04 |
|
crazypenguin posted:why do people want editors in terminals, i dont get it some times you just have to use a terminal
|
# ? Mar 9, 2016 22:04 |
|
vi(m) is a must learn if you want to work on remote/minimal servers. It also owns really hard. Learning curve is the same as practically anything else on linux
|
# ? Mar 9, 2016 22:05 |
|
Roargasm posted:vi(m) is a must learn if you want to work on remote/minimal servers. quote:It also owns really hard. Its utter loving piss garbage and if you think differently you're stockholmed as gently caress
|
# ? Mar 9, 2016 23:42 |
|
jre posted:yep
|
# ? Mar 9, 2016 23:45 |
|
Wheany posted:some times you just have to use a terminal i am actually sorta serious with that question. the only time i can think of when i use an editor in a terminal is when i'm writing a git commit message that's too long to -m. i'm pretty sure it opens nano by default. it works fine for that. I can't be arsed to try to use something different because there's issues with notifying git when I'm done editing. like, it waits on a pid and that doesn't always work with gui editors or something. is it just that you're trying to edit files that are on a remote machine, and you don't have any good options for being able to slurp those files across ssh in order to use a good editor? ...i wonder if i can fix that
|
# ? Mar 10, 2016 00:07 |
|
crazypenguin posted:i am actually sorta serious with that question. Setting up machines with unconfigured / hosed up networking via a virtual console is not that uncommon a use case.
|
# ? Mar 10, 2016 00:31 |
|
If you're editing files on a remote server you're very probably loving up. I spun up a fairly hefty box on EC2 so that I could make OpenEmbedded builds in reasonable time and I do most of my mucking around with recipes on there (and I commit to Git from there sometimes too). I might possibly be loving up.
|
# ? Mar 10, 2016 00:49 |
|
crazypenguin posted:is it just that you're trying to edit files that are on a remote machine, and you don't have any good options for being able to slurp those files across ssh in order to use a good editor? good editors, such as emacs, do the slurping across ssh for you
|
# ? Mar 10, 2016 01:23 |
|
the best part about vim/emacs is identification of people who like to waste time. sure if you're sshing into a remote and need to edit something really quick vim is fine. but there's always that person who has a bespoke special snowflake vimrc that they've tirelessly handcrafted in their "free" time. i guess what i'm saying is, vim/emacs are honeypots.
|
# ? Mar 10, 2016 01:43 |
|
moonshine is...... posted:the best part about vim/emacs is identification of people who like to waste time. sure if you're sshing into a remote and need to edit something really quick vim is fine. but there's always that person who has a bespoke special snowflake vimrc that they've tirelessly handcrafted in their "free" time. i guess what i'm saying is, vim/emacs are honeypots. it's really not that bad. i'm pretty sure i've made fewer customizations to my emacs setup than to, say, my eclipse setup; it's just easier to see because it's all in one place in a form intended for human editing i guess there's some stuff like custom modes for some obscure/proprietary file formats that took a fair bit of work to set up, but that's the kind of thing that's literally impossible to do in most editors beyond trivial context-free syntax highlighting, so ... oh ok i'm a huge nerd i admit it are you happy now
|
# ? Mar 10, 2016 02:12 |
|
|
# ? Jun 4, 2024 15:56 |
|
just set up a smb share on the Linux you need to edit and open the file using Microsoft word 2016
|
# ? Mar 10, 2016 02:18 |