Re: shorcut automatization
John Levon wrote: Doesn't sound like a good idea to me. It would make use of second word impossible, careful ordering so that more common options are preferred, etc. But rethinking again: I don't think this as a problem, but as a feature. (Also, it should be trivial to set the policy to prefer first letter, then first letter on the second word if it exist, then second letter and so on) Making shorcuts consistent would accelerate user interaction. In fact, I find a PITA every cleverness in choosing shorcuts. In the Layout-Document-Layout dialog tab (Qt frontend) we have for instance Options|t without any reason for not using O. Or Page style|s when P would be much more intuitive. And Float placement|p, same thing. At least we should decide a shorcut policy for manually placing them. And once the policy is decided, I would find strange if it cannot be automatized. If you want my opinion, I think shorcuts are useful when they are on the first letter. With some effort I can use if they are on the first letter of the second word, but if I have to find the underlined letter in the middle then I better tab out or click with the mouse. And it's indifferent (at least for me) if they follow some meaning of the action: you have to look at the dialog to use them. It's a problem for translation, but I do not think this is a solution. I'm not sure neither if this is the solution. But I don't think it's only a problem for translations. Alfredo (Back pretending to think)
Re: Bug: Matrix column separators.
On Mon, Feb 10, 2003 at 10:55:52PM +, Angus Leeming wrote: Joao Luis Meloni Assirati wrote: Is there some emacs mode that indents code only with tabs, as required by lyx code rules? Do you recommend another editor? Those brainwashed by vi propoganda will make some ridiculous suggestions to this question. Ignore them. Like use vim? That would not qualify as ridiculous Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: [PATCH] changes: LColor
Allan Rae wrote: What I'd like to know is how did Angus know I have purple on my desktop (as icon backgrounds and title bars as it happens) as well as black and gold? Let's just call it an educated guess based on the evidence available. AKA, a shot in the dark ;-) -- Angus
Re: shorcut automatization
Lars Gullik Bjønnes wrote: Angus Leeming [EMAIL PROTECTED] writes: | If we did this, then lyx could quite conceivably become a daemon process | communicating via the lyxserver with an external process which --- quite | conceivably --- could be our frontend dialogs with a main() routine. Then we would use bsd sockets (tcp) or local sockets (unix)... and then a lyx daemon could run and serve a xfroms gui and a qt gui at the same time... On deamon, one machine :-) _but_ I am not completely sure that I like the idea. Sure. However, the necessary first step of passing dialog information between the frontend and the core only as an LFUN, string pair is a good idea I think. Especially if we can use the same inset's read, write functions to do this as are used when loading up a document. Clearly, passing an inset*, as now, is nasty, nasty, nasty. Moreover, it may not be too much work ;-) The necessary second step of an improved lyxserver is also a fun project. When that is in place, there is nothing stopping an external app calling itself a LyX frontend, even if it's not the way that LyX itself chooses to do things. -- Angus
Re: Bug: Matrix column separators.
Joao Luis Meloni Assirati wrote: I must pay for complaining on such irrelevant bug. ;-P Welcome to the club. Jürgen.
Re: 140
Rod Pinna wrote: Hi all, Just checked out 1.4.0, and after a very quick play with track changes, it looks very good. When should I start reporting bugs with it? The moment you find them of course, together with a prescription to reproduce the bug. Filing them on bugzilla with key 'change tracking' would be icing on the cake. ps. Does such a key exist yet? -- Angus
Re: autoconf 2.57 works for me
Christian Ridderström wrote: so autogen.sh could be modified: Index: autogen.sh === RCS file: /cvs/lyx/lyx-devel/autogen.sh,v retrieving revision 1.42 diff -r1.42 autogen.sh 22c22 *2.5[2346]) --- *2.5[23467]) /Christian For me too, with both 1.3.x. and with 1.4cvs using a stock RH8 system. -- Angus
Re: [PATCH] QDocument (A4 specials)
Lars Gullik Bjønnes wrote: | Which would look a like the attached patch, which solves bug 844 | frontend-wise. With this, BufferParams::setPaperStuff and thus the | papersize/papersize2 distinction could go I think (but this is rather | your area). This means that the clever stuff moved from the core to | frontends (advantage is: it is more visible to the user). Any | disadvantages? Have I missed something? Duplicatoin of policy might be a problem. You mean per frontend? Yes. But at the moment we have three different policies for this simple function. One in the xfroms frontend (which is not complete, thus this patch), one in the qt frontend (also buggy, thus the other patch) and one -- which does exactly the contrary -- in bufferparams. Bloat is the smallest problem. The consequence ATM is that 1.3.0 is unusable for qt users who need papersizes other than the class default. You cannot produce a document in e.g. A5 with the qt version of 1.3.0 (because we have forgotten the core logic [BufferParams::setPaperStuff()] in the qt frontend). I think we should decide if we want the logic in the core or in the frontends. I'd vote for the frontend simply because of transparency to the users (disabling/enabling widgets etc.) and because the frontends have different means to handle the logic. Jürgen.
Re: What Magic Compiler Is Needed for LyX?
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: Lars | Sorry John, but andreas is right. Here is what the GNU Lars standards | texinfo file has to say Lars Why is the GNU standards texinfo file really appropriate in this Lars case? I really hope that document then also talks about autoconf Lars and automake. Actually, it is the autoconf docs that points to standards.texi, which itself points to make-stds.texi (both are bundled with autoconf). Anyway, I think this is a perfectly reasonable convention. JMarc
Re: [PATCH] QDocument (A4 specials)
Juergen == Juergen Spitzmueller [EMAIL PROTECTED] writes: Juergen I think we should decide if we want the logic in the core or Juergen in the frontends. I'd vote for the frontend simply because of Juergen transparency to the users (disabling/enabling widgets etc.) Juergen and because the frontends have different means to handle the Juergen logic. I do not understand how this changes transparency for the users? Could you explain what the difference would be? JMarc
One for Lars: insetminipage
Lars, you've written this in insetminipage.C
// \begin{minipage}[pos][height][inner-pos]{width} text \end{minipage}
Where:
// inner-pos [opt] = the position of the text within the box.
// It can be t, c, b or s, if unspecified the value
// of pos is used.
void InsetMinipage::read(Buffer const * buf, LyXLex lex) {
...
if (lex.isOK()) {
lex.next();
string const token = lex.getString();
if (token == inner_position) {
lex.next();
inner_pos_ = static_castInnerPosition(lex.getInteger());
} else {
lyxerr InsetMinipage::Read: Missing 'inner_position'-tag!
endl;
// take countermeasures
lex.pushToken(token);
}
}
}
At the moment we don't actually make use of inner_pos_ (nor do we output it
to LaTeX!). However, I thought I'd get reLyX to support minipage in its
entirety, so my question is what do you expect inner_pos_ values to be?
I ask, because I use this map
my %map = ('t' = '0', 'c' = '1', 'b' = '2');
to go from LaTeX to LyX values for the minipage 'pos' arg. Should I have a
similar map
%map = ('t' = '0', 'c' = '1', 'b' = '2', 's' = 3);
for 'inner_pos' or should I just pass t, c, b or s?
--
Angus
Re: Screenshots
Juergen == Juergen Spitzmueller [EMAIL PROTECTED] writes: Juergen while I was at it, I have also updated the screenshots page. Juergen Find it here: Juergen http://omnibus.uni-freiburg.de/~spitzmue/lyx-screenshots/screenshots.php3 Could you package it as a tar file so that I can put that on the web site? JMarc
Re: lyx graphical tour
Juergen == Juergen Spitzmueller [EMAIL PROTECTED] writes: Juergen John Levon wrote: Isn't this a little outdated (v1.0a)? While you are at it, why don't you shoot some new pictures, preferably with the qt frontend? I have been planning to do this for ages. Juergen http://omnibus.uni-freiburg.de/~spitzmue/lyx-lgt-1.3/lgt.html Juergen A tarball with the files is here: Juergen http://omnibus.uni-freiburg.de/~spitzmue/lyx-lgt-1.3.tar.gz Could you do a version that directly modifies the php3 files, please? You can get all the files from www-user cvs. You could also maybe update the file lgt.lyx which can be found there. Also, there are files in directories .pics and .xvpics, I guess they are not necessary. JMarc
Re: shorcut automatization
Lars Gullik Bjønnes wrote: Have I said that I really do not like the dialogs at all? I'd prefere an application completely without dialogs... Dialogs are indeed overused in most applications. I would love to see lyx do search replace emacs style. I.e. use the minibuffer instead of some popup the user have to move out of the way _and_ eventually close. The same applies to any other dialog small enough for the minibuffer, or that can be divided up sanely. Parameters for floats and other insets could be part of the expanded inset instead of a popup dialog. That could get big fast, so perhaps tabs or two levels of expansion is in order. The preamble could be a collapsable inset (very much like a ERT inset) but anchored at the beginning. But please don't see this as a new paradigm or absolute rule - lots of bad software appear when people try applying good ideas _everywhere_, even where they don't fit. I see no problem having preferences in a popup dialog - it is not something done every day and it certainly don't belong anywhere inside the document. Helge Hafting
Re: shorcut automatization
On Tue, Feb 11, 2003 at 03:14:30PM +1000, Allan Rae wrote: Menues, toolbar(s) and a minibuffer. The minute the minibuffer becomes necessary, the game is over, collect your shoes, and go home ... Rendering some configuration pages in a buffer -- like (x)emacs' customization settings. I have never been able to use that interface, and it buys us precisely nothing, and costs a lot. john
Re: shorcut automatization
On Tue, Feb 11, 2003 at 04:17:23PM +0900, Rob Lahaye wrote: Context-sensitive right-mouse-click menu popups. Yes, we do want this. Would something like this be feasible? In Xforms, Qt and/or Gnome? Yes regards john
Re: shorcut automatization
On Tue, Feb 11, 2003 at 11:50:55AM +0100, Helge Hafting wrote: I would love to see lyx do search replace emacs style. I.e. use the minibuffer instead of some popup the user have to move out of the way _and_ eventually close. This would be nice indeed, but it must be a complementary interface not the only way. Parameters for floats and other insets could be part of the expanded inset instead of a popup dialog. That could get big fast, so perhaps tabs or two levels of expansion is in order. sounds like a bad idea to me. The preamble could be a collapsable inset (very much like a ERT inset) but anchored at the beginning. Not sure about this. regards john
A question about lengths and reLyX
I have a trivial patch to the reLyX minibuffer output: * reLyX/BasicLyX.pm: Wrap minipage width and height output in inverted commas to keep the LyX parser happy with 4.5 cm. (Note the space.) However, I wonder whether I should do this or whether I should strip out the space instead? -- Angus
Re: shorcut automatization
John Levon [EMAIL PROTECTED] writes: | On Tue, Feb 11, 2003 at 03:14:30PM +1000, Allan Rae wrote: | | Menues, toolbar(s) and a minibuffer. | | The minute the minibuffer becomes necessary, the game is over, collect | your shoes, and go home ... Because you rather want a popup? | Rendering some configuration pages in a buffer -- like (x)emacs' | customization settings. | | I have never been able to use that interface, and it buys us precisely | nothing, and costs a lot. Gets rid of the popup/dialog clutter. -- Lgb
Re: shorcut automatization
On Tue, Feb 11, 2003 at 09:08:25AM +0100, Alfredo Braunstein wrote: Making shorcuts consistent would accelerate user interaction. In fact, I find a PITA every cleverness in choosing shorcuts. In the Layout-Document-Layout dialog tab (Qt frontend) we have for instance Options|t without any reason for not using O. Or Page style|s when P would be much more intuitive. And Float placement|p, same thing. This doesn't sound like cleverness to me, but silly choices. If you want my opinion, I think shorcuts are useful when they are on the first letter. That's fine for the default first choice, the tricky part is when the first letter is not available. And it's indifferent (at least for me) if they follow some meaning of the action: you have to look at the dialog to use them. If you do it often, it's likely slightly easier to remember if it's a meaningful mnemonic. regards john
Re: shorcut automatization
On Tue, Feb 11, 2003 at 11:59:28AM +0100, Lars Gullik Bj?nnes wrote: | The minute the minibuffer becomes necessary, the game is over, collect | your shoes, and go home ... Because you rather want a popup? I want default usable interfaces that do not require book-learnin' Suitable visual display and feedback is an important rationale for the existence of dialogs. I'd love to see how you do match whole words in the minibuffer. | I have never been able to use that interface, and it buys us precisely | nothing, and costs a lot. Gets rid of the popup/dialog clutter. By replacing it with some clutter on the buffer instead, which : 1) is non-standard 2) cannot use the frontend's architecture 3) requires more code I don't know about you, but I do not fancy coding all the stuff like tab navigation etc. by hand. john
Re: 140
On Tue, Feb 11, 2003 at 09:07:45AM +, Angus Leeming wrote: ps. Does such a key exist yet? Yes. Please report away. john
Re: [PATCH] changes: LColor
On Tuesday 11 February 2003 08:54, Angus Leeming wrote: Allan Rae wrote: What I'd like to know is how did Angus know I have purple on my desktop (as icon backgrounds and title bars as it happens) as well as black and gold? Let's just call it an educated guess based on the evidence available. AKA, a shot in the dark ;-) You hited the gold spot on the darkness. Ok, I'm starting to see a pattern here. ;-) -- José Abílio
Re: lyx graphical tour
Jean-Marc == Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: Juergen == Juergen Spitzmueller [EMAIL PROTECTED] writes: Juergen John Levon wrote: Isn't this a little outdated (v1.0a)? While you are at it, why don't you shoot some new pictures, preferably with the qt frontend? I have been planning to do this for ages. Juergen http://omnibus.uni-freiburg.de/~spitzmue/lyx-lgt-1.3/lgt.html Juergen A tarball with the files is here: Juergen http://omnibus.uni-freiburg.de/~spitzmue/lyx-lgt-1.3.tar.gz Jean-Marc Could you do a version that directly modifies the php3 Jean-Marc files, please? You can get all the files from www-user cvs. Jean-Marc You could also maybe update the file lgt.lyx which can be Jean-Marc found there. Oops, I see that the original lgt does not use our nice php stuff. Could you convert yours to use start.php3 and end.php3 and be php3 files? JMarc
Re: shorcut automatization
John Levon [EMAIL PROTECTED] writes: | On Tue, Feb 11, 2003 at 11:59:28AM +0100, Lars Gullik Bj?nnes wrote: | | | The minute the minibuffer becomes necessary, the game is over, collect | | your shoes, and go home ... | | Because you rather want a popup? | | I want default usable interfaces that do not require book-learnin' | | Suitable visual display and feedback is an important rationale for the | existence of dialogs. | | I'd love to see how you do match whole words in the minibuffer. think incremental search. | 1) is non-standard standard!?! -- Lgb
update the file descriptor generated by reLyX
Is anybody unhappy with this? If not, I'll commit it this afternoon sometime.
Angus
Index: lib/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/ChangeLog,v
retrieving revision 1.373
diff -u -p -r1.373 ChangeLog
--- lib/ChangeLog 11 Feb 2003 11:24:31 - 1.373
+++ lib/ChangeLog 11 Feb 2003 11:27:54 -
@@ -1,5 +1,10 @@
2003-02-11 Angus Leeming [EMAIL PROTECTED]
+ * reLyX/MakePreamble.pm: Output an accurate decription of what created
+ the file.
+
+2003-02-11 Angus Leeming [EMAIL PROTECTED]
+
* reLyX/BasicLyX.pm: Do as LyX does: wrap the minipage width and
height output in inverted commas and strip the space from 4.5 cm.
Factorise the code by defining sub getAsLyXLength.
Index: lib/reLyX/MakePreamble.pm
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/reLyX/MakePreamble.pm,v
retrieving revision 1.10
diff -u -p -r1.10 MakePreamble.pm
--- lib/reLyX/MakePreamble.pm 7 Feb 2003 22:27:23 - 1.10
+++ lib/reLyX/MakePreamble.pm 11 Feb 2003 11:27:54 -
@@ -148,7 +148,8 @@ sub translate_preamble {
#}
# Write first line of the lyx file
-$LyX_Preamble .= \#LyX 1.2 created this file. For more info see
http://www.lyx.org/\n;;
+$LyX_Preamble .= \# The reLyX bundled with LyX 1.3 created this file.\n .
+ # For more info see http://www.lyx.org/\n;;
# Print \lyxformat.
$LyX_Preamble .= \\lyxformat $Format\n;
Re: shorcut automatization
John Levon wrote: On Tue, Feb 11, 2003 at 09:08:25AM +0100, Alfredo Braunstein wrote: Making shorcuts consistent would accelerate user interaction. In fact, I find a PITA every cleverness in choosing shorcuts. In the Layout-Document-Layout dialog tab (Qt frontend) we have for instance Options|t without any reason for not using O. Or Page style|s when P would be much more intuitive. And Float placement|p, same thing. This doesn't sound like cleverness to me, but silly choices. That's my point. Non-standard choices are bad, so let's automatize the thing. Or at least make it in a standard way. That's fine for the default first choice, the tricky part is when the first letter is not available. What I'm saying is that they are not useful at all (for me) if they are not on the first say, two, letters of any word. If you do it often, it's likely slightly easier to remember if it's a meaningful mnemonic. Maybe you are right. An example not in the first letter? (without using run-together words please) Regards, Alfredo
Re: shorcut automatization
On Tue, Feb 11, 2003 at 12:15:31PM +0100, Lars Gullik Bj?nnes wrote: | I'd love to see how you do match whole words in the minibuffer. think incremental search. And how do you do case-insensitive ? john
Re: shorcut automatization
John Levon wrote: On Tue, Feb 11, 2003 at 12:15:31PM +0100, Lars Gullik Bj?nnes wrote: | I'd love to see how you do match whole words in the minibuffer. think incremental search. And how do you do case-insensitive ? It strikes me that you're playing the rôle of Luddite here ;-) If people want it and are willing to code it, why not let 'em? -- Angus
Re: shorcut automatization
On Tue, Feb 11, 2003 at 11:44:39AM +, Angus Leeming wrote: It strikes me that you're playing the rôle of Luddite here ;-) If people want it and are willing to code it, why not let 'em? In context, we are talking about replacing the find dialog. I have no problem with such additional functionality, in fact I'd welcome it, and likely use it myself. But replacing: no. regards john
Re: Importing really long tables
On Tuesday 11 February 2003 11:44, Garst R. Reese wrote: It makes the table and I can import into it, but it does not split the table over pages. Inserting a \newpage in the table put latex in a dither 98%cpu forever. And what happens if you convert the table to a longtable? -- José Abílio
Re: shorcut automatization
On Tue, 11 Feb 2003, Alfredo Braunstein wrote: John Levon wrote: Maybe you are right. An example not in the first letter? (without using run-together words please) The insert menu is full of examples of shortcuts that does not correspond to the first letters: Insert-Float a Insert-List TOC O Insert-Include file d Insert-Insert file e /Christian -- Christian Ridderström http://www.md.kth.se/~chr
Re: shorcut automatization
John Levon [EMAIL PROTECTED] writes: | On Tue, Feb 11, 2003 at 12:15:31PM +0100, Lars Gullik Bj?nnes wrote: | | | I'd love to see how you do match whole words in the minibuffer. | | think incremental search. | | And how do you do case-insensitive ? lowercase only - insensitive mixed case/upper case - sensitive just like emacs. -- Lgb
Re: shorcut automatization
On Tue, Feb 11, 2003 at 01:33:49PM +0100, Lars Gullik Bj?nnes wrote: | And how do you do case-insensitive ? lowercase only - insensitive mixed case/upper case - sensitive which has an obvious failure mode. john
Re: A question about lengths and reLyX
On Tue, Feb 11, 2003 at 11:00:37AM +, Angus Leeming wrote: I have a trivial patch to the reLyX minibuffer output: * reLyX/BasicLyX.pm: Wrap minipage width and height output in inverted commas to keep the LyX parser happy with 4.5 cm. (Note the space.) However, I wonder whether I should do this or whether I should strip out the space instead? I wonder whether this is not wasted effort. Could you have a look at the tex2lyx I just commited and try to figure out whether it is would be worthwhile to start from there instead of fixing reLyX? Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: shorcut automatization
On Tue, Feb 11, 2003 at 11:03:23AM +, John Levon wrote: | The minute the minibuffer becomes necessary, the game is over, collect | your shoes, and go home ... Because you rather want a popup? I want default usable interfaces that do not require book-learnin' I've never seen a search-and-replace dialog that would qualify as more usable than a minibuffer based approach with a decent history. I did require some learning, though... Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: shorcut automatization
On Tue, Feb 11, 2003 at 01:41:34PM +0100, Andre Poenitz wrote: I want default usable interfaces that do not require book-learnin' I've never seen a search-and-replace dialog that would qualify as more usable than a minibuffer based approach with a decent history. I did require some learning, though... The point is that the occassional or new user gets to use the dialog, which is (hopefully) obvious to use. As a user gets more experienced, or starts using search more heavily, the more efficient interface is there for them. Efficiency is not exactly equal to usability. Rather, efficiency is (an important part) of the whole package regards, john
Re: shorcut automatization
John Levon [EMAIL PROTECTED] writes: | On Tue, Feb 11, 2003 at 01:33:49PM +0100, Lars Gullik Bj?nnes wrote: | | | And how do you do case-insensitive ? | | lowercase only - insensitive | mixed case/upper case - sensitive | | which has an obvious failure mode. which does not matter. You have tried the functionality, yes? Does it work or not? -- Lgb
Re: A question about lengths and reLyX
On Tuesday 11 February 2003 12:39 pm, Andre Poenitz wrote: On Tue, Feb 11, 2003 at 11:00:37AM +, Angus Leeming wrote: I have a trivial patch to the reLyX minibuffer output: * reLyX/BasicLyX.pm: Wrap minipage width and height output in inverted commas to keep the LyX parser happy with 4.5 cm. (Note the space.) However, I wonder whether I should do this or whether I should strip out the space instead? I wonder whether this is not wasted effort. I wonder too. However, my motivation has been: 1. learn enough perl to feel comfortable when confronted with it. 2. LyX 1.3 will be around for at least 6 months. Could you have a look at the tex2lyx I just commited and try to figure out whether it is would be worthwhile to start from there instead of fixing reLyX? Certainly. But I would note that reLyX isn't very broken. The only _real_ problem is due to the foobarred state of the current LyX table format, about which I've already moaned. Anyway, I'll go look. Angus Andre'
Re: shorcut automatization
On Tue, Feb 11, 2003 at 11:39:46AM +, John Levon wrote: On Tue, Feb 11, 2003 at 12:15:31PM +0100, Lars Gullik Bj?nnes wrote: | I'd love to see how you do match whole words in the minibuffer. think incremental search. And how do you do case-insensitive ? By prepending \c. I doubt you click faster than I type that. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: shorcut automatization
John == John Levon [EMAIL PROTECTED] writes: John On Tue, Feb 11, 2003 at 01:41:34PM +0100, Andre Poenitz wrote: I want default usable interfaces that do not require book-learnin' I've never seen a search-and-replace dialog that would qualify as more usable than a minibuffer based approach with a decent history. I did require some learning, though... John The point is that the occassional or new user gets to use the John dialog, which is (hopefully) obvious to use. As a user gets more John experienced, or starts using search more heavily, the more John efficient interface is there for them. John Efficiency is not exactly equal to usability. Rather, efficiency John is (an important part) of the whole package Agreed. Getting rid of dialogs is a stupid move, IMO. JMarc
Re: update the file descriptor generated by reLyX
Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus Is anybody unhappy with this? If not, I'll commit it this Angus afternoon sometime. Angus I think this is ok (for 1.3 too) JMarc
Re: autoconf 2.57 works for me
Christian == Christian Ridderström [EMAIL PROTECTED] writes: Christian so autogen.sh could be modified: Done. JMarc
Re: [patch 13x]: reLyX natbib citations try 2
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus Fixes the mess in syntax.default. -- Angus
This one does not look right:
+\citealt[][{}
Once this is fixed, you can apply it to 1.3.x.
JMarc
Re: A question about lengths and reLyX
Andre Poenitz wrote:
On Tue, Feb 11, 2003 at 11:00:37AM +, Angus Leeming wrote:
I have a trivial patch to the reLyX minibuffer output:
* reLyX/BasicLyX.pm: Wrap minipage width and height output in
inverted commas to keep the LyX parser happy with 4.5 cm.
(Note the space.)
However, I wonder whether I should do this or whether I should strip out
the space instead?
I wonder whether this is not wasted effort.
Could you have a look at the tex2lyx I just commited and try to figure out
whether it is would be worthwhile to start from there instead of fixing
reLyX?
Andre'
Points so far:
s/stared/starred/
As JMarc noted yesterday, this approach:
else if (t.cs() == usepackage) {
string const options = getArg('[', ']');
string const name = getArg('{', '}');
if (name == a4wide) {
h_papersize = a4;
h_paperpackage = widemarginsa4;
fails for \usepackage{amsmath, natbib}. I see a nice 'split' function. Shall
I give you the first external contribution?
Interestingly, compilation fails with
Makefile:308: .deps/tex2lyx.Po: No such file or directory
$ mkdir src/tex2lyx/.deps
$ touch src/tex2lyx/.deps/tex2lyx.Po
solves the problem. Should it be generated automatically or cvs added?
I also needed a few using directives. See attached.
--
Angus
Index: src/tex2lyx/tex2lyx.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/tex2lyx/tex2lyx.C,v
retrieving revision 1.1
diff -u -p -r1.1 tex2lyx.C
--- src/tex2lyx/tex2lyx.C 11 Feb 2003 12:37:27 - 1.1
+++ src/tex2lyx/tex2lyx.C 11 Feb 2003 13:09:46 -
@@ -21,8 +21,13 @@ using std::endl;
using std::fill;
using std::getline;
using std::ios;
+using std::ifstream;
using std::istream;
+using std::istringstream;
using std::ostream;
+using std::ostringstream;
+using std::stack;
+using std::string;
using std::vector;
@@ -150,7 +155,7 @@ mode_type asMode(mode_type oldmode, stri
}
-bool stared(string const s)
+bool starred(string const s)
{
string::size_type const n = s.size();
return n s[n - 1] == '*';
Re: A question about lengths and reLyX
On Tue, Feb 11, 2003 at 12:51:24PM +, Angus Leeming wrote: I wonder too. However, my motivation has been: 1. learn enough perl to feel comfortable when confronted with it. 2. LyX 1.3 will be around for at least 6 months. Currently there is no dependency on LyX in tex2lyx (quite contrary to what I expected initially) so we would not need to wait six month do release it. Certainly. But I would note that reLyX isn't very broken. It is sort of ok for standard basic stuff and one or two things it supports. I've never seen it working for real world examples (i.e. $U_\epsilon$ of my desk with $\epsilon 3m$) Anyway, I'll go look. The tokenizer should be ok unless someone starts changing catcodes ore redefines macros. The backend (i.e. writing the proper .lyx constructs) is far from working, let alone complete... Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: A question about lengths and reLyX
On Tue, Feb 11, 2003 at 01:12:33PM +, Angus Leeming wrote:
As JMarc noted yesterday, this approach:
else if (t.cs() == usepackage) {
string const options = getArg('[', ']');
string const name = getArg('{', '}');
if (name == a4wide) {
h_papersize = a4;
h_paperpackage = widemarginsa4;
fails for \usepackage{amsmath, natbib}. I see a nice 'split' function. Shall
I give you the first external contribution?
Sure, why not.
$ mkdir src/tex2lyx/.deps
$ touch src/tex2lyx/.deps/tex2lyx.Po
solves the problem. Should it be generated automatically or cvs added?
I don't know.
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
Re: [patch 13x]: reLyX natbib citations try 2
Jean-Marc Lasgouttes wrote:
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus Fixes the mess in syntax.default. -- Angus
This one does not look right:
+\citealt[][{}
Once this is fixed, you can apply it to 1.3.x.
JMarc
What would I do without you? ;-)
--
Angus
Re: [PATCH] QDocument (A4 specials)
Jean-Marc Lasgouttes wrote: Juergen I think we should decide if we want the logic in the core or Juergen in the frontends. I'd vote for the frontend simply because of Juergen transparency to the users (disabling/enabling widgets etc.) Juergen and because the frontends have different means to handle the Juergen logic. I do not understand how this changes transparency for the users? Could you explain what the difference would be? Before 1.2 (I think) the logic of paperpackages vs. papersize was completely handled by the core. There were two choices in the dialog: Papersize and Special (A4 portrait only) (i.e. paperpackages). It was possible to chose e.g. A5 and Extra wide Margins, but this was reset to A4/Extra wide margins by bufferparams. So errors were corrected, but the user was not informed about this. In the 1.2 development cycle, we have decided to give some visual clues in the dialog. When an input does not make sense, it should not be allowed, when a widget does not make sense, it should be disabled (greyed out). In the case of the paper packages, this means (despite that the code is buggy without my patch): Disable paperpackages when - Papersize is not A4 - Custom Margins (geometry) is not chosen - Orientation is Landscape (Of course this means that we give papersize higher priority than paperpackages. We could have done this also the other way round, but that's not my point) I think this is more transparent, as the user sees Aha, this is not possible now. But once the logic is handled by the frontend, the core code is not needed anymore I think (unless you think this count as a kind of second prove). I'm not shure if I answered your question though. Did I? Jürgen.
Re: Bug: Matrix column separators.
Joao == Joao Luis Meloni Assirati [EMAIL PROTECTED] writes: Joao I must pay for complaining on such irrelevant bug. OK, I made Joao two patchs, one for 1.3 and the other for 1.4 (they differ only Joao in the ChangeLog). I applied the patch. Next time, please aoid to send patches with DOS-type line ends. JMarc
Re: A question about lengths and reLyX
Andre Poenitz [EMAIL PROTECTED] writes: | $ mkdir src/tex2lyx/.deps | $ touch src/tex2lyx/.deps/tex2lyx.Po | | solves the problem. Should it be generated automatically or cvs added? No! That was something wrong on your end. a autogen, re-configure, make distclean etc would have fixed it. -- Lgb
Re: reLyX support for \i, \j, \l, \L, \ss
Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus This patch enables reLyX to recognise that these should all be Angus output as insetLatexAccents. LyX can render all except \ss Angus well. Is this a limitation of insetlatexaccent, or should \ss Angus not be such a beast? Angus, feel free to apply to 1.3.x your latest version of this patch. JMarc
Re: A question about lengths and reLyX
On Tuesday 11 February 2003 1:21 pm, Lars Gullik Bjønnes wrote: Andre Poenitz [EMAIL PROTECTED] writes: | $ mkdir src/tex2lyx/.deps | $ touch src/tex2lyx/.deps/tex2lyx.Po | | solves the problem. Should it be generated automatically or cvs added? No! That was something wrong on your end. a autogen, re-configure, make distclean etc would have fixed it. Thanks for the info
Re: shorcut automatization
On Tue, Feb 11, 2003 at 01:46:49PM +0100, Lars Gullik Bj?nnes wrote: | which has an obvious failure mode. which does not matter. You have tried the functionality, yes? Yes. Does it work or not? It has an obvious failure mode, as above. john
Re: shorcut automatization
On Tue, Feb 11, 2003 at 02:02:48PM +0100, Andre Poenitz wrote: And how do you do case-insensitive ? By prepending \c. I doubt you click faster than I type that. I'm not sure how many times I can say that efficiency is not the be all and end all of a usable interface john
Re: reLyX support for \i, \j, \l, \L, \ss
Jean-Marc Lasgouttes wrote: Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus This patch enables reLyX to recognise that these should all be Angus output as insetLatexAccents. LyX can render all except \ss Angus well. Is this a limitation of insetlatexaccent, or should \ss Angus not be such a beast? Angus, feel free to apply to 1.3.x your latest version of this patch. JMarc I think I'll hold off on this one for the time being. -- Angus
Re: [patch] reLyX and \(...\)*
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus Ok, JMarc. I dug deep enough to understand how it works and
Angus have developed a gruding admiration for it. I append
^^^grudging? (I had to look up the word in
the webster. I learn everyday)
Angus 'lookAheadToken' (with some extra print statements). The guts
Angus of it is this line:
Angus $macro will match \X where X is: case 1: ')' (but not ')*').
Angus case 2: a single char 'not alphabetical, a-z or A-Z', followed
Angus by a single '*', if present, followed by an arbitrary amount of
Angus whitespace. Thus, matches both '\\' and '\\*'. case 3: a
Angus multi-char, alphabetical string, followed by a single '*', if
Angus present, followed by an arbitrary amount of whitespace. Thus,
Angus this matches both '\section' and '\section*'.
Angus In conclusion, therefore, my patch _is_ safe and does
Angus specialise the test so that '\)' (but not '\)*' is counted as a
Angus macro.
You have convinced me. But now I have another doubt: you take great
length to handle \)*, because this is what is pointed out in bug 9.
But as far as I can see, this is a rather rare occurence, not more
likely than for example \textbf* (which is \textbf{*}).
So a different algorithm could be:
1/ grab the macro always with the star.
2/ If this macro exists in syntax.default, then keep it.
3/ Otherwise, if the macro exists in syntax.default without the star,
then assume that * is a separate character
4/ Otherwise put the macro without * in ert, with a * after it
This may be a lot of work (is it?), but at least it would fix a bug
properly. I am not sure that I see the need to fix bug 9 per se. This
is adding special casing for a rare occurence.
As it is, I am not sure it is worth putting in 1.3.x.
JMarc
Re: shorcut automatization
John Levon [EMAIL PROTECTED] writes: | On Tue, Feb 11, 2003 at 01:46:49PM +0100, Lars Gullik Bj?nnes wrote: | | | which has an obvious failure mode. | | which does not matter. | | You have tried the functionality, yes? | | Yes. | | Does it work or not? | | It has an obvious failure mode, as above. which does not matter! -- Lgb
Re: shorcut automatization
On Tue, Feb 11, 2003 at 02:40:40PM +0100, Lars Gullik Bj?nnes wrote: | It has an obvious failure mode, as above. which does not matter! says who ! john
Re: reLyX support for \i, \j, \l, \L, \ss
Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus Jean-Marc Lasgouttes wrote: Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus This patch enables reLyX to recognise that these should all be Angus output as insetLatexAccents. LyX can render all except \ss Angus well. Is this a limitation of insetlatexaccent, or should \ss Angus not be such a beast? Angus, feel free to apply to 1.3.x your latest version of this patch. Angus I think I'll hold off on this one for the time being. OK, I let you be judge. JMarc
Re: [patch] reLyX and \(...\)*
On Tuesday 11 February 2003 1:38 pm, Jean-Marc Lasgouttes wrote:
You have convinced me. But now I have another doubt: you take great
length to handle \)*, because this is what is pointed out in bug 9.
But as far as I can see, this is a rather rare occurence, not more
likely than for example \textbf* (which is \textbf{*}).
So a different algorithm could be:
1/ grab the macro always with the star.
2/ If this macro exists in syntax.default, then keep it.
3/ Otherwise, if the macro exists in syntax.default without the star,
then assume that * is a separate character
4/ Otherwise put the macro without * in ert, with a * after it
This may be a lot of work (is it?), but at least it would fix a bug
properly. I am not sure that I see the need to fix bug 9 per se. This
is adding special casing for a rare occurence.
As it is, I am not sure it is worth putting in 1.3.x.
All fair points. As I said yesterday, I will not rewrite the TeX.pm parser; it
is a can or worms that will make a horrible mess if split open.
Let's bin the patch; at least we understand the logic of the code now.
Angus
Re: [patch 13x]: reLyX natbib citations try 2
Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus What would I do without you? ;-) Apply patches faster :) JMarc
Re: A question about lengths and reLyX
Andre == Andre Poenitz [EMAIL PROTECTED] writes: Andre The tokenizer should be ok unless someone starts changing Andre catcodes ore redefines macros. The backend (i.e. writing the Andre proper .lyx constructs) is far from working, let alone Andre complete... Are you sure that producing a .lyx file is the way to go? Another way would be to build a lyx document and then write it. This would mean that you do not need to update the program everytime there is a change of interfaces. I presume that you thought about that. So what are your reasons for doing it like you do now? JMarc
Re: reLyX support for \i, \j, \l, \L, \ss
On Tuesday 11 February 2003 1:43 pm, Jean-Marc Lasgouttes wrote: Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus Jean-Marc Lasgouttes wrote: Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus This patch enables reLyX to recognise that these should all be Angus output as insetLatexAccents. LyX can render all except \ss Angus well. Is this a limitation of insetlatexaccent, or should \ss Angus not be such a beast? Angus, feel free to apply to 1.3.x your latest version of this patch. Angus I think I'll hold off on this one for the time being. OK, I let you be judge. The only outstanding reLyX patch for 1.3.x is the 'recognise m columns in tabulars' one. Have you formed an opinion about it yet? I'll throw you a patch to support minipages eventually, but would like to squash the '% at end of paragraph causes 2 pars to be joined' bug first. Angus
Re: [patch] reLyX and \(...\)*
Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus All fair points. As I said yesterday, I will not rewrite the Angus TeX.pm parser; it is a can or worms that will make a horrible Angus mess if split open. Yes, it does not need more special casing added here and there... Angus Let's bin the patch; at least we understand the logic of the Angus code now. Angus Yes, and this is great progress. You can probably clse bug 9 as WONTFIX. JMarc
Re: lyx-devel src/tex2lyx/: ChangeLog tex2lyx.C
On Tuesday 11 February 2003 2:48 pm, [EMAIL PROTECTED] wrote: CVSROOT: /usr/local/lyx/cvsroot Module name: lyx-devel Repository: lyx-devel/src/tex2lyx/ Changes by: [EMAIL PROTECTED] 03/02/11 14:48:48 Modified files: lyx-devel/src/tex2lyx/: ChangeLog tex2lyx.C Log message: fix compile Patches: lyx-devel/src/tex2lyx/ http://www.lyx.org/cgi-bin/viewcvs.cgi/lyx-devel/src/tex2lyx/ChangeLog?r1=1 .2r2=1.3 http://www.lyx.org/cgi-bin/viewcvs.cgi/lyx-devel/src/tex2lyx/tex2lyx.C?r1=1 .2r2=1.3 You didn't cvs update did you? They're already in. Could you revert this please? Angus
Re: reLyX support for \i, \j, \l, \L, \ss
Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus The only outstanding reLyX patch for 1.3.x is the 'recognise m Angus columns in tabulars' one. Have you formed an opinion about it Angus yet? Since nobody else complained about it, I think you can apply it. What kind of plans do you have for reLyX (at least for 1.3.x)? JMarc
Re: Screenshots
Jean-Marc Lasgouttes wrote: Juergen == Juergen Spitzmueller [EMAIL PROTECTED] writes: Juergen while I was at it, I have also updated the screenshots page. Juergen Find it here: Juergen http://omnibus.uni-freiburg.de/~spitzmue/lyx-screenshots/screenshots.php3 Could you package it as a tar file so that I can put that on the web site? http://omnibus.uni-freiburg.de/~spitzmue/lyx-screenshots.tar.gz Regards, Jürgen. JMarc
Re: lyx-devel src/tex2lyx/: ChangeLog tex2lyx.C
On Tue, Feb 11, 2003 at 01:53:29PM +, Angus Leeming wrote: You didn't cvs update did you? I did (it wouldn't have let me commit otherwise). They're already in. Could you revert this Amazing that it managed to merge without conflicts. It's not normally that lax. john
Re: A question about lengths and reLyX
On Tue, Feb 11, 2003 at 02:46:48PM +0100, Jean-Marc Lasgouttes wrote: Andre The tokenizer should be ok unless someone starts changing Andre catcodes ore redefines macros. The backend (i.e. writing the Andre proper .lyx constructs) is far from working, let alone Andre complete... Are you sure that producing a .lyx file is the way to go? No. But it has certain benefits: - No dependence on LyX proper. - Small. - No need to access fragile LyX internals. Another way would be to build a lyx document and then write it. Yes. Actually that's what I intended originally. But it turned out while removing stuff from the math parser, that writing the .lyx is feasible and less effort. And as long as the LyX core is the mess it is I'd rather avoid internal interfaces as these are more likely to change than the comparatively stable external format. This would mean that you do not need to update the program everytime there is a change of interfaces. I do not have to. If all tex2lyx does is to produced lyxformat 222 reliably, the burden to create future formats is shifted to lyx2lyx. Of course, if at one point of time the format has evolved too far, tex2lyx might get an update. I presume that you thought about that. So what are your reasons for doing it like you do now? See above. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: lyx graphical tour
Am Dienstag, 11. Februar 2003 12:13 schrieb Jean-Marc Lasgouttes: Jean-Marc Could you do a version that directly modifies the php3 Jean-Marc files, please? You can get all the files from www-user cvs. Jean-Marc You could also maybe update the file lgt.lyx which can be Jean-Marc found there. Oops, I see that the original lgt does not use our nice php stuff. Could you convert yours to use start.php3 and end.php3 and be php3 files? http://omnibus.uni-freiburg.de/~spitzmue/lgt-1.0.tar.gz I think this follows the convention. Please insert in in the directory lgt-1.0, where the old LGT is located. There are still some dvi shots that I keep using (the others will be overridden). What is left is that the links in the menu of the other files should be changed from lgt.html to lgt.php3. I'm shure our resident script gurus will show us that this is a breeze ;-) Regards, Jürgen.
Re: shorcut automatization
Christian Ridderström wrote: On Tue, 11 Feb 2003, Alfredo Braunstein wrote: John Levon wrote: Maybe you are right. An example not in the first letter? (without using run-together words please) The insert menu is full of examples of shortcuts that does not correspond to the first letters: Insert-Float a Insert-List TOC O Insert-Include file d Insert-Insert file e /Christian I know. The question was if there are examples of 'natural' letter which aren't the first one. Are those of your example particularly better than choosing the first 'unused' one? Alfredo
Re: A question about lengths and reLyX
Andre == Andre Poenitz [EMAIL PROTECTED] writes: Andre But it has certain benefits: Andre - No dependence on LyX proper. - Small. - No need to access Andre fragile LyX internals. Indeed. But at least, when the internals change, you know about it because it does not compile anymore. This would mean that you do not need to update the program everytime there is a change of interfaces. Andre I do not have to. If all tex2lyx does is to produced lyxformat Andre 222 reliably, the burden to create future formats is shifted to Andre lyx2lyx. Andre Of course, if at one point of time the format has evolved too Andre far, tex2lyx might get an update. Like reLyX that produces a strange file format with a mix of old constructs and new ones... JMarc
Re: shorcut automatization
On Tue, Feb 11, 2003 at 12:43:58PM +, John Levon wrote: On Tue, Feb 11, 2003 at 01:41:34PM +0100, Andre Poenitz wrote: I want default usable interfaces that do not require book-learnin' I've never seen a search-and-replace dialog that would qualify as more usable than a minibuffer based approach with a decent history. I did require some learning, though... The point is that the occassional or new user gets to use the dialog, which is (hopefully) obvious to use. As a user gets more experienced, or starts using search more heavily, the more efficient interface is there for them. Yes! (Oh, dear; I'm agreeing with John again :) This is the Mac/Windows difference. Any idiot can sit down and use either (ok, today's windows; not older ones). Mac tends to have other and more efficient ways of doing things as you get experience--oddly, these stem from early MS products for mac, the company which has been systematically forcing everyone to stay in beginner mode. I'm not going to be able to sit someone down in front of LyX and convince them to try it if I have to do a minibuffer instead of a dialog search (unless it's someone accustomed to either emacs or a real editor to start with :). You keep people who ar able to find more efficient ways of doing things (which go into finger memory). Lyx has three major advantages that I see over latex at the moment: 1) You can see your complicated equations, and coherently edit them. 2) Less keystrokes than latex for the same effect (including auto-termination). 3) You can sit down at it with no training. The first is big for new and experienced users; the second keeps experienced users, and the third catches new users. hawk, who would still like the vi interface to lyx :) Efficiency is not exactly equal to usability. Rather, efficiency is (an important part) of the whole package regards, john -- Richard E. Hawkins, Asst. Prof. of Economics/\ ASCII ribbon campaign [EMAIL PROTECTED] Smeal 178 (814) 375-4700 \ / against HTML mail These opinions will not be those of Xand postings. Penn State until it pays my retainer. / \
Re: Using Qt in text.C
On Monday 10 February 2003 12:22, John Levon wrote: You'll have no joy trying that at all. You'll have to add some code in frontends/qt2/ and hide it behind the GUII firewall. Is there documentation on how to do that? Or are there files which can be used as an example (and which are not too complicated)? Try adding some functions to lyx_gui.C if it's just for testing Yes, it works for simple cases. But I cannot QObject::connect() stuff, since lyx_gui isn't a class but only a namespace it seems. Regards Daniel -- http://www.danielnaber.de
Re: Using Qt in text.C
On Tue, Feb 11, 2003 at 03:08:22PM +0100, Daniel Naber wrote: Is there documentation on how to do that? not really Yes, it works for simple cases. But I cannot QObject::connect() stuff, since lyx_gui isn't a class but only a namespace it seems. Create an object in lyx_gui::init then, and provide access like that regards john
Re: reLyX support for \i, \j, \l, \L, \ss
Jean-Marc Lasgouttes wrote: Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus The only outstanding reLyX patch for 1.3.x is the 'recognise m Angus columns in tabulars' one. Have you formed an opinion about it Angus yet? Since nobody else complained about it, I think you can apply it. Ok. What kind of plans do you have for reLyX (at least for 1.3.x)? To slow down ;-) But I do intend to keep going with the bug fixes and support for things like insetgraphics is probably easy too. I've decided that I will not bother upgrading the output of existing constructs to the current lyxformat, not least because the current lyxformat is foobarred in the case of tables. -- Angus
Re: [Fwd: LyX translations into polish]
Jean-Marc Lasgouttes wrote: Hello Tomasz, Michael forwarded your message to the list. Tomasz I send you fresh (I hope last :-)) update for pl.po, three new Tomasz layouts and alternatives polish keymaps. I applied pl.po and polski.kmap. Thanks Tomasz mwsls are available on TeXLive 7, tetex-beta and will be in Tomasz MikTeX, and contains: mwart, mwbk, mwrep -- classes for Tomasz preparing polish documents. And CTAN Could you send a short entry for the LaTeXConfig.lyx.in file and (if you can) a short explanation of the classes for Extended.lyx (if you feel that there are things to explain: is the class properly supported, are there special things to look for...)? I enclose updated mw*.layout files and short entry for the LaTeXConfig.lyx.in file and a short explanation of the classes for Extended.lyx. Bests Regards Tomasz -- Tomasz Luczak -| TECHNODAT Sp. z o.o. | +48 32 2382337 http://212.106.135.195/~tlu | PL 44-100 Gliwice| +48 32 3314484 http://www.technodat.com.pl | ul. Kosciuszki 1c| +48 602 524713 LyX_pl.tar.gz Description: GNU Zip compressed data
Re: shorcut automatization
On Tue, Feb 11, 2003 at 09:08:25AM +0100, Alfredo Braunstein wrote: If you want my opinion, I think shorcuts are useful when they are on the first letter. With some effort I can use if they are on the first letter of the second word, but if I have to find the underlined letter in the middle then I better tab out or click with the mouse. M-c c i I have no idea why anyone would associate that with insert columnt, but after doing a bunch from the menu, I finally noticed it, and it sure helps. Intuitive ones are nice (and again I'll mention early ms software for mac; I was using commands I'd never heard of!), but available sure beats the rodent if you have to do it a lot . . . hawk
Re: shorcut automatization
On Tue, Feb 11, 2003 at 03:00:49PM +0100, Alfredo Braunstein wrote: Christian Ridderstr?m wrote: Insert-List TOC O etc I know. The question was if there are examples of 'natural' letter which aren't the first one. Are those of your example particularly better than choosing the first 'unused' one? absolutely. His stay put when someone adds a feature higher up the menu, or earlier in the alphabet. There afe few things worse than the commands in your application changing with each release (this is where MS started losing it in the mac market). hawk -- Richard E. Hawkins, Asst. Prof. of Economics/\ ASCII ribbon campaign [EMAIL PROTECTED] Smeal 178 (814) 375-4700 \ / against HTML mail These opinions will not be those of Xand postings. Penn State until it pays my retainer. / \
Re: A question about lengths and reLyX
On Tue, Feb 11, 2003 at 03:02:52PM +0100, Jean-Marc Lasgouttes wrote: Andre Of course, if at one point of time the format has evolved too Andre far, tex2lyx might get an update. Like reLyX that produces a strange file format with a mix of old constructs and new ones... Not necessarily. The backend can be reworked completely if necessary. And I think it would be not too much effort.. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: shorcut automatization
Dr. Richard E. Hawkins wrote: On Tue, Feb 11, 2003 at 09:08:25AM +0100, Alfredo Braunstein wrote: M-c c i I have no idea why anyone would associate that with insert columnt, but after doing a bunch from the menu, I finally noticed it, and it sure helps. Intuitive ones are nice (and again I'll mention early ms software for mac; I was using commands I'd never heard of!), but available sure beats the rodent if you have to do it a lot . . . hawk But you have 'real' shorcuts for that, i.e. keyboard bindings of lfuns. I agree that bindings could be shown on the menu, though. Alfredo
Sorting and POTFILES.in
As Michael S pointed out, po/POTFILES.in gets updated every other commit just because the sort command has different semantics on different systems. This is a pain because it affects the po files too. Why is that? The current command used to sort is sort -f -n, where -f is to ignore case and -n is for numeric sorting. First, the -n seems bogus, and on my system it actually prevents case ignoring. This is why when I commit the file the case is preserved, while others commit a POTFILES.in with case ignored. I tried to use sort -f only, but it is not yet portable since I get the following diff: -src/insets/insetbib.C src/insets/inset.C +src/insets/insetbib.C So in one case '.' is before 'b' and in the other case it is after. Why are different sort implementations do different things, I don't know. So what should we do? Maybe remove the options altogether and use a plain sort? Would that give the same result for everybody? JMarc
Re: shorcut automatization
John Levon [EMAIL PROTECTED] writes: | On Tue, Feb 11, 2003 at 02:40:40PM +0100, Lars Gullik Bj?nnes wrote: | | | It has an obvious failure mode, as above. | | which does not matter! | | says who ! says me! -- Lgb
Re: reLyX support for \i, \j, \l, \L, \ss
Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus To slow down ;-) But I do intend to keep going with the bug Angus fixes and support for things like insetgraphics is probably Angus easy too. That's what I was about to suggest. Angus I've decided that I will not bother upgrading the output of Angus existing constructs to the current lyxformat, not least because Angus the current lyxformat is foobarred in the case of tables. Probably a good move. JMarc
Re: shorcut automatization
John Levon wrote: On Tue, Feb 11, 2003 at 11:59:28AM +0100, Lars Gullik Bj?nnes wrote: | The minute the minibuffer becomes necessary, the game is over, collect | your shoes, and go home ... Because you rather want a popup? I want default usable interfaces that do not require book-learnin' Suitable visual display and feedback is an important rationale for the existence of dialogs. I'd love to see how you do match whole words in the minibuffer. Easy enough. Make it a two-line minibuffer. Don't even need to enlarge it - use the minibuffer area _and_ the status line below it and stuff the GUI elements from the search replace dialog there when doing a search. No learning required. They press a key / use the menu as usual, and get the search replace stuff. Only they get it at the bottom of the screen instead of in some stupid dialog that obscures half of the text they're going to search in. Everybody know how to move the dialog - and hates having to do it too. Helge Hafting
Re: Sorting and POTFILES.in
On Tue, Feb 11, 2003 at 03:51:42PM +0100, Jean-Marc Lasgouttes wrote: So what should we do? Maybe remove the options altogether and use a plain sort? Would that give the same result for everybody? Do they need to be sorted at all? Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: shorcut automatization
John Levon wrote: On Tue, Feb 11, 2003 at 11:50:55AM +0100, Helge Hafting wrote: I would love to see lyx do search replace emacs style. I.e. use the minibuffer instead of some popup the user have to move out of the way _and_ eventually close. This would be nice indeed, but it must be a complementary interface not the only way. Why - if it offers the same functionality? The search dialog is small enough that its components can be squashed into the buffer area. Then there wouldn't be a need for a popup dialog because the dialog pops up inside the buffer area. Parameters for floats and other insets could be part of the expanded inset instead of a popup dialog. That could get big fast, so perhaps tabs or two levels of expansion is in order. sounds like a bad idea to me. I don't know if it'll be hard to code - I'm only thinking of the looks here. One can always dream. :-) Helge Hafting
Re: Sorting and POTFILES.in
Andre == Andre Poenitz [EMAIL PROTECTED] writes: Andre On Tue, Feb 11, 2003 at 03:51:42PM +0100, Jean-Marc Lasgouttes Andre wrote: So what should we do? Maybe remove the options altogether and use a plain sort? Would that give the same result for everybody? Andre Do they need to be sorted at all? Yes, probably, so that we can uniquify the list. JMarc
Re: shorcut automatization
On Tue, Feb 11, 2003 at 03:53:22PM +0100, Lars Gullik Bj?nnes wrote: | says who ! says me! My 300 page SCSI manual disagrees with you when I'm looking for a mis-spelling as scsi instead of SCSI john
Re: Sorting and POTFILES.in
On Tue, Feb 11, 2003 at 04:05:05PM +0100, Jean-Marc Lasgouttes wrote:
Andre Do they need to be sorted at all?
Yes, probably, so that we can uniquify the list.
This could be solved in twelve lines or so in any language that has map
#include set
#include string
#include iostream
int main()
{
setstring seen;
string word;
while (cin word)
if (seen.find(word) == seen.end()) {
seen.insert(word);
cout word ' ';
}
}
It's probably even shorter in perl.
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
Re: shorcut automatization
John Levon [EMAIL PROTECTED] writes: | On Tue, Feb 11, 2003 at 03:53:22PM +0100, Lars Gullik Bj?nnes wrote: | | | says who ! | | says me! | | My 300 page SCSI manual disagrees with you when I'm looking for a | mis-spelling as scsi instead of SCSI Your SCSI manual does not have an opinion. -- Lgb
Re: shorcut automatization
On Tue, Feb 11, 2003 at 04:30:52PM +0100, Lars Gullik Bj?nnes wrote: | My 300 page SCSI manual disagrees with you when I'm looking for a | mis-spelling as scsi instead of SCSI Your SCSI manual does not have an opinion. You're just discriminating against it ! john
Re: Screenshots
Juergen == Juergen Spitzmueller [EMAIL PROTECTED] writes: Could you package it as a tar file so that I can put that on the web site? Juergen http://omnibus.uni-freiburg.de/~spitzmue/lyx-screenshots.tar.gz Thanks, I converted this to real php3 files (including start.php3/end.php3) and commited. Now, let's look at the lgt. JMarc
Re: shorcut automatization
John Levon [EMAIL PROTECTED] writes: | On Tue, Feb 11, 2003 at 03:53:22PM +0100, Lars Gullik Bj?nnes wrote: | | | says who ! | | says me! | | My 300 page SCSI manual disagrees with you when I'm looking for a | mis-spelling as scsi instead of SCSI C-s M-c incremental searchstring Alternatively set the case-fold-search variable to 'nil' and you will get a case sensitive search all the time. -- Lgb
Re: lyx graphical tour
Juergen == Juergen Spitzmueller [EMAIL PROTECTED] writes: Juergen Am Dienstag, 11. Februar 2003 12:13 schrieb Jean-Marc Juergen Lasgouttes: Jean-Marc Could you do a version that directly modifies the php3 Jean-Marc files, please? You can get all the files from www-user cvs. Jean-Marc You could also maybe update the file lgt.lyx which can be Jean-Marc found there. Oops, I see that the original lgt does not use our nice php stuff. Could you convert yours to use start.php3 and end.php3 and be php3 files? Juergen http://omnibus.uni-freiburg.de/~spitzmue/lgt-1.0.tar.gz Are you sure this is the right URL? Juergen I think this follows the convention. Please insert in in the Juergen directory lgt-1.0, where the old LGT is located. There are Juergen still some dvi shots that I keep using (the others will be Juergen overridden). We should probably rename the directory lgt, then. JMarc
Re: Sorting and POTFILES.in
Andre == Andre Poenitz [EMAIL PROTECTED] writes: Andre On Tue, Feb 11, 2003 at 04:05:05PM +0100, Jean-Marc Lasgouttes Andre wrote: Do they need to be sorted at all? Yes, probably, so that we can uniquify the list. Andre This could be solved in twelve lines or so in any language that Andre has map Which is irrelevant to our problem, probably but... Andre setstring seen; Does the standard offer guarrantees about the order in which these things will be given by the iterator? JMarc
Re: shorcut automatization
On Tue, 11 Feb 2003, Dr. Richard E. Hawkins wrote: On Tue, Feb 11, 2003 at 03:00:49PM +0100, Alfredo Braunstein wrote: Christian Ridderstr?m wrote: Insert-List TOC O etc I know. The question was if there are examples of 'natural' letter which aren't the first one. Are those of your example particularly better than choosing the first 'unused' one? To be honest, I misunderstood the question and thought the requested example was only for shortcuts that weren't associated with the first letter, i.e. nothing about natural. However, I'd say that Minipage p is an example of a natural shortcut, and perhaps also 'x' for export. But on the other hand, I really _hate_ having to remember 'a' for float... Actually, I liked your idea of systematically naming the shortcuts until I read hawk's point: His stay put when someone adds a feature higher up the menu, or earlier in the alphabet. There afe few things worse than the commands in your application changing with each release (this is where MS started losing it in the mac market). Can the user change this through the .bind-files (and also see the change in the menues)? (I looked in menus.bind and cua.bind but didn't find anything there) /Christian -- Christian Ridderström http://www.md.kth.se/~chr
Re: Sorting and POTFILES.in
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: | Andre == Andre Poenitz [EMAIL PROTECTED] writes: | | Andre On Tue, Feb 11, 2003 at 04:05:05PM +0100, Jean-Marc Lasgouttes | Andre wrote: Do they need to be sorted at all? | Yes, probably, so that we can uniquify the list. | | Andre This could be solved in twelve lines or so in any language that | Andre has map | | Which is irrelevant to our problem, probably but... | | Andre setstring seen; | | Does the standard offer guarrantees about the order in which these | things will be given by the iterator? sorted. sorting function and locale decides sorting order. -- Lgb
tex2lyx
André, here's a patch to get it to work on this little test case. Else it
get's lost in an infinite loop in handle_opts (There are none to
documentclass...).
--
Angus
\documentclass{article}
\usepackage{a4wide, ae}
\begin{document}
text above
\begin{minipage}[c][0.45\textheight][a]{0.45\columnwidth}%
foo foo foo foo foo foo foo foo foo foo foo foo foo foo
foo foo foo foo foo foo foo foo foo foo foo foo foo
foo foo foo foo foo foo foo foo foo foo foo foo foo
foo foo foo foo foo foo foo foo foo foo foo foo foo
foo foo foo foo foo foo\end{minipage}%
\hfill\begin{minipage}[t]{4.5 cm}%
bar bar bar bar bar bar bar bar bar bar bar bar bar bar
bar bar bar bar bar bar bar bar bar bar bar bar bar bar
bar bar bar bar bar bar bar bar bar bar bar bar bar bar
bar bar bar bar bar bar bar bar bar bar bar bar bar bar
bar bar bar bar bar bar bar bar\end{minipage}%
text below
\end{document}
Index: src/tex2lyx/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/tex2lyx/ChangeLog,v
retrieving revision 1.4
diff -u -p -r1.4 ChangeLog
--- src/tex2lyx/ChangeLog 11 Feb 2003 13:56:50 - 1.4
+++ src/tex2lyx/ChangeLog 11 Feb 2003 15:47:59 -
@@ -1,5 +1,12 @@
2003-02-11 Angus Leeming [EMAIL PROTECTED]
+ * tex2lyx.C (handle_opt): prevent infinite loop if opts is empty.
+ (handle_package): new function, factoring code out of Parser::parse.
+ (trim): copied across from support/lstrings.C
+ (Parser::parse): handle '\usepackage{foo, bar}'.
+
+2003-02-11 Angus Leeming [EMAIL PROTECTED]
+
* .cvsignore: new file.
2003-02-10 Angus Leeming [EMAIL PROTECTED]
Index: src/tex2lyx/tex2lyx.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/tex2lyx/tex2lyx.C,v
retrieving revision 1.4
diff -u -p -r1.4 tex2lyx.C
--- src/tex2lyx/tex2lyx.C 11 Feb 2003 13:56:50 - 1.4
+++ src/tex2lyx/tex2lyx.C 11 Feb 2003 15:47:59 -
@@ -1,4 +1,3 @@
-
/** The .tex to .lyx converter
\author André Pönitz (2003)
*/
@@ -88,6 +87,24 @@ stackstring active_environments;
+string const trim(string const a, char const * p = )
+{
+ // lyx::Assert(p);
+
+ if (a.empty() || !*p)
+ return a;
+
+ string::size_type r = a.find_last_not_of(p);
+ string::size_type l = a.find_first_not_of(p);
+
+ // Is this the minimal test? (lgb)
+ if (r == string::npos l == string::npos)
+ return string();
+
+ return a.substr(l, r - l + 1);
+}
+
+
void split(string const s, vectorstring result, char delim)
{
istringstream is(s);
@@ -111,6 +128,9 @@ string join(vectorstring const input
void handle_opt(vectorstring opts, char const ** what, string target)
{
+ if (opts.empty())
+ return;
+
for ( ; what; ++what) {
vectorstring::iterator it = find(opts.begin(), opts.end(), *what);
if (it != opts.end()) {
@@ -131,6 +151,38 @@ void handle_ert(ostream os, string con
}
+void handle_package(string const name, string const options)
+{
+ if (name == a4wide) {
+ h_papersize = a4;
+ h_paperpackage = widemarginsa4;
+ } else if (name == ae)
+ h_fontscheme = ae;
+ else if (name == aecompl)
+ h_fontscheme = ae;
+ else if (name == amsmath)
+ h_use_amsmath = 1;
+ else if (name == amssymb)
+ h_use_amsmath = 1;
+ else if (name == babel)
+ ; // ignore this
+ else if (name == fontenc)
+ ; // ignore this
+ else if (name == inputenc)
+ h_inputencoding = options;
+ else if (name == makeidx)
+ ; // ignore this
+ else if (name == verbatim)
+ ; // ignore this
+ else {
+ if (options.size())
+ h_preamble += \\usepackage[ + options + ]{ + name + }\n;
+ else
+ h_preamble += \\usepackage{ + name + }\n;
+ }
+}
+
+
string wrap(string const cmd, string const str)
{
return OPEN + cmd + ' ' + str + CLOSE;
@@ -811,32 +863,16 @@ string Parser::parse(unsigned flags, mod
else if (t.cs() == usepackage) {
string const options = getArg('[', ']');
string const name = getArg('{', '}');
- if (name == a4wide) {
-h_papersize = a4;
-h_paperpackage = widemarginsa4;
- } else if (name == ae)
-h_fontscheme = ae;
- else if (name == aecompl)
-h_fontscheme = ae;
- else if (name == amsmath)
-h_use_amsmath = 1;
- else if (name == amssymb)
-h_use_amsmath = 1;
- else if (name == babel)
-; // ignore this
- else if (name == fontenc)
-; // ignore this
- else if (name == inputenc)
-h_inputencoding = options;
- else if (name == makeidx)
-; // ignore this
- else if (name == verbatim)
-; // ignore this
- else {
-if (options.size())
- h_preamble += \\usepackage[ + options + ]{ + name + }\n;
-else
- h_preamble += \\usepackage{ + name + }\n;
+ if (options.empty() name.find(',')) {
+vectorstring vecnames;
+split(name, vecnames, ',');
+vectorstring::const_iterator it = vecnames.begin();
+vectorstring::const_iterator end = vecnames.end();
+for (; it != end; ++it) {
+ handle_package(trim(*it), string());
+
