gnome-latex issueshttps://gitlab.gnome.org/Archive/gnome-latex/-/issues2019-11-22T14:34:34Zhttps://gitlab.gnome.org/Archive/gnome-latex/-/issues/86Problem when hiding badboxes in the bottom panel2019-11-22T14:34:34ZGhost UserProblem when hiding badboxes in the bottom panelWith a document having lots of badboxes, the following occurred:
- Compile the document. Badboxes are shown in the bottom panel.
- (I think I clicked on a badbox, so one badbox was selected in the bottom panel).
- Click on the toggle but...With a document having lots of badboxes, the following occurred:
- Compile the document. Badboxes are shown in the bottom panel.
- (I think I clicked on a badbox, so one badbox was selected in the bottom panel).
- Click on the toggle button to hide the badboxes.
--> What happened is that when hiding the badboxes, the program removed one by one each badbox, but when doing so it has *selected* each badbox, which opened lots of files and going each time to the specified line. So I then needed to close each file manually.
Not a big problem, but it was a bit a WTF moment :-)https://gitlab.gnome.org/Archive/gnome-latex/-/issues/82Keyboard shortcuts for own build tools2019-11-29T18:49:43ZGhost UserKeyboard shortcuts for own build toolsWhen a new build method is created from the dialogue by cloning an existing (default) method, the keyboard shortcut (F2..F12) gets cloned too and appears in the menu behind that custom action. When the key is pressed, only the default co...When a new build method is created from the dialogue by cloning an existing (default) method, the keyboard shortcut (F2..F12) gets cloned too and appears in the menu behind that custom action. When the key is pressed, only the default command is executed.
It would be nice, if the key pressed to launch an action, can be set in the build tools configurator. First, the removal of keyboard shortcuts when cloning an action could help.
The associated keys should be configurable in the "build_tools.xml". The handling of duplicates needs to be managed.https://gitlab.gnome.org/Archive/gnome-latex/-/issues/71Auto-completion not working2019-11-29T18:33:14ZGhost UserAuto-completion not workingCompletion of LaTeX commands is not working (on Linux Mint 18.3 based on Ubunut 16.04).
Otherwise, great product!Completion of LaTeX commands is not working (on Linux Mint 18.3 based on Ubunut 16.04).
Otherwise, great product!https://gitlab.gnome.org/Archive/gnome-latex/-/issues/64don't spellcheck text inside specific latex commands2019-11-29T18:18:17Zkartoffelsalatdon't spellcheck text inside specific latex commandsText inside latex commands such as `\cite{Author2018}` or `\label{sec:important-section}` are underlined in red, if spell-check is turned on (because they are written wrong in obvious ways). I'd like to have an option to turn the spellch...Text inside latex commands such as `\cite{Author2018}` or `\label{sec:important-section}` are underlined in red, if spell-check is turned on (because they are written wrong in obvious ways). I'd like to have an option to turn the spellchecking off for such commands. I do see that for other commands such as `\section{A missssspelled title}` spell check makes sense.
Possibly this is a feature request for `gspell`, though?https://gitlab.gnome.org/Archive/gnome-latex/-/issues/51Remember state of structure widget after changing components in the side panel2018-03-25T12:28:50ZRobert GrieselRemember state of structure widget after changing components in the side panelWhen I switch to "Symbols"/"Files" and back to "Structure" all my folding is gone and everything is expanded again, for example. Also when the structure is updated, it is expanding again. Changing the latter could be a complicated task I...When I switch to "Symbols"/"Files" and back to "Structure" all my folding is gone and everything is expanded again, for example. Also when the structure is updated, it is expanding again. Changing the latter could be a complicated task I imagine. That's why I propose first to preserve the folding when the structure hasn't changed. Next I would save the structure state even when the app is closed (the way open files are preserved?).
Preserve the folding even while the structure is changing: I will think about this problem and post here when I find a (part-)solution.https://gitlab.gnome.org/Archive/gnome-latex/-/issues/42Projects: after changing main file of a project, tab label tooltip not updated2018-02-24T07:22:57ZBugzillaProjects: after changing main file of a project, tab label tooltip not updated## Submitted by Sébastien Wilmet `@swilmet`
**[Link to original bug (#786349)](https://bugzilla.gnome.org/show_bug.cgi?id=786349)**
## Description
After changing the main file of a project, the tab label tooltip is not updated.
The...## Submitted by Sébastien Wilmet `@swilmet`
**[Link to original bug (#786349)](https://bugzilla.gnome.org/show_bug.cgi?id=786349)**
## Description
After changing the main file of a project, the tab label tooltip is not updated.
The code for handling projects should be re-organized.https://gitlab.gnome.org/Archive/gnome-latex/-/issues/23Read-only files are not recognized2018-02-24T07:22:06ZBugzillaRead-only files are not recognized## Submitted by Chunyang Xu
**[Link to original bug (#724460)](https://bugzilla.gnome.org/show_bug.cgi?id=724460)**
## Description
Created attachment 269268
latex and gedit try to modify same read-only file (window title)
It seems...## Submitted by Chunyang Xu
**[Link to original bug (#724460)](https://bugzilla.gnome.org/show_bug.cgi?id=724460)**
## Description
Created attachment 269268
latex and gedit try to modify same read-only file (window title)
It seems that window's title should update when open read-only file.
In src/main_window.vala line 842:
active_document.readonly ? " [" + _("Read-Only") + "]" : ""
want to add "[Read-Only]" to window's title (like gedit), but it not work
**Attachment 269268**, "latex and gedit try to modify same read-only file (window title)":
![Screenshot_from_2014-02-16_14_12_01](/uploads/938d60376c10ab70ea2c701cb94696b1/Screenshot_from_2014-02-16_14_12_01.png)https://gitlab.gnome.org/Archive/gnome-latex/-/issues/8latexmk post-processor: error message not shown when xelatex not found2018-02-24T07:21:24ZBugzillalatexmk post-processor: error message not shown when xelatex not found## Submitted by Sébastien Wilmet `@swilmet`
**[Link to original bug (#722855)](https://bugzilla.gnome.org/show_bug.cgi?id=722855)**
## Description
The latexmk post-processor doesn't show an error message when the xelatex command is ...## Submitted by Sébastien Wilmet `@swilmet`
**[Link to original bug (#722855)](https://bugzilla.gnome.org/show_bug.cgi?id=722855)**
## Description
The latexmk post-processor doesn't show an error message when the xelatex command is not found. The complete latexmk output must be shown to understand what's wrong.