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 21:26:11 +0200 [thread overview]
Message-ID: <7c632bae-36a0-58bd-cfb2-9b26ef9bb3ac@easy-emacs.de> (raw)
In-Reply-To: <87worv3mf0.fsf@igel.home>
On 08.09.2018 19:54, Andreas Schwab wrote:
> On Sep 08 2018, Andreas Röhler <andreas.roehler@easy-emacs.de> wrote:
>
>> 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.
>
> The concept of a list is independent of any programming language, and
> has nothing to do with the Lisp reader.
Hmm, didn't expect that and don't believe it. We speak about lists in
emacs-lisp here, it is defined what a list is. They affect there meaning
of a program and therefor can't exist inside a comment.
Moreover, you can run
> eval-last-sexp also inside a comment.
>
Thanks, just another bug. As the info above tells contents of a comment
having no effect WRT meaning of a program, result of evaluation in this
case comes from the deepness of nothing? ;)
next prev parent reply other threads:[~2018-09-08 19:26 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
2018-09-08 17:54 ` Andreas Schwab
2018-09-08 19:26 ` Andreas Röhler [this message]
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=7c632bae-36a0-58bd-cfb2-9b26ef9bb3ac@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.