From: "Andreas Röhler" <andreas.roehler@online.de>
To: bruce.connor.am@gmail.com
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: mark-sexp again
Date: Mon, 08 Jun 2015 20:55:34 +0200 [thread overview]
Message-ID: <5575E526.70902@online.de> (raw)
In-Reply-To: <CAAdUY-LxQCctOnEKdZ8uthrxsPDF6k2MCU9a9-rk5YdPSq0gUg@mail.gmail.com>
Am 08.06.2015 um 18:09 schrieb Artur Malabarba:
> 2015-06-08 15:24 GMT+01:00 Andreas Röhler <andreas.roehler@online.de>:
>> When inside a string, mark-sexp should mark the string. IMO doesn't make sense to consider the contents then.
>>
>> Example, cursor at beginning of docstring at "Just"
>>
>> (defun foo1 ()
>> "Just foo")
>>
>> M-x mark-sexp RET marks word "Just", not the string.
>>
>> Respectivly forward-sexp should reach the end of string, if called inside.
> That would make it redundant with `up-list'.
Don't think so:
(list "asdfsdf adfsadf " "asdfsd asd asdf " "asdfasf asdfsad ")
When started a "list", forward-sexp travels string by string, which is
ok and also means, it recognises a string as sexp already.
Accordingly from inside a string, it should go to the end first.
>
> As for the general suggestion, I personally like the current behavior.
> For instance, in the following docstring, it's nice that forward-sexp
> and kill-sexp work on `foo-bar' inside the string.
>
> (defun ok ()
> "something `foo-bar' something")
>
Because a kill-symbol-at-point seems missing.
No reason to maintain a quirk :)
next prev parent reply other threads:[~2015-06-08 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 13:57 mark-sexp again Andreas Röhler
2015-06-03 15:24 ` Stefan Monnier
2015-06-07 8:32 ` Andreas Röhler
2015-06-08 13:09 ` Stefan Monnier
2015-06-08 14:24 ` Andreas Röhler
2015-06-08 16:09 ` Artur Malabarba
2015-06-08 18:55 ` Andreas Röhler [this message]
2015-06-08 19:37 ` Artur Malabarba
2015-06-09 6:24 ` Andreas Röhler
2015-06-08 21:02 ` Stefan Monnier
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=5575E526.70902@online.de \
--to=andreas.roehler@online.de \
--cc=bruce.connor.am@gmail.com \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).