From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: command-separator char
Date: Mon, 22 Jun 2015 22:47:25 +0200 [thread overview]
Message-ID: <87d20n1ndu.fsf@debian.uxu> (raw)
In-Reply-To: mailman.5354.1434868275.904.help-gnu-emacs@gnu.org
Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
> several languages know about a character separating
> expressions resp. commands: ";" for example.
>
> Reflecting a generic level of navigations, it would
> be helpful if the language-modes would set such
> a constant.
This seems like a good idea - but is it?
If you use Emacs long enough which I think you have
isn't it better to just use the common point-moving
keys? G*d knows there are alot of them by now.
Also combine them with the M-{1..9} to move say three
`forward-word'. (Or use the otherwise `digit-argument'
keys which include C-{1..9} for you non-Linux VT user.
- or use C-u.)
Also write code to fit the style: Short words that are
simple to type and navigate, with short lines.
If you intend to use Emacs for a variety of
programming modes this seems like good money to start
putting in the bank early on. It makes sense being an
accordion player only because those chords will appear
over and over... Remember, "what you once feared, now
makes you free."
On the other "hand", if you will just use but a few
programming modes, say for Lisp and C, apart from
still being much helped by the first approach, you can
use the mode-specific functions on top of that:
`forward-sexp', for example.
What I see you are trying to do is put a third level
in-between then mode-specific and then all-out general
Emacs point-movement commands. It is a good idea on
the drawing board but a don't see myself ever using
it. But of course, I am not you.
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2015-06-22 20:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5354.1434868275.904.help-gnu-emacs@gnu.org>
2015-06-21 17:29 ` command-separator char Stefan Monnier
2015-06-21 18:18 ` Andreas Röhler
[not found] ` <mailman.5381.1434910741.904.help-gnu-emacs@gnu.org>
2015-06-22 20:00 ` Stefan Monnier
2015-06-23 6:19 ` Andreas Röhler
[not found] ` <mailman.5482.1435040400.904.help-gnu-emacs@gnu.org>
2015-06-23 12:45 ` Stefan Monnier
2015-06-23 13:56 ` Andreas Röhler
[not found] ` <mailman.5495.1435067817.904.help-gnu-emacs@gnu.org>
2015-06-23 17:00 ` Stefan Monnier
2015-06-23 18:43 ` Andreas Röhler
[not found] ` <mailman.5516.1435085009.904.help-gnu-emacs@gnu.org>
2015-06-23 19:33 ` Stefan Monnier
2015-06-24 5:47 ` Andreas Röhler
[not found] ` <mailman.5548.1435124835.904.help-gnu-emacs@gnu.org>
2015-06-24 14:32 ` Stefan Monnier
2015-06-22 20:47 ` Emanuel Berg [this message]
2015-06-21 6:31 Andreas Röhler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d20n1ndu.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.