Emacs Troubles
I've recently switched over from using GVim to Emacs, and it's worked out well so far, but I have one qualm. Whenever I'm writing C or C++ code it's only indenting by two spaces, while I'd prefer it to be set to four. Does anyone know how I could go about fixing this? Thanks!
Look it up in the manual. (Google "emacs manual". Hint, look for "tab stops".)
Tangentially related: http://xkcd.com/378/
Good luck!
Tangentially related: http://xkcd.com/378/
Good luck!
Haha yeah I didn't know you could switch sides in an editor war, but I needed a new OS. Anyhow I fixed it, and learned a little bit of lisp on the way with the addition of this to my .emacs:
|
|
Last edited on
I recently tried using emacs. I spent about 2 hours figuring out how to make it insert a TAB when I pressed the TAB key rather than spaces and making the TAB spacing 4 spaces wide. I then spent another couple of hours finding and installing a plugin that does really neat code-completion. Unfortunately the code-completion plugin interfered with my fix for the TAB key returning it to its former behaviour.
Configuring a text editor should not be this painful... ;o)
Configuring a text editor should not be this painful... ;o)
I think I nearly formatted my harddrive trying to figure out how to escape quit the program the first time I started it up.
Emacs is a very valuable editor, productively used by a great many people. I just don't like it, personally. ("Loathe" might be an appropriate description of how I feel about it.)
I like a modified WordStar 3 command set -- as soon as I get my own editor in gear you'll all get a chance to try it out. (Don't hold your collective breath, though. I still needs a lot of work.)
Emacs is a very valuable editor, productively used by a great many people. I just don't like it, personally. ("Loathe" might be an appropriate description of how I feel about it.)
I like a modified WordStar 3 command set -- as soon as I get my own editor in gear you'll all get a chance to try it out. (Don't hold your collective breath, though. I still needs a lot of work.)
Personally I think Emacs is a great Operating System... now if only it had a decent editor...
Yeah we haven't heard that joke ten-thousand times.
@Duoas, the first thing I did with it was open the tutorial, and the first command it taught you was how to close it :) Also out of curiosity might I ask what language you're coding your editor in and what library you're using (if you're using C/++)?
@Duoas, the first thing I did with it was open the tutorial, and the first command it taught you was how to close it :) Also out of curiosity might I ask what language you're coding your editor in and what library you're using (if you're using C/++)?
Last edited on
Yes, but I did not understand the wonky instruction. (What the heck does C-x mean? Everyone else in the known computing universe uses ^X or Ctrl-X.)
I think that one of the flaws of Emacs is that it assumes too much, breaking some important UI guidelines:
First: Users don't read squat.
Second: Don't use abnormal vocabulary or symbols in the squat your users aren't reading and assume they have any clue what it means.
Third: If your users are demonstrating a difficulty (such as, "How do I quit this blasted thing!?"), assume your interface is at fault -- don't put up more verbiage to "edumacate" the stoopid user.
By the time I decided that the program was too smart for me -- forcing me to google (well, actually, archie, remember that?) some more information about the blasted thing (instead of just killing the process, which I was going to do next) -- I had already tried many common methods of closing it (including asking XWM to do it -- which it refused, first requiring me to figure out how to save or abandon my active "buffer" -- more frighteningly non-descript vocabulary).
I can actually use Emacs nowdays, without too much chagrin, but it has enough annoying "features" to drive me batty. When simple edits become a battle of will with a piece of software, the software will loose -- my bit bucket is permanent, you see.
I'm coding my own editor with Tcl/Tk 8.5. (Sorry, no C++.)
There's no particular reason I couldn't do it in C++, but doing it directly in Tcl/Tk matches the project goals much more nicely...
:-]
I think that one of the flaws of Emacs is that it assumes too much, breaking some important UI guidelines:
First: Users don't read squat.
Second: Don't use abnormal vocabulary or symbols in the squat your users aren't reading and assume they have any clue what it means.
Third: If your users are demonstrating a difficulty (such as, "How do I quit this blasted thing!?"), assume your interface is at fault -- don't put up more verbiage to "edumacate" the stoopid user.
By the time I decided that the program was too smart for me -- forcing me to google (well, actually, archie, remember that?) some more information about the blasted thing (instead of just killing the process, which I was going to do next) -- I had already tried many common methods of closing it (including asking XWM to do it -- which it refused, first requiring me to figure out how to save or abandon my active "buffer" -- more frighteningly non-descript vocabulary).
I can actually use Emacs nowdays, without too much chagrin, but it has enough annoying "features" to drive me batty. When simple edits become a battle of will with a piece of software, the software will loose -- my bit bucket is permanent, you see.
I'm coding my own editor with Tcl/Tk 8.5. (Sorry, no C++.)
There's no particular reason I couldn't do it in C++, but doing it directly in Tcl/Tk matches the project goals much more nicely...
:-]
¿anybody tryied ed? http://www.gnu.org/fun/jokes/ed.msg.html
All the subsequent text uses "C-" ...
| man screen wrote: |
|---|
| Screen does not understand the prefix "C-" to mean control. Please use the caret notation ("^A" instead of "C-a") as arguments |
| Duoas wrote: |
|---|
| I'm coding my own editor with Tcl |
I could have called it (in fact, when I saw ascii's post, I considered calling it).
Topic archived. No new replies allowed.