From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: Problem positioning cursor
Date: Sun, 27 Apr 2003 13:47:15 +0200 [thread overview]
Message-ID: <843ck4yxfg.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: usms55liy.fsf@ID-87814.user.dfncis.de
Oliver Scholz <alkibiades@gmx.de> writes:
> It should be possible even in Emacs 21.2. If you use something like
> ("lirum" _ "larum" _ "schubi"), then point is put at the first "_",
> unless that is consumed (so to say) for the region.
But the OP wants point to end up at the _second_ spot.
Hm.
Oh, are you saying that, if the region is active, then it gets put at
the first spot, and point at the second? That'd work, then.
--
file-error; Data: (Opening input file no such file or directory ~/.signature)
next prev parent reply other threads:[~2003-04-27 11:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5188.1051270162.21513.help-gnu-emacs@gnu.org>
2003-04-26 14:06 ` Problem positioning cursor Kai Großjohann
2003-04-26 15:24 ` Oliver Scholz
2003-04-27 11:47 ` Kai Großjohann [this message]
2003-04-27 12:40 ` Oliver Scholz
2003-04-25 11:01 Victor Kirk
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=843ck4yxfg.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).