From: stl@isogmbh.de
Cc: Richard Stallman <rms@gnu.org>, henrik@enberg.org, emacs-devel@gnu.org
Subject: Re: backward-up-list
Date: 09 Aug 2002 10:38:31 +0200 [thread overview]
Message-ID: <uit2kv33s.fsf@isogmbh.de> (raw)
In-Reply-To: <200208090800.g7980In12044@rum.cs.yale.edu>
"Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> writes:
> > Of course if backward-up-list can work all within the string
> > (in which it currently already DTRT), it should still DTRT.
> >
> > I don't think so. I think that reliably moving out of the string
> > would be a more useful feature than operating on parentheses within a
> > string's contents.
>
> I very often use sexp-operations like backward-up-list inside strings
> (and even across strings, although it's only by luck that it works ;-).
> It's very handy when jumping around regexp groups, for example.
I thought backward-up-list does not work inside a string? Actually thats why
i came up with the first post...
> Maybe this usage pattern is unusual, I don't know, but I do know that
> I would miss it enough to write a little function to recover the "old"
> behavior rather than get used to the new behavior.
Maybe a variable could be used to switch between the two possibilities?
And a toogle function so that one could bind it to a key if need.
Stephan
next prev parent reply other threads:[~2002-08-09 8:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 13:45 backward-up-list Stephan Stahl
2002-07-17 13:48 ` backward-up-list Stefan Monnier
2002-07-18 14:55 ` backward-up-list Richard Stallman
2002-07-18 18:08 ` backward-up-list Henrik Enberg
2002-07-18 18:56 ` backward-up-list Stefan Monnier
2002-07-19 16:54 ` backward-up-list Richard Stallman
2002-07-19 17:52 ` backward-up-list Stefan Monnier
2002-07-20 0:35 ` backward-up-list Richard Stallman
2002-08-09 8:00 ` backward-up-list Stefan Monnier
2002-08-09 8:38 ` stl [this message]
2002-08-10 17:16 ` backward-up-list Richard Stallman
2002-07-20 22:02 ` backward-up-list Henrik Enberg
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=uit2kv33s.fsf@isogmbh.de \
--to=stl@isogmbh.de \
--cc=emacs-devel@gnu.org \
--cc=henrik@enberg.org \
--cc=rms@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.