bug#32649: 27.0.50; up-list stops inside comment

bug#32649: 27.0.50; up-list stops inside comment

[Andreas Röhler]

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.

Thanks,
Andreas,
GNU Emacs 27.0.50 (build 1, i686-pc-linux-gnu, GTK+ Version 3.14.5) of 
2018-08-29

bug#32649: 27.0.50; up-list stops inside comment

[Leo Liu]

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?

up-list has always worked that way and it is a nice feature of emacs
that I use everybody.

Cheers,
Leo

bug#32649: 27.0.50; up-list stops inside comment

[Andreas Röhler]

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.

bug#32649: 27.0.50; up-list stops inside comment

[Andreas Schwab]

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.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

bug#32649: 27.0.50; up-list stops inside comment

[Andreas Röhler]

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

> 

bug#32649: 27.0.50; up-list stops inside comment

[Andreas Schwab]

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.  Moreover, you can run
eval-last-sexp also inside a comment.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

bug#32649: 27.0.50; up-list stops inside comment

[Andreas Röhler]

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? ;)

bug#32649: 27.0.50; up-list stops inside comment

[Stefan Kangas]

tags 32649 + notabug wontfix
close 32649
thanks

Andreas Schwab <schwab@linux-m68k.org> writes:

> 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.

The request here is to make the navigational command `up-list' ignore
commented out text.  From reading this thread, no one was very
enthusiastic about this proposal.

To the arguments presented by others for the correctness of this
behaviour, I can only add that the proposal would make the command
significantly less useful.

I'm therefore closing this as wontfix.

Best regards,
Stefan Kangas