Mrthfx

Examples of transfinite towers

How to make healing in an exploration game interesting

What exactly is this small puffer fish doing and how did it manage to accomplish such a feat?

If I am holding an item before I cast Blink, will it move with me through the Ethereal Plane?

How are passwords stolen from companies if they only store hashes?

Why did it take so long to abandon sail after steamships were demonstrated?

Is it normal that my co-workers at a fitness company criticize my food choices?

Is a party consisting of only a bard, a cleric, and a warlock functional long-term?

Bach's Toccata and Fugue in D minor breaks the "no parallel octaves" rule?

Bacteria contamination inside a thermos bottle

Have the tides ever turned twice on any open problem?

Employee lack of ownership

What's the meaning of a knight fighting a snail in medieval book illustrations?

"of which" is correct here?

Different outputs for `w`, `who`, `whoami` and `id`

Custom alignment for GeoMarkers

Are Roman Catholic priests ever addressed as pastor

Is there a symmetric-key algorithm which we can use for creating a signature?

Non-trivial topology where only open sets are closed

Why does a Star of David appear at a rally with Francisco Franco?

Could the Saturn V actually have launched astronauts around Venus?

Professor being mistaken for a grad student

If I can solve Sudoku, can I solve the Travelling Salesman Problem (TSP)? If so, how?

Can I use USB data pins as a power source?

TeX warnings about non closed groups and LaTeX editors (that not warning)

Is there a TeX/LaTeX editor that can show results in real-time?Are there any (La)TeX editors that accept pasting rich text?StackExchange-like LaTeX editor - with live preview/rendering and control/formatting syntax not requiredWhich else Tex editors for windows are such that XeCJK is smoothly workable?latex editors and installation for asus eeebook running windows 10alignment and groups in LaTeX: how to explain the behavior?

1

Here is a MWE:

documentclass{article}



begin{document}



bgroup

Test 1



{

bfseries

Test 2



begingroup

Test 3

{



Test 4



end{document}

After running pdflatex through my kile editor, I don't get even a simple message or warning in the output (as I see it inside kile's "Log and Messages" window) but in the log file or by runing pdflatex I can see:

### simple group (level 4) entered at line 14 ({)

### semi simple group (level 3) entered at line 12 (begingroup)

### simple group (level 2) entered at line 8 ({)

### simple group (level 1) entered at line 5 ({)

### bottom level</usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/c

mbx10.pfb></usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmr10.p

fb>

I was expecting at least a warning on my editor. So my question is:

1. Which editors reproduce this "no warning" problem?


2. Is it a bug we have to report for every editor?

editors grouping

share|improve this question

edited Oct 30 '17 at 5:19

koleygr

asked Oct 30 '17 at 2:30

koleygrkoleygr

12.8k11038

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  the simple group message is the warning. it's issued by tex, not latex. i don't have a copy at hand, but i'm sure it's documented in the texbook. i also covered it in a talk at tug 2017; the slides are available from a link at the tug 2017 web site, accessible at tug.org/tug2017. the paper appears in tugboat 38:2 (accessible only to members at the moment); it's much different from the preprint, so if you're not a member, the slides are better.
  
  – barbara beeton
  Oct 30 '17 at 2:44
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks @barbarabeeton. For next visitors the slide is slide 14 here: gust.org.pl/bachotex/2017-pl/presentations/bbeeton-1-2017.pdf. It discussing about the good practice of closing any open group earlier, and at that slide talks about debugging of such "warnings". I also found there that a "good editor" had to provide functionality (like highlighting or may be warnings as far as I can understand it) about such groups... I tested on kile and LyX (kile just dont closing the highlighted area)... Both showed nothing on compilation. So, is this a feature of "no good editors" ?
  
  – koleygr
  Oct 30 '17 at 3:11
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @koleygr Kile is hopeless with TeX stuff, at least in LaTeX files. Reliably hopeless. It certainly won't recognise those as warnings.
  
  – cfr
  Oct 30 '17 at 4:59
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks @cfr for the information... If anyone of you find the same problem in other editors you can add them in comments to include them in my post since it is an editor specific problem as far as I can understand now... (I can confirm the problem on kile and lyx right now...)
  
  – koleygr
  Oct 30 '17 at 5:08
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  it's not really a bug but of course it would not be an unreasonable feature request for any editor. TeX makes it tricky as it doesn't change the program exit status or use the word Warning or write to stderr rather than stdout or do anything else to give any indication that anything is wrong, so the editor would need to look for that specific text and show it in their view of editors/warnings.
  
  – David Carlisle
  Oct 30 '17 at 7:57
  
  
  

  
  
  
  

 | 
show 8 more comments

1

Here is a MWE:

documentclass{article}



begin{document}



bgroup

Test 1



{

bfseries

Test 2



begingroup

Test 3

{



Test 4



end{document}

After running pdflatex through my kile editor, I don't get even a simple message or warning in the output (as I see it inside kile's "Log and Messages" window) but in the log file or by runing pdflatex I can see:

### simple group (level 4) entered at line 14 ({)

### semi simple group (level 3) entered at line 12 (begingroup)

### simple group (level 2) entered at line 8 ({)

### simple group (level 1) entered at line 5 ({)

### bottom level</usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/c

mbx10.pfb></usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmr10.p

fb>

I was expecting at least a warning on my editor. So my question is:

1. Which editors reproduce this "no warning" problem?


2. Is it a bug we have to report for every editor?

editors grouping

share|improve this question

edited Oct 30 '17 at 5:19

koleygr

asked Oct 30 '17 at 2:30

koleygrkoleygr

12.8k11038

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  the simple group message is the warning. it's issued by tex, not latex. i don't have a copy at hand, but i'm sure it's documented in the texbook. i also covered it in a talk at tug 2017; the slides are available from a link at the tug 2017 web site, accessible at tug.org/tug2017. the paper appears in tugboat 38:2 (accessible only to members at the moment); it's much different from the preprint, so if you're not a member, the slides are better.
  
  – barbara beeton
  Oct 30 '17 at 2:44
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks @barbarabeeton. For next visitors the slide is slide 14 here: gust.org.pl/bachotex/2017-pl/presentations/bbeeton-1-2017.pdf. It discussing about the good practice of closing any open group earlier, and at that slide talks about debugging of such "warnings". I also found there that a "good editor" had to provide functionality (like highlighting or may be warnings as far as I can understand it) about such groups... I tested on kile and LyX (kile just dont closing the highlighted area)... Both showed nothing on compilation. So, is this a feature of "no good editors" ?
  
  – koleygr
  Oct 30 '17 at 3:11
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @koleygr Kile is hopeless with TeX stuff, at least in LaTeX files. Reliably hopeless. It certainly won't recognise those as warnings.
  
  – cfr
  Oct 30 '17 at 4:59
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks @cfr for the information... If anyone of you find the same problem in other editors you can add them in comments to include them in my post since it is an editor specific problem as far as I can understand now... (I can confirm the problem on kile and lyx right now...)
  
  – koleygr
  Oct 30 '17 at 5:08
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  it's not really a bug but of course it would not be an unreasonable feature request for any editor. TeX makes it tricky as it doesn't change the program exit status or use the word Warning or write to stderr rather than stdout or do anything else to give any indication that anything is wrong, so the editor would need to look for that specific text and show it in their view of editors/warnings.
  
  – David Carlisle
  Oct 30 '17 at 7:57
  
  
  

  
  
  
  

 | 
show 8 more comments

Here is a MWE:

documentclass{article}



begin{document}



bgroup

Test 1



{

bfseries

Test 2



begingroup

Test 3

{



Test 4



end{document}

After running pdflatex through my kile editor, I don't get even a simple message or warning in the output (as I see it inside kile's "Log and Messages" window) but in the log file or by runing pdflatex I can see:

### simple group (level 4) entered at line 14 ({)

### semi simple group (level 3) entered at line 12 (begingroup)

### simple group (level 2) entered at line 8 ({)

### simple group (level 1) entered at line 5 ({)

### bottom level</usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/c

mbx10.pfb></usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmr10.p

fb>

I was expecting at least a warning on my editor. So my question is:

1. Which editors reproduce this "no warning" problem?


2. Is it a bug we have to report for every editor?

editors grouping

share|improve this question

edited Oct 30 '17 at 5:19

koleygr

asked Oct 30 '17 at 2:30

koleygrkoleygr

12.8k11038

documentclass{article}



begin{document}



bgroup

Test 1



{

bfseries

Test 2



begingroup

Test 3

{



Test 4



end{document}

### simple group (level 4) entered at line 14 ({)

### semi simple group (level 3) entered at line 12 (begingroup)

### simple group (level 2) entered at line 8 ({)

### simple group (level 1) entered at line 5 ({)

### bottom level</usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/c

mbx10.pfb></usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmr10.p

fb>

share|improve this question

edited Oct 30 '17 at 5:19

koleygr

asked Oct 30 '17 at 2:30

koleygrkoleygr

12.8k11038

share|improve this question

edited Oct 30 '17 at 5:19

koleygr

asked Oct 30 '17 at 2:30

koleygrkoleygr

12.8k11038

asked Oct 30 '17 at 2:30

koleygrkoleygr

12.8k11038

asked Oct 30 '17 at 2:30

koleygrkoleygr

12.8k11038

1 Answer
1

active

oldest

votes

0

Groups inside LaTeX and TeX is something that sometimes could be complicated and could even not be closed at all or closed after the expansion of a command somehow complicated and thus only TeX would discover on exiting that one or more groups are still open. (Thanks to all of the members that commented and made me understand this fact and to this community in general that helped me see some examples like the described)

In my opinion a good editor should provide all of the output of the compilation proces and of course the user should gain the ability to understand as more messages as possible and be able to debug easier hes/her code.

In order to not leave the question unanswered I am adding here the editors that tested till now and didn't gave output in their interface about the non closed groups (that TeX already provided) but have left them hidden inside the log file.

1. Overleaf (online editor that also forces the compilation)


2. Kile (that you have to open the log file in order to find TeX output)


3. LyX (as far as I remember it was giving no information at all and I have to open the log file too -but used just two or three times-)


4. TeXworks??? (not sure now)

Anyone is welcome to edit and add/remove editors

PS: Finally I realized that this forgotten question should deal with hiding "importand" TeX information from the user interface to be more useful/general and to offer something in this community.

share

answered 9 mins ago

koleygrkoleygr

12.8k11038

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f398716%2ftex-warnings-about-non-closed-groups-and-latex-editors-that-not-warning%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

0

Groups inside LaTeX and TeX is something that sometimes could be complicated and could even not be closed at all or closed after the expansion of a command somehow complicated and thus only TeX would discover on exiting that one or more groups are still open. (Thanks to all of the members that commented and made me understand this fact and to this community in general that helped me see some examples like the described)

In my opinion a good editor should provide all of the output of the compilation proces and of course the user should gain the ability to understand as more messages as possible and be able to debug easier hes/her code.

In order to not leave the question unanswered I am adding here the editors that tested till now and didn't gave output in their interface about the non closed groups (that TeX already provided) but have left them hidden inside the log file.

1. Overleaf (online editor that also forces the compilation)


2. Kile (that you have to open the log file in order to find TeX output)


3. LyX (as far as I remember it was giving no information at all and I have to open the log file too -but used just two or three times-)


4. TeXworks??? (not sure now)

Anyone is welcome to edit and add/remove editors

PS: Finally I realized that this forgotten question should deal with hiding "importand" TeX information from the user interface to be more useful/general and to offer something in this community.

share

answered 9 mins ago

koleygrkoleygr

12.8k11038

add a comment | 

0

Groups inside LaTeX and TeX is something that sometimes could be complicated and could even not be closed at all or closed after the expansion of a command somehow complicated and thus only TeX would discover on exiting that one or more groups are still open. (Thanks to all of the members that commented and made me understand this fact and to this community in general that helped me see some examples like the described)

In my opinion a good editor should provide all of the output of the compilation proces and of course the user should gain the ability to understand as more messages as possible and be able to debug easier hes/her code.

In order to not leave the question unanswered I am adding here the editors that tested till now and didn't gave output in their interface about the non closed groups (that TeX already provided) but have left them hidden inside the log file.

1. Overleaf (online editor that also forces the compilation)


2. Kile (that you have to open the log file in order to find TeX output)


3. LyX (as far as I remember it was giving no information at all and I have to open the log file too -but used just two or three times-)


4. TeXworks??? (not sure now)

Anyone is welcome to edit and add/remove editors

PS: Finally I realized that this forgotten question should deal with hiding "importand" TeX information from the user interface to be more useful/general and to offer something in this community.

share

answered 9 mins ago

koleygrkoleygr

12.8k11038

add a comment | 

Groups inside LaTeX and TeX is something that sometimes could be complicated and could even not be closed at all or closed after the expansion of a command somehow complicated and thus only TeX would discover on exiting that one or more groups are still open. (Thanks to all of the members that commented and made me understand this fact and to this community in general that helped me see some examples like the described)

In my opinion a good editor should provide all of the output of the compilation proces and of course the user should gain the ability to understand as more messages as possible and be able to debug easier hes/her code.

In order to not leave the question unanswered I am adding here the editors that tested till now and didn't gave output in their interface about the non closed groups (that TeX already provided) but have left them hidden inside the log file.

1. Overleaf (online editor that also forces the compilation)


2. Kile (that you have to open the log file in order to find TeX output)


3. LyX (as far as I remember it was giving no information at all and I have to open the log file too -but used just two or three times-)


4. TeXworks??? (not sure now)

Anyone is welcome to edit and add/remove editors

PS: Finally I realized that this forgotten question should deal with hiding "importand" TeX information from the user interface to be more useful/general and to offer something in this community.

share

answered 9 mins ago

koleygrkoleygr

12.8k11038

share

answered 9 mins ago

koleygrkoleygr

12.8k11038

answered 9 mins ago

koleygrkoleygr

12.8k11038

answered 9 mins ago

koleygrkoleygr

12.8k11038