You can subscribe to this list here.
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2011 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
(38) |
Jun
(26) |
Jul
(2) |
Aug
(2) |
Sep
(2) |
Oct
(8) |
Nov
(5) |
Dec
|
2012 |
Jan
(22) |
Feb
(33) |
Mar
(21) |
Apr
(25) |
May
(284) |
Jun
(90) |
Jul
(43) |
Aug
(29) |
Sep
(41) |
Oct
(14) |
Nov
(27) |
Dec
(51) |
2013 |
Jan
(69) |
Feb
(14) |
Mar
(32) |
Apr
(33) |
May
(7) |
Jun
(16) |
Jul
(20) |
Aug
(27) |
Sep
(38) |
Oct
(48) |
Nov
(31) |
Dec
(8) |
2014 |
Jan
(7) |
Feb
(6) |
Mar
(16) |
Apr
(2) |
May
(28) |
Jun
(16) |
Jul
(5) |
Aug
(23) |
Sep
(3) |
Oct
(19) |
Nov
(42) |
Dec
(28) |
2015 |
Jan
(1) |
Feb
(4) |
Mar
(15) |
Apr
(36) |
May
|
Jun
(2) |
Jul
(20) |
Aug
(5) |
Sep
(43) |
Oct
(33) |
Nov
(17) |
Dec
(26) |
2016 |
Jan
(81) |
Feb
(24) |
Mar
(3) |
Apr
(12) |
May
(12) |
Jun
(11) |
Jul
(4) |
Aug
|
Sep
(2) |
Oct
(13) |
Nov
(16) |
Dec
(6) |
2017 |
Jan
(17) |
Feb
(8) |
Mar
(36) |
Apr
(15) |
May
(12) |
Jun
(11) |
Jul
(13) |
Aug
(7) |
Sep
(4) |
Oct
(1) |
Nov
(2) |
Dec
(6) |
2018 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(6) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(2) |
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(2) |
Dec
(7) |
2021 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
(2) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Benito v. d. Z. <be...@be...> - 2012-05-31 13:22:12
|
Or the script %SCRIPT cursor.insertText("\\"); editorView.complete(1); with trigger ² On 05/30/12 21:40, Benito van der Zander wrote: > Now you can use the script > > %SCRIPT > if (triggerMatches[0][1] == "²") { > cursor.insertText("\\\\"); > } else { > cursor.insertText("\\"+triggerMatches[0][1]); > app.NormalCompletion(); > } > > with trigger string (?.) > > On 05/30/12 17:31, Benito van der Zander wrote: >>> Essentially that means giving access to captured text, right? Anyway that'd >>> be a good idea. >>> >> Yes. >> >> But it will still be an ugly way to redefine ² as \ >> >> On 05/30/12 16:51, Tim Hoffmann wrote: >>>> Von: Benito van der Zander [mailto:be...@be...] >>>> Gesendet: Mittwoch, 30. Mai 2012 16:49 >>>> >>>>> You mean, internally to TXS? Otherwise, it will be confusing. >>>> Externally... >>>> >>>> Since this is the only way I see without changing txs >>>> >>>>> In such a case (²+ctrl+space), it will be longer to reach completion >>>>> than with AltGr+8. >>>> That's not was I meant. >>>> >>>> You already can write a user script that insert \ and calls the >>>> ctrl+space completion, >>>> whenever ² is pressed. >>>> >>>> But, because the completion dialog doesn't open, if there is no letter >>> after the \ >>>> that script has no effect. >>>> >>>>> Not sure what you mean here. >>>> You can define a macro with trigger ². that is called whenever the user >>> writes ² >>>> followed by letter. >>>> >>>> Then the ² and letter is removed, and the script called. >>>> That script can activate the completion, but first it has to insert \ and >>> the >>>> removed letter. >>>> However, the script has no way to determine, which letter was removed. >>>> >>>> But I could add such a way >>> Essentially that means giving access to captured text, right? Anyway that'd >>> be a good idea. >>> >>>> On 05/30/12 15:42, Denis Bitouzé wrote: >>>>> Le mercredi 30/05/12 à 15h32, >>>>> Benito van der Zander<be...@be...> a écrit : >>>>> >>>>>> Well, you can define those 52 user macros. >>>>> You mean, internally to TXS? Otherwise, it will be confusing. >>>>> >>>>>> Or we change one of the "bad" points, either show the completion list >>>>>> if the user calls it (presses ctrl+space) after a single \, >>>>> In such a case (²+ctrl+space), it will be longer to reach completion >>>>> than with AltGr+8. >>>>> >>>>>> or allow scripts to read its own trigger string >>>>> Not sure what you mean here. >>> ---------------------------------------------------------------------------- >>> -- >>>> Live Security Virtual Conference >>>> Exclusive live event will cover all the ways today's security and threat >>>> landscape has changed and how IT managers can respond. Discussions will >>>> include endpoint security, mobile security and the latest in malware >>> threats. >>>> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>> _______________________________________________ >>>> TeXstudio-list mailing list >>>> TeX...@li... >>>> https://lists.sourceforge.net/lists/listinfo/texstudio-list >>> ------------------------------------------------------------------------------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. Discussions >>> will include endpoint security, mobile security and the latest in malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> TeXstudio-list mailing list >>> TeX...@li... >>> https://lists.sourceforge.net/lists/listinfo/texstudio-list >>> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> TeXstudio-list mailing list >> TeX...@li... >> https://lists.sourceforge.net/lists/listinfo/texstudio-list >> > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > TeXstudio-list mailing list > TeX...@li... > https://lists.sourceforge.net/lists/listinfo/texstudio-list > |
From: Lion G. <ast...@gm...> - 2012-05-31 08:40:56
|
Ok, thanks for your response. G. Le 31/05/12 02:15, Tim Hoffmann a écrit : > > This effect was one of the reasons to introduce line spacing. It's > documented in the tool tip of the font size. > > The editor component we use, was not originally designed for different > font sizes. It might be possible to dynamically change the line > height, but that would require some fundamental changes to the drawing > method. At least you would have to determine the necessary line height > in advance. Likely there are more complications, because the font can > dynamically change on many operations and there are things like > caching. It's definitively not a high priority, so won't promise > anything about such a feature. Of course, if you or someone else has a > bit of programming background and is interested in that, you might > have a look at the drawing method (QDocumentPrivate::draw() in > qdocument.cpp) > > Tim > > *Von:*Lion Guillaume [mailto:ast...@gm...] > *Gesendet:* Donnerstag, 31. Mai 2012 00:54 > *An:* tex...@li... > *Betreff:* [TeXstudio-list] Line Spacing and Font Family > > Hi! > > When we increase the Font Family of an item in Syntax Highlighting, I > noted that top and bottom of the text (displays in the editor) may be > cut off if the line-height (or line spacing) is too small. > I give an example below by modifying the font of structure and the > line spacing: > > %--------- > [+++ THE REFERENCE +++] > Structure with Font Family: 100% > Line Spacing: 100% > Beschreibung: cid:par...@gm... > %--------- > Structure with Font Family: 130% > Line Spacing: 100% > Beschreibung: cid:par...@gm... > %--------- > Structure with Font Family: 180% > Line Spacing: 100% > Beschreibung: cid:par...@gm... > %--------- > Structure with Font Family: 130% > Line Spacing: 110% > Beschreibung: cid:par...@gm... > > Do you think it's possible to increase locally and automatically the > line-height according to the maximum Font value used in the line in > order to avoid this effect? > > Kind regards, > > Guillaume. > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > > _______________________________________________ > TeXstudio-list mailing list > TeX...@li... > https://lists.sourceforge.net/lists/listinfo/texstudio-list |
From: Denis B. <dbi...@wa...> - 2012-05-31 06:21:38
|
Le mercredi 30/05/12 à 21h55, Matthias Pospiech <mat...@gm...> a écrit : > ins files have a limited range of commands. These could be > automatically loaded for autocompletion. > > However I have not a list of these commands. I only copy them from > other files... I guess most of those commands are described in section 2 of dtxtut package/documentation and maybe DocStrip documentation. With TeX Live, you can easily reach them with: texdoc dtxtut texdoc DocStrip But this is an interesting question: for instance, biblatex.cfg is a file where the user can configure most of the biblatex options but currently TXS doesn't know biblatex's commands must be recognized in such a file (a commented \usepackage{biblatex} line doesn't help of course). Would it be possible, for instance with magic comments, to let TXS accept syntax from given class/packages in arbitrary files? -- Denis |
From: Lion G. <ast...@gm...> - 2012-05-30 22:54:24
|
Hi! When we increase the Font Family of an item in Syntax Highlighting, I noted that top and bottom of the text (displays in the editor) may be cut off if the line-height (or line spacing) is too small. I give an example below by modifying the font of structure and the line spacing: %--------- [+++ THE REFERENCE +++] Structure with Font Family: 100% Line Spacing: 100% %--------- Structure with Font Family: 130% Line Spacing: 100% %--------- Structure with Font Family: 180% Line Spacing: 100% %--------- Structure with Font Family: 130% Line Spacing: 110% Do you think it's possible to increase locally and automatically the line-height according to the maximum Font value used in the line in order to avoid this effect? Kind regards, Guillaume. |
From: Matthias P. <mat...@gm...> - 2012-05-30 19:55:45
|
Am 30.05.2012 00:33, schrieb Tim Hoffmann: > > Added cfg and ins to the extension filter. Please check, if everything works > with these files. > ins files have a limited range of commands. These could be automatically loaded for autocompletion. However I have not a list of these commands. I only copy them from other files... Matthias |
From: Benito v. d. Z. <be...@be...> - 2012-05-30 19:36:34
|
Now you can use the script %SCRIPT if (triggerMatches[0][1] == "²") { cursor.insertText("\\\\"); } else { cursor.insertText("\\"+triggerMatches[0][1]); app.NormalCompletion(); } with trigger string (?.) On 05/30/12 17:31, Benito van der Zander wrote: >> Essentially that means giving access to captured text, right? Anyway that'd >> be a good idea. >> > Yes. > > But it will still be an ugly way to redefine ² as \ > > On 05/30/12 16:51, Tim Hoffmann wrote: >>> Von: Benito van der Zander [mailto:be...@be...] >>> Gesendet: Mittwoch, 30. Mai 2012 16:49 >>> >>>> You mean, internally to TXS? Otherwise, it will be confusing. >>> Externally... >>> >>> Since this is the only way I see without changing txs >>> >>>> In such a case (²+ctrl+space), it will be longer to reach completion >>>> than with AltGr+8. >>> That's not was I meant. >>> >>> You already can write a user script that insert \ and calls the >>> ctrl+space completion, >>> whenever ² is pressed. >>> >>> But, because the completion dialog doesn't open, if there is no letter >> after the \ >>> that script has no effect. >>> >>>> Not sure what you mean here. >>> You can define a macro with trigger ². that is called whenever the user >> writes ² >>> followed by letter. >>> >>> Then the ² and letter is removed, and the script called. >>> That script can activate the completion, but first it has to insert \ and >> the >>> removed letter. >>> However, the script has no way to determine, which letter was removed. >>> >>> But I could add such a way >> Essentially that means giving access to captured text, right? Anyway that'd >> be a good idea. >> >>> On 05/30/12 15:42, Denis Bitouzé wrote: >>>> Le mercredi 30/05/12 à 15h32, >>>> Benito van der Zander<be...@be...> a écrit : >>>> >>>>> Well, you can define those 52 user macros. >>>> You mean, internally to TXS? Otherwise, it will be confusing. >>>> >>>>> Or we change one of the "bad" points, either show the completion list >>>>> if the user calls it (presses ctrl+space) after a single \, >>>> In such a case (²+ctrl+space), it will be longer to reach completion >>>> than with AltGr+8. >>>> >>>>> or allow scripts to read its own trigger string >>>> Not sure what you mean here. >>> >> ---------------------------------------------------------------------------- >> -- >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and threat >>> landscape has changed and how IT managers can respond. Discussions will >>> include endpoint security, mobile security and the latest in malware >> threats. >>> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> TeXstudio-list mailing list >>> TeX...@li... >>> https://lists.sourceforge.net/lists/listinfo/texstudio-list >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> TeXstudio-list mailing list >> TeX...@li... >> https://lists.sourceforge.net/lists/listinfo/texstudio-list >> > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > TeXstudio-list mailing list > TeX...@li... > https://lists.sourceforge.net/lists/listinfo/texstudio-list > |
From: Denis B. <dbi...@wa...> - 2012-05-30 15:33:22
|
Le mercredi 30/05/12 à 16h50, "Tim Hoffmann" <hof...@hi...> a écrit : > You mean as a word on the sheet icon? I meant just a button with text that could depend ("View DVI", "View PS" or "View PDF") on the last compilation the user has run. > Alternatively I could a magnifier symbol on top of the sheet. Why not? -- Denis |
From: Benito v. d. Z. <be...@be...> - 2012-05-30 15:28:14
|
> Essentially that means giving access to captured text, right? Anyway that'd > be a good idea. > Yes. But it will still be an ugly way to redefine ² as \ On 05/30/12 16:51, Tim Hoffmann wrote: >> Von: Benito van der Zander [mailto:be...@be...] >> Gesendet: Mittwoch, 30. Mai 2012 16:49 >> >>> You mean, internally to TXS? Otherwise, it will be confusing. >> Externally... >> >> Since this is the only way I see without changing txs >> >>> In such a case (²+ctrl+space), it will be longer to reach completion >>> than with AltGr+8. >> That's not was I meant. >> >> You already can write a user script that insert \ and calls the >> ctrl+space completion, >> whenever ² is pressed. >> >> But, because the completion dialog doesn't open, if there is no letter > after the \ >> that script has no effect. >> >>> Not sure what you mean here. >> You can define a macro with trigger ². that is called whenever the user > writes ² >> followed by letter. >> >> Then the ² and letter is removed, and the script called. >> That script can activate the completion, but first it has to insert \ and > the >> removed letter. >> However, the script has no way to determine, which letter was removed. >> >> But I could add such a way > Essentially that means giving access to captured text, right? Anyway that'd > be a good idea. > >> On 05/30/12 15:42, Denis Bitouzé wrote: >>> Le mercredi 30/05/12 à 15h32, >>> Benito van der Zander<be...@be...> a écrit : >>> >>>> Well, you can define those 52 user macros. >>> You mean, internally to TXS? Otherwise, it will be confusing. >>> >>>> Or we change one of the "bad" points, either show the completion list >>>> if the user calls it (presses ctrl+space) after a single \, >>> In such a case (²+ctrl+space), it will be longer to reach completion >>> than with AltGr+8. >>> >>>> or allow scripts to read its own trigger string >>> Not sure what you mean here. >> >> > ---------------------------------------------------------------------------- > -- >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and threat >> landscape has changed and how IT managers can respond. Discussions will >> include endpoint security, mobile security and the latest in malware > threats. >> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> TeXstudio-list mailing list >> TeX...@li... >> https://lists.sourceforge.net/lists/listinfo/texstudio-list > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > TeXstudio-list mailing list > TeX...@li... > https://lists.sourceforge.net/lists/listinfo/texstudio-list > |
From: Tim H. <hof...@hi...> - 2012-05-30 14:51:58
|
> Von: Benito van der Zander [mailto:be...@be...] > Gesendet: Mittwoch, 30. Mai 2012 16:49 > > > You mean, internally to TXS? Otherwise, it will be confusing. > Externally... > > Since this is the only way I see without changing txs > > > In such a case (²+ctrl+space), it will be longer to reach completion > > than with AltGr+8. > That's not was I meant. > > You already can write a user script that insert \ and calls the > ctrl+space completion, > whenever ² is pressed. > > But, because the completion dialog doesn't open, if there is no letter after the \ > that script has no effect. > > > Not sure what you mean here. > You can define a macro with trigger ². that is called whenever the user writes ² > followed by letter. > > Then the ² and letter is removed, and the script called. > That script can activate the completion, but first it has to insert \ and the > removed letter. > However, the script has no way to determine, which letter was removed. > > But I could add such a way Essentially that means giving access to captured text, right? Anyway that'd be a good idea. > On 05/30/12 15:42, Denis Bitouzé wrote: > > Le mercredi 30/05/12 à 15h32, > > Benito van der Zander<be...@be...> a écrit : > > > >> Well, you can define those 52 user macros. > > You mean, internally to TXS? Otherwise, it will be confusing. > > > >> Or we change one of the "bad" points, either show the completion list > >> if the user calls it (presses ctrl+space) after a single \, > > In such a case (²+ctrl+space), it will be longer to reach completion > > than with AltGr+8. > > > >> or allow scripts to read its own trigger string > > Not sure what you mean here. > > > ---------------------------------------------------------------------------- -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and threat > landscape has changed and how IT managers can respond. Discussions will > include endpoint security, mobile security and the latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > TeXstudio-list mailing list > TeX...@li... > https://lists.sourceforge.net/lists/listinfo/texstudio-list |
From: Tim H. <hof...@hi...> - 2012-05-30 14:50:22
|
> Von: Denis Bitouzé [mailto:dbi...@wa...] > Gesendet: Mittwoch, 30. Mai 2012 15:50 > > Le mercredi 30/05/12 à 13h57, > "Tim Hoffmann" <hof...@hi...> a écrit : > > > I could add black or grey lines indicating text. Any other > > suggestions? > > Just text? You mean as a word on the sheet icon? Alternatively I could a magnifier symbol on top of the sheet. |
From: Benito v. d. Z. <be...@be...> - 2012-05-30 14:45:26
|
> You mean, internally to TXS? Otherwise, it will be confusing. Externally... Since this is the only way I see without changing txs > In such a case (²+ctrl+space), it will be longer to reach completion > than with AltGr+8. That's not was I meant. You already can write a user script that insert \ and calls the ctrl+space completion, whenever ² is pressed. But, because the completion dialog doesn't open, if there is no letter after the \ that script has no effect. > Not sure what you mean here. You can define a macro with trigger ². that is called whenever the user writes ² followed by letter. Then the ² and letter is removed, and the script called. That script can activate the completion, but first it has to insert \ and the removed letter. However, the script has no way to determine, which letter was removed. But I could add such a way On 05/30/12 15:42, Denis Bitouzé wrote: > Le mercredi 30/05/12 à 15h32, > Benito van der Zander<be...@be...> a écrit : > >> Well, you can define those 52 user macros. > You mean, internally to TXS? Otherwise, it will be confusing. > >> Or we change one of the "bad" points, either show the completion >> list if the user calls it (presses ctrl+space) after a single \, > In such a case (²+ctrl+space), it will be longer to reach completion > than with AltGr+8. > >> or allow scripts to read its own trigger string > Not sure what you mean here. |
From: Denis B. <dbi...@wa...> - 2012-05-30 13:52:06
|
Le mercredi 30/05/12 à 13h52, "Tim Hoffmann" <hof...@hi...> a écrit : > > As in Texmaker? I'm not fan of it but why not. > > Maybe. But I tend to prefer a horizontal solution. Either as an > additional toolbar (but that costs space in hight), or in one line > with the tabs (could be to the right of the tabs) or a bar like in > QtCreator. This last solution looks nice. -- Denis |
From: Denis B. <dbi...@wa...> - 2012-05-30 13:50:03
|
Le mercredi 30/05/12 à 13h57, "Tim Hoffmann" <hof...@hi...> a écrit : > I could add black or grey lines indicating text. Any other > suggestions? Just text? -- Denis |
From: Denis B. <dbi...@wa...> - 2012-05-30 13:43:05
|
Le mercredi 30/05/12 à 15h32, Benito van der Zander <be...@be...> a écrit : > Well, you can define those 52 user macros. You mean, internally to TXS? Otherwise, it will be confusing. > Or we change one of the "bad" points, either show the completion > list if the user calls it (presses ctrl+space) after a single \, In such a case (²+ctrl+space), it will be longer to reach completion than with AltGr+8. > or allow scripts to read its own trigger string Not sure what you mean here. -- Denis |
From: Denis B. <dbi...@wa...> - 2012-05-30 13:40:18
|
Le mercredi 30/05/12 à 14h10, "Tim Hoffmann" <hof...@hi...> a écrit : > > @article: Article in &Journal > > I'm not very in favour of that because it gets very verbose. I agree but it helps both beginners and advanced users. IMO, this order technical term and then description is easy to read even if verbose. > Maybe if we get a two column menu? Could be great! Hence, it could be easy to reverse the order (technical term/description) if massively requested. > Rethinking Guillaume's original suggestion, we could just put the > entry type in the menu and entry type plus description in the dialog. Why not? > Another idea would be, not to show all entries in the menu. Then > again I don't think there is a consensus on the most used items, so > it would have to be configurable. Could be nice. > Maybe later. Anyway, as pointed out the whole scheme (text file, > menu, dialog) is a less-than-ideal solution for editing literature, > so I would not put too much effort into that. Yes. Do you think it could be helpful to make JabRef aware of TXS? I tested it with Kile and it works nicely: selecting LyX/Kile in the interface, selecting an entry whom key is 'key', Ctrl-L or clicking on the LyX/Kile icon, '\cite{key}' is inserted at the cursor position in Kile. > > Another request: in the "Insert Bibliography Entry..." dialog box, > > would it be possible to make the "ID" translatable? > > Yes. But I would have to think for a moment, how to do that correctly, > because internally we need the original strings. OK, thanks. -- Denis |
From: Benito v. d. Z. <be...@be...> - 2012-05-30 13:28:53
|
> Well, no hope? Well, you can define those 52 user macros. Or we change one of the "bad" points, either show the completion list if the user calls it (presses ctrl+space) after a single \, or allow scripts to read its own trigger string On 05/30/12 15:13, Denis Bitouzé wrote: > Le mercredi 30/05/12 à 13h56, > "Tim Hoffmann"<hof...@hi...> a écrit : > >> Of course we can do it. I'm just concerned if it's the "right" way. >> IMHO such basic key mapping is not business of an application but of >> the OS. > Well the backslash is not that much used outside the (La)TeX world. So > it is enough that TeX editors map a key for it. For instance, I mapped > the '²' key onto '\' in Emacs. > >> There again, its more difficult to configure. >> Would the user want different key bindings in different applications >> or is it more distracting, because you have to adapt your typing when >> switching between applications. > This is true for generic editors like Emacs or Vim. Currently, TXS > is dealing just with TeX files do we may postpone this question :) |
From: Denis B. <dbi...@wa...> - 2012-05-30 13:13:50
|
Le mercredi 30/05/12 à 13h56, "Tim Hoffmann" <hof...@hi...> a écrit : > Of course we can do it. I'm just concerned if it's the "right" way. > IMHO such basic key mapping is not business of an application but of > the OS. Well the backslash is not that much used outside the (La)TeX world. So it is enough that TeX editors map a key for it. For instance, I mapped the '²' key onto '\' in Emacs. > There again, its more difficult to configure. > Would the user want different key bindings in different applications > or is it more distracting, because you have to adapt your typing when > switching between applications. This is true for generic editors like Emacs or Vim. Currently, TXS is dealing just with TeX files do we may postpone this question :) -- Denis |
From: Denis B. <dbi...@wa...> - 2012-05-30 13:10:10
|
Le mercredi 30/05/12 à 13h46, "Tim Hoffmann" <hof...@hi...> a écrit : > On just a very quick view I didn't get the meaning of the options. > Seems like an options dialog would be reasonable. However an this > would require some work. If it's requested, it has to be postponed. > Is there something like a standard set of options, that we could > provide as a minimal solution? I'll try to provide such a set, though I guess that for standard case: htlatex filename is enough. If you have specific needs, for example you want to break up of the output into separate web pages, in accordance to the two top sectioning levels of the document, you'll have to specify: htlatex filename "html,2,info" -- Denis |
From: Tim H. <hof...@hi...> - 2012-05-30 12:19:07
|
> Von: Tim Hoffmann [mailto:hof...@hi...] > Gesendet: Mittwoch, 30. Mai 2012 13:58 > > > Von: Denis Bitouzé [mailto:dbi...@wa...] > > Gesendet: Mittwoch, 30. Mai 2012 10:24 > > > > Hi, > > > > I noticed that neutral icons were chosen for default tools. "Quick" > > and "Compile" ones are OK but, IMHO, the "View" one is a bit unfunny > > and > too > > neutral to be clear. > > I could add black or grey lines indicating text. Any other suggestions? Btw. I noticed, that TeXworks uses the term "Typeset" instead of Build or Compile. I think it's a good idea. If someone does not have a background in programming, these terms are not easy to understand (especially to distinguish). |
From: Tim H. <hof...@hi...> - 2012-05-30 12:10:38
|
> Von: Denis Bitouzé [mailto:dbi...@wa...] > Gesendet: Mittwoch, 30. Mai 2012 09:49 > > Hi, > > I noticed that biblatex entries are now implemented: many thanks! > > As the their number becomes high, it could be nice to sort them in order to let > the user more easily find out one of them. Sorting them by frequency of use is > hopeless but the alphabetic order could be nice. > > BTW: Guillaume suggests to place the technical (LaTeX or Bib(la)tex) terms > before their meaning, for instance: > > @article - Article in &Journal > > or even: > > @article: Article in &Journal I'm not very in favour of that because it gets very verbose. Maybe if we get a two column menu? Rethinking Guillaume's original suggestion, we could just put the entry type in the menu and entry type plus description in the dialog. Another idea would be, not to show all entries in the menu. Then again I don't think there is a consensus on the most used items, so it would have to be configurable. Maybe later. Anyway, as pointed out the whole scheme (text file, menu, dialog) is a less-than-ideal solution for editing literature, so I would not put too much effort into that. > to let: > > 1. the advanced user more easily find an entry; > > 2. the newbie learn the technical terms (it looks like a definition). > > This may be applied to other menu entries where both technical terms and > definitions are displayed (for instance LaTeX -> Font styles). > > Another request: in the "Insert Bibliography Entry..." dialog box, would it be > possible to make the "ID" translatable? Yes. But I would have to think for a moment, how to do that correctly, because internally we need the original strings. > -- > Denis > > ---------------------------------------------------------------------------- -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and threat > landscape has changed and how IT managers can respond. Discussions will > include endpoint security, mobile security and the latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > TeXstudio-list mailing list > TeX...@li... > https://lists.sourceforge.net/lists/listinfo/texstudio-list |
From: Tim H. <hof...@hi...> - 2012-05-30 11:58:07
|
> Von: Denis Bitouzé [mailto:dbi...@wa...] > Gesendet: Mittwoch, 30. Mai 2012 10:24 > > Hi, > > I noticed that neutral icons were chosen for default tools. "Quick" > and "Compile" ones are OK but, IMHO, the "View" one is a bit unfunny and too > neutral to be clear. I could add black or grey lines indicating text. Any other suggestions? |
From: Tim H. <hof...@hi...> - 2012-05-30 11:57:01
|
> Von: Denis Bitouzé [mailto:dbi...@wa...] > Gesendet: Mittwoch, 30. Mai 2012 10:18 > > Le mercredi 30/05/12 à 00h22, > Benito van der Zander <be...@be...> a écrit : > > > [...] > > > > Bad: You have to define 52 user macros, for every ² - lower/uppercase > > letter combination. > > > > Good: Then it works :) > > ;) > > Well, no hope? Of course we can do it. I'm just concerned if it's the "right" way. IMHO such basic key mapping is not business of an application but of the OS. There again, its more difficult to configure. Would the user want different key bindings in different applications or is it more distracting, because you have to adapt your typing when switching between applications. > -- > Denis > > ---------------------------------------------------------------------------- -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and threat > landscape has changed and how IT managers can respond. Discussions will > include endpoint security, mobile security and the latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > TeXstudio-list mailing list > TeX...@li... > https://lists.sourceforge.net/lists/listinfo/texstudio-list |
From: Tim H. <hof...@hi...> - 2012-05-30 11:52:22
|
> Von: Denis Bitouzé [mailto:dbi...@wa...] > Gesendet: Mittwoch, 30. Mai 2012 10:12 > > Le mercredi 30/05/12 à 00h23, > "Tim Hoffmann" <hof...@hi...> a écrit : > > > Almost :) It additionally switches the view. Is this combination still > > required? > > The panel can now be toggled via View -> Messages / Log File (or the > > button in the status bar). > > > > What about the following: > > - Remove View Log. > > I agree. > > > - Change clear markers to a toggle button "Show Markers" (which > > performs really the inverse). > > OK. > > > - Maybe move these as well as the next/previous error buttons to a > > toolbar attached to the log panel > > Do you mean to the "Errors" panel? Yes. But also Log File. > > to be created. > > As in Texmaker? I'm not fan of it but why not. Maybe. But I tend to prefer a horizontal solution. Either as an additional toolbar (but that costs space in hight), or in one line with the tabs (could be to the right of the tabs) or a bar like in QtCreator. > > It could also host additional buttons to select, which markers to > > show. > > Why not. > > > (Usually I'm not interested in bad boxes, > > Some of them need a deep look as they are very big! > > That's the reason I strongly suggest to make automatically appear the "Errors" > panel not only in case of errors but only when warning or badboxes arise: a > missing warning may lead to inconsistent table of contents, of figures, of tables, > inconsistent index and, even worse, wrong cross-references. > > > because latex produces a lot of them and you cannot do much about it) > > You can try microtype package which helps a lot. > -- > Denis > > ---------------------------------------------------------------------------- -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and threat > landscape has changed and how IT managers can respond. Discussions will > include endpoint security, mobile security and the latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > TeXstudio-list mailing list > TeX...@li... > https://lists.sourceforge.net/lists/listinfo/texstudio-list |
From: Tim H. <hof...@hi...> - 2012-05-30 11:46:52
|
> Von: Denis Bitouzé [mailto:dbi...@wa...] > Gesendet: Mittwoch, 30. Mai 2012 10:02 > > Le mardi 29/05/12 à 23h59, > "Tim Hoffmann" <hof...@hi...> a écrit : > > > Is it just like calling another compiler, i.e. switching between > > pdflatex and xelatex? (and no settings dialog). Then it's straight > > forward to implement. > > Yes. Up to my knowledge, what is specific to htlatex compiler: > > htlatex filename > > is that: > > 1. it silently runs 3 times; > > 2. it may take options after the filename: > > htlatex filename "options1" "option2" "options3" "options4" > > More details here: > > http://www.tug.org/applications/tex4ht/mn-commands.html On just a very quick view I didn't get the meaning of the options. Seems like an options dialog would be reasonable. However an this would require some work. If it's requested, it has to be postponed. Is there something like a standard set of options, that we could provide as a minimal solution? > > Otherwise I'd rather remove the HTML conversion. Last time I tried the > > present version, there were some problems, but I did not have the time > > to look into that. > > Maybe an missing option... > -- > Denis > > ---------------------------------------------------------------------------- -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and threat > landscape has changed and how IT managers can respond. Discussions will > include endpoint security, mobile security and the latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > TeXstudio-list mailing list > TeX...@li... > https://lists.sourceforge.net/lists/listinfo/texstudio-list |
From: Denis B. <dbi...@wa...> - 2012-05-30 08:24:33
|
Hi, I noticed that neutral icons were chosen for default tools. "Quick" and "Compile" ones are OK but, IMHO, the "View" one is a bit unfunny and too neutral to be clear. -- Denis |