From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Leo Liu <sdl.web@gmail.com>, 32649@debbugs.gnu.org
Subject: bug#32649: 27.0.50; up-list stops inside comment
Date: Sat, 8 Sep 2018 19:15:13 +0200 [thread overview]
Message-ID: <cc57675c-6ed2-b2bb-9de5-b9194bf6640e@easy-emacs.de> (raw)
In-Reply-To: <87a7otk7sg.fsf@igel.home>
On 07.09.2018 10:53, Andreas Schwab wrote:
> On Sep 07 2018, Andreas Röhler <andreas.roehler@easy-emacs.de> wrote:
>
>> On 07.09.2018 06:46, Leo Liu wrote:
>>> On 2018-09-06 21:04 +0200, Andreas Röhler wrote:
>>>> In scratch-buffer, cursor at "d" towards end of line 1
>>>>
>>>> (foo\n(a ;(b c d)
>>>> e) bar)
>>>>
>>>> M-- M-x up-list --called with negative argument-- stops at opening
>>>> paren inside comment.
>>>
>>> I am not following. What is the issue here?
>>
>> A list can't start resp. end inside a commented section.
>
> Sure it can. Just because it's behind a comment char doesn't mean it's
> not a list.
>
> Andreas.
From Elisp Info
2.2 Comments
============
A "comment" is text that is written in a program only for the sake of
humans that read the program, and that has no effect on the meaning of
the program. [...] The Lisp reader discards comments; they do not
become part of the Lisp objects which represent the program within the
Lisp system.
;;;
BTW being in favor to remove all syntax-fiddling from plain text modes
and fundamental-mode alike. Setting syntax there must produce
inconsistency and unexpected behavior.
An example: try M-x backward-sexp RET from end of a text-mode buffer
with contents:
1) Asdf
2) Asdf
>
next prev parent reply other threads:[~2018-09-08 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 19:04 bug#32649: 27.0.50; up-list stops inside comment Andreas Röhler
2018-09-07 4:46 ` Leo Liu
2018-09-07 7:52 ` Andreas Röhler
2018-09-07 8:53 ` Andreas Schwab
2018-09-08 17:15 ` Andreas Röhler [this message]
2018-09-08 17:54 ` Andreas Schwab
2018-09-08 19:26 ` Andreas Röhler
2020-08-21 11:51 ` Stefan Kangas
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=cc57675c-6ed2-b2bb-9de5-b9194bf6640e@easy-emacs.de \
--to=andreas.roehler@easy-emacs.de \
--cc=32649@debbugs.gnu.org \
--cc=schwab@linux-m68k.org \
--cc=sdl.web@gmail.com \
/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.