Texmaker and TeXstudio ⇒ TexMakerX (with interactive spellchecking!)

[benibela]

Feature suggestions/requests:

Is it possible to make sure that sectioning part (Structure) does not collapse at every save? It is pretty inconvenient to expand it every time one saves the document.

You're right, that is annoying, but only a symptom of the larger problem that the structure tree is removed and recreated every time you save. (which makes everything slower and is the reason there is no structure tree for every loaded file)
A workaround is too just select something in the tree, because the selection is restored afterwards.

It would be nice if sectioning commands, when given a shortcut (e.g. Ctrl+1 for \chapter), do not erase selected text but put it inside the brackets. Kile does that and Texmaker opens a dialog in which one can insert selected text with middle click.

That is a bug, I didn't noticed the texmaker dialog.
But you can define your own user tag as \chapter{%<%>} until it is fixed.

Also it would be nice to have "Change case" option for changing text between Uppercase and Lowercase letters.

Easy to implement, but won't get high priority (the edit menu is too long anyways)

Benito

[meho_r]

Thanks a lot for tips.

Regarding Edit menu and Change Case, maybe to add "Format" menu?

[lalop]

Change case is one thing that's been missing from every word processor I've ever used.

[benibela]

1.9.3 is there, to fix some bugs.
This is changed:
- \chapter will insert the selected text (without showing a dialog)
- bibtex will be automatically called
- forward search will work within included files
- paths relative to the master document will work again in the structure view
- dde doesn't crash anymore
- it won't slow down on mac
- kde dark theme is supported

[meho_r]

Thanks a lot, you just made life a lot easier Looking forward to work and test it. Installed on Mandriva from converted .deb to .rpm file. Works fine.

BTW, just a thought, regarding that Change Case feature. Maybe to put Bookmarks part of Edit menu on their own menu, and add Change Case to Edit menu. This way Edit menu will not become larger, and Bookmarks will be easier to access. What do you think, benibela?

[bookez]

Thanks for nice program. I think there is a small bug. I really like folding option, but it seems that it is not working properly when there are unbalanced brackets. I would like to have open brackets for something like i) bla bla, ii) bla bla...

Cheers.

[bookez]

One more thing. While code is folded, for example in bibtex, playing with the empty space between, going with the cursor up and down may lead to erratic deletion/insertion of visible text lines. I think that while everything is folded, there should be no scroll bar on the side for error to be reproducible.

[benibela]

I really like folding option, but it seems that it is not working properly when there are unbalanced brackets. I would like to have open brackets for something like i) bla bla, ii) bla bla

The problem is that the folded commands like \chapter are treated like brackets and if there are not closed brackets between them, the matching pair can't be detected.
The only fix I have so far for this, has the side effect to disable the highlighting of wrong brackets...

One more thing. While code is folded, for example in bibtex, playing with the empty space between, going with the cursor up and down may lead to erratic deletion/insertion of visible text lines. I think that while everything is folded, there should be no scroll bar on the side for error to be reproducible.

I don't understand how to reproduce that, can you post an example file?

[lalop]

I agree that the parentheses-code folding should be fixed if at all feasible. For instance, I can't even use the numbering system 1), etc without breaking the code folding.

[benibela]

Perhaps I can change it so, that there are different bracket categories, so that brackets from different categories are never assigned to eachother, however I have never idea how the bracket matching works in qcodeedit, since I never looked at function of the source so far.


But why are you even using 1) in the tex files, if \item looks nicer anyways...