GNU bug report logs - #48914
2021-06-07; C-cC-e environment insertion with first line of contents commented out

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 48914 in the body.
You can then email your comments to 48914 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: jfbu <jfbu <at> free.fr>
To: bug-auctex <at> gnu.org
Subject: 2021-06-07;
 C-cC-e environment insertion with first line of contents commented out
Date: Tue, 8 Jun 2021 10:42:52 +0200

Hi,
This may be a duplicate, sorry.
I am testing with git clone at 1b1361c0 Make TeX-fold-mode aware of superscript and subscript

Starting with this buffer:
---
\documentclass{article}

\begin{document}
%deliberately missing closing $ after \simeq
Reduces the background count rate by a factor of $R$ ($R\simeq 1/(1-.89)
= 9.1 for the shielding I used).
\end{document}
---

and LaTeX-mode active, select the three lines inside
the document environment, then hit C-cC-e foo

The result is

% \begin{foo}
%   deliberately missing closing $ after \simeq
Reduces the background count rate by a factor of $R$ ($R\simeq 1/(1-.89) = 9.1
for the shielding I used).
% \end{foo}

Perhaps environment insertion should by default, except
if in doctex-mode, not use % ?

or use it only if **all** lines are commented out ?

Best,
Jean-François

Message #8 received at 48914 <at> debbugs.gnu.org (full text, mbox):

From: Ikumi Keita <ikumi <at> ikumi.que.jp>
To: jfbu <jfbu <at> free.fr>
Cc: 48914 <at> debbugs.gnu.org
Subject: Re: bug#48914: 2021-06-07;
 C-cC-e environment insertion with first line of contents commented out
Date: Thu, 10 Jun 2021 15:05:09 +0900

Hi Jean,

>>>>> jfbu <jfbu <at> free.fr> writes:
> The result is

> % \begin{foo}
> %   deliberately missing closing $ after \simeq
> Reduces the background count rate by a factor of $R$ ($R\simeq 1/(1-.89) = 9.1
> for the shielding I used).
> % \end{foo}

> Perhaps environment insertion should by default, except
> if in doctex-mode, not use % ?

> or use it only if **all** lines are commented out ?

How about customizing `LaTeX-insert-into-comments' to nil? This option
has an effect of adding comment prefixes at the beginning of line for
some commands, and defaults to t.

AUCTeX sets this option to t unconditionally in doctex mode, so the
current default makes the standard latex mode to behave like doctex mode
in some aspects. (I'm not sure why it defaults to t.)

Some other commands are affected when you set this to nil, so please
report if it brings any undesired experience for you.

Regards,
Ikumi Keita

Message #11 received at submit <at> debbugs.gnu.org (full text, mbox):

From: jfbu <jfbu <at> free.fr>
To: bug-auctex <at> gnu.org
Subject: Re: bug#48914: 2021-06-07; C-cC-e environment insertion with first
 line of contents commented out
Date: Thu, 10 Jun 2021 17:27:11 +0200

Hi Keita,

Le 10/06/2021 à 08:05, Ikumi Keita a écrit :
> Hi Jean,
> 
>>>>>> jfbu <jfbu <at> free.fr> writes:
>> The result is
> 
>> % \begin{foo}
>> %   deliberately missing closing $ after \simeq
>> Reduces the background count rate by a factor of $R$ ($R\simeq 1/(1-.89) = 9.1
>> for the shielding I used).
>> % \end{foo}
> 
>> Perhaps environment insertion should by default, except
>> if in doctex-mode, not use % ?
> 
>> or use it only if **all** lines are commented out ?
> 
> How about customizing `LaTeX-insert-into-comments' to nil? This option
> has an effect of adding comment prefixes at the beginning of line for
> some commands, and defaults to t.


Thank you.  I have set it to nil and will see what happens.

> 
> AUCTeX sets this option to t unconditionally in doctex mode, so the
> current default makes the standard latex mode to behave like doctex mode
> in some aspects. (I'm not sure why it defaults to t.)

It would be better to be able to set it to nil only in non-doctex mode.

But, although I do currently work often with doctex-mode, I rarely
insert an environment in comments, because
1. in my way of using dtx, the documentation for user is not commented
   out in the file
2. only code comments are commented out (sic)
   and I rarely (almost never) use environments as I use there most of
   the time a custom tex macro for multi-paragraph \verb-like behaviour

> 
> Some other commands are affected when you set this to nil, so please
> report if it brings any undesired experience for you.
> 

I will try to be alert to changes I may detect.

Thanks for the tip.

Jean-François

Message #14 received at 48914 <at> debbugs.gnu.org (full text, mbox):

From: Arash Esbati <arash <at> gnu.org>
To: jfbu <jfbu <at> free.fr>
Cc: 48914 <at> debbugs.gnu.org
Subject: Re: bug#48914: 2021-06-07; C-cC-e environment insertion with first
 line of contents commented out
Date: Tue, 05 Mar 2024 10:43:37 +0100

jfbu <jfbu <at> free.fr> writes:

> Hi Keita,
>
> Le 10/06/2021 à 08:05, Ikumi Keita a écrit :
>> Hi Jean,
>> 
>>>>>>> jfbu <jfbu <at> free.fr> writes:
>>> The result is
>> 
>>> % \begin{foo}
>>> %   deliberately missing closing $ after \simeq
>>> Reduces the background count rate by a factor of $R$ ($R\simeq 1/(1-.89) = 9.1
>>> for the shielding I used).
>>> % \end{foo}
>> 
>>> Perhaps environment insertion should by default, except
>>> if in doctex-mode, not use % ?
>> 
>>> or use it only if **all** lines are commented out ?
>> How about customizing `LaTeX-insert-into-comments' to nil? This
>> option
>> has an effect of adding comment prefixes at the beginning of line for
>> some commands, and defaults to t.
>
>
> Thank you.  I have set it to nil and will see what happens.
>
>> AUCTeX sets this option to t unconditionally in doctex mode, so the
>> current default makes the standard latex mode to behave like doctex mode
>> in some aspects. (I'm not sure why it defaults to t.)
>
> It would be better to be able to set it to nil only in non-doctex mode.
>
> But, although I do currently work often with doctex-mode, I rarely
> insert an environment in comments, because
> 1. in my way of using dtx, the documentation for user is not commented
>    out in the file
> 2. only code comments are commented out (sic)
>    and I rarely (almost never) use environments as I use there most of
>    the time a custom tex macro for multi-paragraph \verb-like behaviour
>
>> Some other commands are affected when you set this to nil, so please
>> report if it brings any undesired experience for you.
>> 
>
> I will try to be alert to changes I may detect.
>
> Thanks for the tip.

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

No further comments, therefore I'm closing this report.

Best, Arash

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.