Re: Sorting and POTFILES.in
On Tue, Feb 11, 2003 at 04:42:38PM +0100, Jean-Marc Lasgouttes wrote: 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... Why? Can't this be used as instead of the 'sort | uniq' you need? Andre setstring seen; Does the standard offer guarrantees about the order in which these things will be given by the iterator? Sorted by operator(string,string) unless specified otherwise if I am not mistaken. Note that _this_ is irrelevant as it is not used for sorting but just to determine whether we currently look at a duplicate. If so, it is swallowed, if not, the current string is echoed to cout. 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: tex2lyx
On Tue, Feb 11, 2003 at 03:52:31PM +, Angus Leeming wrote: 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...). You are big enough to apply this by yourself, aren't you? ;-) Andre', hoping that you won't recognize the pattern (preview, tex2lyx, ...) -- 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, 11 Feb 2003, Alfredo Braunstein wrote: But you have 'real' shorcuts for that, i.e. keyboard bindings of lfuns. I agree that bindings could be shown on the menu, though. What's an lfun? I've seen this lots of times now ?lyx-function /Christian -- Christian Ridderström http://www.md.kth.se/~chr
Re: Sorting and POTFILES.in
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: Lars sorted. Lars sorting function and locale decides sorting order. I stand corrected, then. So, lars, would you be OK with replacing sort -f -n with a plain sort? I do not understand why you used -n actually. JMarc
Re: Sorting and POTFILES.in
Andre == Andre Poenitz [EMAIL PROTECTED] writes: Andre On Tue, Feb 11, 2003 at 04:42:38PM +0100, Jean-Marc Lasgouttes Andre wrote: This could be solved in twelve lines or so in any Andre language that has map Which is irrelevant to our problem, probably but... Andre Why? Can't this be used as instead of the 'sort | uniq' you Andre need? This is a command used in a makefile. If we write a C++ program everytime someone has to think more than 30 seconds about a shell command, we are soon going to have problems. JMarc
Re: tex2lyx
On Tuesday 11 February 2003 3:54 pm, Andre Poenitz wrote: On Tue, Feb 11, 2003 at 03:52:31PM +, Angus Leeming wrote: 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...). You are big enough to apply this by yourself, aren't you? ;-) Nope! There's a girl I know who thinks I regress with each passing day ;-) Andre', hoping that you won't recognize the pattern (preview, tex2lyx, ...) ;-) You've let the cat out of the bag now. I know your game and am not playing anymore. A
Re: Sorting and POTFILES.in
On Tue, Feb 11, 2003 at 04:56:17PM +0100, Jean-Marc Lasgouttes wrote: Andre Why? Can't this be used as instead of the 'sort | uniq' you Andre need? This is a command used in a makefile. If we write a C++ program everytime someone has to think more than 30 seconds about a shell command, we are soon going to have problems. Maybe. But we spent already more than 30 seconds on that shell command. Ok. I bite: Is: `$^' The names of all the prerequisites, with spaces between them. For prerequisites which are archive members, only the member named is used (*note Archives::). A target has only one prerequisite on each other file it depends on, no matter how many times each file is listed as a prerequisite. So if you list a prerequisite more than once for a target, the value of `$^' contains just one copy of the name. portable? If so, one could probably use make itself to remove the duplicates. 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: Sorting and POTFILES.in
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: | Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: | | Lars sorted. | | Lars sorting function and locale decides sorting order. | | I stand corrected, then. | | So, lars, would you be OK with replacing sort -f -n with a plain | sort? I do not understand why you used -n actually. Me neither... I probably thought that it would help. -- Lgb
Re: shorcut automatization
Christian Ridderström wrote: On Tue, 11 Feb 2003, Alfredo Braunstein wrote: But you have 'real' shorcuts for that, i.e. keyboard bindings of lfuns. I agree that bindings could be shown on the menu, though. What's an lfun? I've seen this lots of times now ?lyx-function /Christian See src/commandtags.h. The lfun enums tell the dispatch methods what to do with a particular string. They are mapped to identifying strings in src/LyXAction.C so that you can type 'insert-citation foo' in the minibuffer and something happens. -- Angus
Re: shorcut automatization
On Tue, 11 Feb 2003, Angus Leeming wrote: Christian Ridderström wrote: On Tue, 11 Feb 2003, Alfredo Braunstein wrote: But you have 'real' shorcuts for that, i.e. keyboard bindings of lfuns. I agree that bindings could be shown on the menu, though. What's an lfun? I've seen this lots of times now ?lyx-function /Christian See src/commandtags.h. The lfun enums tell the dispatch methods what to do with a particular string. They are mapped to identifying strings in src/LyXAction.C so that you can type 'insert-citation foo' in the minibuffer and something happens. Thanks... since this was a bit above and beyound what a normal user would be intersted in, I just put the answer here: http://ev-en.org/wiki/moin.cgi/LyxDevelFAQ /Christian -- Christian Ridderström http://www.md.kth.se/~chr
Re: Screenshots
Jean-Marc Lasgouttes wrote: Thanks, I converted this to real php3 files (including start.php3/end.php3) and commited. Now, let's look at the lgt. Sorry, I didn't know that that was needed. Actually, I used the existing screenshots page and just replaced the images. Jürgen.
wheeljump
This has been in my pening queue for a month. Can someone with a mouse wheel try it out and confirm that it's an improvement? -- Angus Index: lyx-devel-1_3_X//src/ChangeLog === RCS file: /cvs/lyx/lyx-devel/src/ChangeLog,v retrieving revision 1.1009 diff -u -r1.1009 ChangeLog --- lyx-devel-1_3_X//src/ChangeLog 2003/01/09 14:31:23 1.1009 +++ lyx-devel-1_3_X//src/ChangeLog 2003/01/09 19:09:57 @@ -1,3 +1,7 @@ +2003-01-08 Michael Schmitt [EMAIL PROTECTED] + +* Clarify the meaning of wheel mouse jump + 2003-01-06 Jean-Marc Lasgouttes [EMAIL PROTECTED] * lyxfunc.C (getStatus): fix disabling of cut/paste of cells in a Index: lyx-devel-1_3_X//src/lyxrc.C === RCS file: /cvs/lyx/lyx-devel/src/lyxrc.C,v retrieving revision 1.138 diff -u -r1.138 lyxrc.C --- lyx-devel-1_3_X//src/lyxrc.C 2003/01/06 14:02:21 1.138 +++ lyx-devel-1_3_X//src/lyxrc.C 2003/01/09 19:10:02 @@ -197,7 +197,7 @@ dpi = 75; // Because a screen typically is wider than a piece of paper: zoom = 150; - wheel_jump = 100; + wheel_jump = 5; // Default LaTeX font size: font_sizes[LyXFont::SIZE_TINY] = 5.0; font_sizes[LyXFont::SIZE_SCRIPT] = 7.0; @@ -2124,7 +2124,7 @@ break; case RC_WHEEL_JUMP: - str = _(The wheel movement factor (for mice with wheels or five button mice).); + str = _(The number of lines that are scrolled by mice with wheels or five button mice.); break; case RC_CONVERTER:
Re: lyx graphical tour
Jean-Marc Lasgouttes wrote: Juergen http://omnibus.uni-freiburg.de/~spitzmue/lgt-1.0.tar.gz Are you sure this is the right URL? Try again please Jürgen.
Re: lyx graphical tour
Juergen == Juergen Spitzmueller [EMAIL PROTECTED] writes: Juergen Jean-Marc Lasgouttes wrote: Juergen http://omnibus.uni-freiburg.de/~spitzmue/lgt-1.0.tar.gz Are you sure this is the right URL? Juergen Try again please It seems to work. Thanks JMarc
HELP! I can't get the *%^% website to accept lgt!
I have made some weak attempts at inegrating Juergen's new lgt to the main site. I have rewritten everything as nice php with start/end et al, but I am finally stopped by the fact that the design cannot accept three levels of subdirs. So what shall I do? Where should about/lgt/lgt.php3 go? Should I put the lgt*.php3 files in about/ and keep the image files in about/lgt? Before I do that, I'd appreciate better ideas. I guess there is not much hope of having a 3rd level of menus for navigating inside the lgt, but that is probably OK for now. Ideas? Everything has been commited in www-user/about/lgt, but nothing points to it yet. JMarc
Re: HELP! I can't get the *%^% website to accept lgt!
Jean-Marc Lasgouttes wrote: I have made some weak attempts at inegrating Juergen's new lgt to the main site. I have rewritten everything as nice php with start/end et al, but I am finally stopped by the fact that the design cannot accept three levels of subdirs. So what shall I do? Where should about/lgt/lgt.php3 go? Should I put the lgt*.php3 files in about/ and keep the image files in about/lgt? Before I do that, I'd appreciate better ideas. I guess there is not much hope of having a 3rd level of menus for navigating inside the lgt, but that is probably OK for now. Ideas? Everything has been commited in www-user/about/lgt, but nothing points to it yet. JMarc Why not move lgt into the top level dir? -- Angus
Re: HELP! I can't get the *%^% website to accept lgt!
Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus Why not move lgt into the top level dir? I thought about it, but before moving things around in cvs, how would you organize the menus in the sidebar? As it is now? JMarc
Re: HELP! I can't get the *%^% website to accept lgt!
On Tuesday 11 February 2003 6:41 pm, Jean-Marc Lasgouttes wrote: Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus Why not move lgt into the top level dir? I thought about it, but before moving things around in cvs, how would you organize the menus in the sidebar? As it is now? Yes. The logical structure of the site to the user need bear no relation to its physical layout. That's up to our discretion. You should create a redirection page from the old lgt.html to the new lgt.php3 though, or we'll be guilty of the spurious generation of broken links horror. Angus
Controller cleanup ---- a possible plan.
I thought I'd see if I could make some progress with my planned clean-up of
the controllers. The getting rid of inset* that I mentioned yesterday.
Unfortunately, I'm stuck and would value some advice.
Pressing (say) a citation inset triggers a call to InsetCitation::edit,
which in turn calls
bv-owner()-getDialogs().showCitation(this);
The inset* is passed to the frontends and stored there. Once the user has
finished modifying the data in the dialog and pressed Ok, the inset is
modified in the frontend with:
void ControlCommand::applyParamsToInset()
{
inset()-setParams(params());
bufferview()-updateInset(inset(), true);
}
What I'd like to do is call lyxfunc().dispatch to modify the inset and
update the bufferview if it sees fit. However, I don't want to store an
inset * in the frontend, so am having difficulty working out how to apply
the modified params to the right inset.
One idea makes use of the fact that we allow only one dialog of a particular
kind to be open in each LyXView. We could have
class LyXView {
public:
void showDialog(string const name, inset * inset) {
ostringstream data;
inset.write(data);
if (getDialogs().show(name, data))
openedDialog(name) = inset;
}
void hideDialog(string const name) {
if (getDialogs().hide(name))
openedDialog(name) = 0;
}
inset * getOpenDialog(string const name) {
return openedDialog(name);
}
private:
map(string, inset *) openedInsets;
};
void InsetCitation::edit(BufferView * bv, int, int, mouse_button::state)
{
bv-owner()-showDialog(citation, this);
}
This would also allow the dispatch method to retrieve the open inset when it
is passed data and apply it as it chooses. The frontends would need know
nothing about the insets themselves. Ie, if
LyXView::getOpenDialog(citation) returns an inset, apply the data to it.
If it returns a null pointer, create a new inset at the current cursor
position.
Does this sound like a viable plan?
--
Angus
prosper2 documentclass with Lyx 1.3.0
Hello,
I just installed Lyx 1.3.0 (love the Qt GUI!), and am having problems
with a Prosper slide presentation with prosper.layout by Dekel Tsur,
which worked with earlier versions of LyX. The problem is with figure
floats. I now get only one option on the menu for figure floats (package
figureflt), and they do not work (there is no figure). Opening older
presentations, which use regular figure floats, produces Tex files with
the following problematic macro definitions which do not compile:
%% LyX specific LaTeX commands.
%% Bold symbol macro for standard LaTeX users
\newcommand{\boldsymbol}[1]{\mbox{\boldmath $#1$}}
\floatstyle{}
\newfloat{}{}{}
\floatname{}{}
I am not sure where the problem is and would appreciate any clues.
Thanks,
Aleksandar
--
__
Aleksandar Donev
Complex Materials Theory Group (http://cherrypit.princeton.edu/)
Princeton Materials Institute Program in Applied and Computational Mathematics
@ Princeton University
Address:
419 Bowen Hall, 70 Prospect Avenue
Princeton University
Princeton, NJ 08540-5211
E-mail: [EMAIL PROTECTED]
WWW: http://atom.princeton.edu/donev
Phone: (609) 258-2775
Fax: (609) 258-6878
__
Re: A question about lengths and reLyX
Am Dienstag, 11. Februar 2003 12:00 schrieb Angus Leeming: 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.) While you are at it: 4,5cm (with comma) is also valid latex (learned that the other day when I fed some more old tex files to reLyX. Georg
Re: prosper2 documentclass with Lyx 1.3.0
On Tue, Feb 11, 2003 at 03:37:22PM -0500, Aleksandar Donev wrote:
I just installed Lyx 1.3.0 (love the Qt GUI!), and am having problems
with a Prosper slide presentation with prosper.layout by Dekel Tsur,
which worked with earlier versions of LyX. The problem is with figure
floats. I now get only one option on the menu for figure floats (package
figureflt), and they do not work (there is no figure). Opening older
presentations, which use regular figure floats, produces Tex files with
the following problematic macro definitions which do not compile:
%% LyX specific LaTeX commands.
%% Bold symbol macro for standard LaTeX users
\newcommand{\boldsymbol}[1]{\mbox{\boldmath $#1$}}
\floatstyle{}
\newfloat{}{}{}
\floatname{}{}
I am not sure where the problem is and would appreciate any clues.
You need to add
Input stdfloats.inc
Input stdcounters.inc
to prosper.layout
Re: prosper2 documentclass with Lyx 1.3.0
Dekel Tsur [EMAIL PROTECTED] writes:
| On Tue, Feb 11, 2003 at 03:37:22PM -0500, Aleksandar Donev wrote:
| I just installed Lyx 1.3.0 (love the Qt GUI!), and am having problems
| with a Prosper slide presentation with prosper.layout by Dekel Tsur,
| which worked with earlier versions of LyX. The problem is with figure
| floats. I now get only one option on the menu for figure floats (package
| figureflt), and they do not work (there is no figure). Opening older
| presentations, which use regular figure floats, produces Tex files with
| the following problematic macro definitions which do not compile:
|
| %% LyX specific LaTeX commands.
| %% Bold symbol macro for standard LaTeX users
| \newcommand{\boldsymbol}[1]{\mbox{\boldmath $#1$}}
|
| \floatstyle{}
| \newfloat{}{}{}
| \floatname{}{}
|
| I am not sure where the problem is and would appreciate any clues.
|
| You need to add
|
| Input stdfloats.inc
| Input stdcounters.inc
But there seems to also be a bug there, in that we should not output
empty floatstyle, newfloat, floatname... ever...
--
Lgb
[PATCH] add support for elsevier elsart.cls
The attached patch adds support for the elsart.cls latex class. It is
based on Herbert's class (with a couple fixes of my own) and the
patch to support it has a similar effect to Herbert's.
This will get included in 1.3.1 if
1/ it gets a good testing. I do not have an elsart.cls here to try to
typeset files. Also, what floats should be defined in elsart?
2/ I get some minimal doc to include in LaTeXConfig:lyx:in (at least)
and Extended.lyx (optional).
JMarc
Index: lib/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/ChangeLog,v
retrieving revision 1.363.2.5
diff -u -r1.363.2.5 ChangeLog
--- lib/ChangeLog 11 Feb 2003 14:31:21 - 1.363.2.5
+++ lib/ChangeLog 11 Feb 2003 23:04:27 -
@@ -1,3 +1,9 @@
+2003-02-11 Jean-Marc Lasgouttes [EMAIL PROTECTED]
+
+ * templates/elsart.lyx:
+ * layouts/elsart.layout: new class, adapted from work of Herbert
+ Voss and Rod Pinna
+
2003-02-11 Angus Leeming [EMAIL PROTECTED]
* BasicLyX.pm: enable reLyX to recognise natbib citations.
Index: lib/layouts/elsart.layout
===
RCS file: lib/layouts/elsart.layout
diff -N lib/layouts/elsart.layout
--- /dev/null 1 Jan 1970 00:00:00 -
+++ lib/layouts/elsart.layout 11 Feb 2003 23:04:30 -
@@ -0,0 +1,474 @@
+#% Do not delete the line below; configure depends on this
+# \DeclareLaTeXClass[elsart,amssymb.sty]{article (elsevier)}
+# Author: Rod Pinna [EMAIL PROTECTED]
+# The Elsevier doc style also duplicates the theorem
+# environments used by the AMS. The definitions here have been
+# mainly taken from the amsmath.inc file, from lyx-1.0.2, by
+# David L. Johnson and Jean-Marc Lasgouttes. Some modifications
+# have been made.
+#
+# The Elsevier style *does not* implement the starred versions
+# of these environments, so they are not supported by this layout.
+# There are also a few AMS environments not impletemented by Elsevier,
+# so they are not included either.
+#
+# Version 1.0 19990506 R. Pinna Inital version
+# modified 2002-04-02 Herbert Voss [EMAIL PROTECTED]
+# for use of BeginTitle/EndTitle
+# modified 2003-03-11 JMarc for use of TitleLatexType/TitleLatexName
+
+# General textclass parameters
+Columns1
+Sides 2
+PageStyle headings
+MaxCounter Counter_Subsection
+
+
+ClassOptions
+# FontSizedefault # controlled by class
+End
+
+# elsart does not use the plain old \maketitle
+TitleLatexType Environment
+TitleLatexName frontmatter
+
+DefaultFont
+ Family Roman
+ Series Medium
+ ShapeUp
+ Size Normal
+ ColorNone
+EndFont
+
+
+Style Standard
+ LatexNamedummy
+ LatexTypeParagraph
+ Margin Static
+ ParIndentMM
+ ParSkip 0.4
+ ParSep 0.4
+ TopSep 1.0
+ BottomSep1.0
+ AlignBlock
+ AlignPossible Block, Left, Right, Center
+ LabelTypeNo_Label
+End
+
+
+Style Keywords
+ LatexNamekeyword
+ LatexTypeEnvironment
+ Margin Static
+ ParIndentMM
+ InTitle 1
+ ParSkip 0.4
+ ParSep 0.4
+ TopSep 1.0
+ BottomSep1.0
+ AlignBlock
+ AlignPossible Block, Left, Right, Center
+ LabelTypeNo_Label
+Font
+Color blue
+EndFont
+End
+
+
+# Load standard defs, as most of the
+# Elsevier stuff seems the same.
+Input stdsections.inc
+Input stdstarsections.inc
+Input stdlists.inc
+Input stdstruct.inc
+Input stdlayouts.inc
+Input stdfloats.inc
+Input stdcounters.inc
+
+
+# Title style definition
+Style Title
+ Margin Static
+ LatexTypeCommand
+ InTitle 1
+ LatexNametitle
+ NextNoIndent 1
+ ParSkip 0.4
+ TopSep 1.3
+ BottomSep0.7
+ ParSep 0.7
+ AlignCenter
+ LabelTypeNo_Label
+# standard font definition
+ Font
+Family Sans
+Series Bold
+Size Largest
+ EndFont
+End
+
+# Author style definition
+Style Author
+ Margin Static
+ LatexTypeCommand
+ InTitle 1
+ LatexNameauthor
+ NextNoIndent 1
+ ParSkip 0.4
+ TopSep 0.7
+ BottomSep0.7
+ ItemSep 0
+ ParSep 0
+ AlignCenter
+ AlignPossibleCenter
+ # standard font definition
+ Font
+Series Bold
+ EndFont
+End
+
+# Author Adress
+Style Author_Address
+ Margin Static
+ LatexTypeCommand
+ InTitle 1
+ LatexNameaddress
+ AlignCenter
+ AlignPossibleCenter
+ Labeltype Static
+ LabelString Address:
+ LabelFont
+Shape Italic
+ EndFont
+End
+
+Style
Re: [PATCH] add support for elsevier elsart.cls
I'll give it a try, and have a go at documentation. When I first put in the old (bad) form of this, I had some docs too, so I'll have a look at updating those. Er, silly question, but what is the easiest way to apply this. For small patches I've used emacs, but this looks a little more imvolved to me... Thanks, Rod On Wed, 12 Feb 2003, Jean-Marc Lasgouttes wrote: The attached patch adds support for the elsart.cls latex class. It is based on Herbert's class (with a couple fixes of my own) and the patch to support it has a similar effect to Herbert's. This will get included in 1.3.1 if 1/ it gets a good testing. I do not have an elsart.cls here to try to typeset files. Also, what floats should be defined in elsart? 2/ I get some minimal doc to include in LaTeXConfig:lyx:in (at least) and Extended.lyx (optional). JMarc _ rod | Beneath the waves, the waves / That's where I will be / | I'm going to see the cow beneath the sea. | They Might Be Giants, Lincoln
Re: shorcut automatization
On Tue, 11 Feb 2003, Alfredo Braunstein wrote: 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. I'm surprised that noone has mentioned the _existing_ shortcut creation tool which is included in the source tree at: development/tools/scgen.pl Such tools are good for initial creation of a dialog but as others have pointed out they are likely to change allocations once a dialog has been reordered (for tab ordering purposes) or extended. Allan. (ARRae)
Re: shorcut automatization
On Tue, 11 Feb 2003, John Levon wrote: On Tue, Feb 11, 2003 at 11:59:28AM +0100, Lars Gullik Bj?nnes wrote: [...] | I have never been able to use that interface, and it buys us precisely | nothing, and costs a lot. Poor John, failed at Emacs but rules with vi. When are you vi guys going to get your acts together and put a vi-style command interface or are you quietly admitting defeat here also. :P 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. Can't Qt create a dialog as part of a canvas? That is, can't you just put everything on a scrolling-canvas instead of a separate popup dialog box? (which all the Qt/KDE apps I remember using seem to always want to make modal) Then the only difference is the stuff that is covered up or blocked by silly dialogs -- in fact it seems that since Qt can float toolbars the same could effectively be done with dialogs -- the user can choose to pull them out of the workarea and decorate the rest of their screen with them if they want to (or vice versa). Allan. (ARRae)
Re: HELP! I can't get the *%^% website to accept lgt!
On Tue, 11 Feb 2003, Angus Leeming wrote: On Tuesday 11 February 2003 6:41 pm, Jean-Marc Lasgouttes wrote: Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus Why not move lgt into the top level dir? I thought about it, but before moving things around in cvs, how would you organize the menus in the sidebar? As it is now? Yes. The logical structure of the site to the user need bear no relation to its physical layout. That's up to our discretion. You should create a redirection page from the old lgt.html to the new lgt.php3 though, or we'll be guilty of the spurious generation of broken links horror. Sorry but this won't work properly because of the way we create the navbar at present. Better to move /about/lgt/ to /lgt/ I also want to rewrite the subdir handling code but haven't gotten around to it yet. I'll make it a priority next week. Allan. (ARRae)
Re: [PATCH] add support for elsevier elsart.cls
patch -p0 diff-file seems to work, so please, ignore me :) Rod On Wed, 12 Feb 2003, Rod Pinna wrote: I'll give it a try, and have a go at documentation. When I first put in the old (bad) form of this, I had some docs too, so I'll have a look at updating those. Er, silly question, but what is the easiest way to apply this. For small patches I've used emacs, but this looks a little more imvolved to me... Thanks, Rod On Wed, 12 Feb 2003, Jean-Marc Lasgouttes wrote: The attached patch adds support for the elsart.cls latex class. It is based on Herbert's class (with a couple fixes of my own) and the patch to support it has a similar effect to Herbert's. This will get included in 1.3.1 if 1/ it gets a good testing. I do not have an elsart.cls here to try to typeset files. Also, what floats should be defined in elsart? 2/ I get some minimal doc to include in LaTeXConfig:lyx:in (at least) and Extended.lyx (optional). JMarc _ rod | Beneath the waves, the waves / That's where I will be / | I'm going to see the cow beneath the sea. | They Might Be Giants, Lincoln _ rod | Beneath the waves, the waves / That's where I will be / | I'm going to see the cow beneath the sea. | They Might Be Giants, Lincoln
Re: [PATCH] changes: LColor
On Tue, 11 Feb 2003, José Matos wrote: 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. ;-) Please tell all. I might have got a colour wrong somewhere. Allan. (ARRae)
Re: tex2lyx
On Tue, 11 Feb 2003, Angus Leeming wrote: On Tuesday 11 February 2003 3:54 pm, Andre Poenitz wrote: On Tue, Feb 11, 2003 at 03:52:31PM +, Angus Leeming wrote: 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...). You are big enough to apply this by yourself, aren't you? ;-) Nope! There's a girl I know who thinks I regress with each passing day ;-) Better bring that wedding day forward a few months then. ;-) Allan. (ARRae)
Re: Angus, Asger, Jean-Marc...! (was: Re: [patch]: pass $...$ and$$...$$ through reLyX unchanged)
On Fri, 7 Feb 2003, Andre Poenitz wrote: Currently it looks like neither Asger, Angus and John could come if we insisted June 20th. Currently I have (5 - ok, 0 - not ok): I think I'm going to be a 0 for all dates this year unless I win the lottery. I am however making good progress on my thesis -- but I have a cunning plan to get me a new distraction this Friday. Allan. (ARRae)
Re: A question about lengths and reLyX
On Tue, Feb 11, 2003 at 09:47:13PM +0100, Georg Baum wrote: Am Dienstag, 11. Februar 2003 12:00 schrieb Angus Leeming: 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.) While you are at it: 4,5cm (with comma) is also valid latex (learned that the other day when I fed some more old tex files to reLyX. And I believe '4.5 Cm' and '4.5 cM' are valid as well... 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: Angus, Asger, Jean-Marc...! (was: Re: [patch]: pass $...$ and $$...$$ through reLyX unchanged)
On Wed, Feb 12, 2003 at 02:14:32PM +1000, Allan Rae wrote: I think I'm going to be a 0 for all dates this year unless I win the lottery. Is that the price of spending the whole life upside down? I wonder whether RyanAir will go beyond Europe some time. Yesterday I've seen Frankfurt-Glasgow for 7 EUR... 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] add support for elsevier elsart.cls
Looks good, except for a few minor points:
\ead - this isn't mentioned in the elsevier instructions, and seems to
have been introduced by Herbert. I'm not sure what it is meant to do, but
doesn't work with the current layout file.
\thanks - in the Elsevier style, thanks should be tied to the author with
something like
\author{Bob\thanksref{ABC}}
then thanks goes
\thanks[ABC]{This is all the thanks I get}
I have no idea if this is possible in Lyx at the moment.
Also attached is a draft for some docs. The config text is in the file, as
I (again) have no idea what format you need for it.
For good measure, I've class file as well. If you want the docs, let me
know. It's 165k gzipped.
Rod
_
rod | Beneath the waves, the waves / That's where I will be /
| I'm going to see the cow beneath the sea.
| They Might Be Giants, Lincoln
elsevier_doc.lyx.gz
Description: Binary data
elsart.cls.gz
Description: Binary data
Re: Angus, Asger, Jean-Marc...! (was: Re: [patch]: pass $...$ and$$...$$ through reLyX unchanged)
On Wed, 12 Feb 2003, Andre Poenitz wrote: On Wed, Feb 12, 2003 at 02:14:32PM +1000, Allan Rae wrote: I think I'm going to be a 0 for all dates this year unless I win the lottery. Is that the price of spending the whole life upside down? No the price for spending my life upside down is that it takes about 7 hours of flying in a 747 to leave the Australian land-mass behind and be flying over water (toward Singapore or Hong Kong) -- and no, the wheels are not in contact with terra firma during those 7 hours. About 7.5hrs to Singapore or 8.5hrs to Hong Kong (I think -- never been that way before). Then 12.5hrs Singapore to Milan or maybe Munich a little longer to Frankfurt. Actually the main reason for the 0 rating is that I've quit my job and am surviving on what little savings I have in an effort to get this thesis finished without too many distractions. I wonder whether RyanAir will go beyond Europe some time. Yesterday I've seen Frankfurt-Glasgow for 7 EUR... How much extra for a seat? And how much on top of that for a seat belt? And how much more on top of that for a pressurised cabin? Allan. (ARRae)
Re: Angus, Asger, Jean-Marc...! (was: Re: [patch]: pass $...$ and $$...$$ through reLyX unchanged)
On Wed, Feb 12, 2003 at 04:36:43PM +1000, Allan Rae wrote: I wonder whether RyanAir will go beyond Europe some time. Yesterday I've seen Frankfurt-Glasgow for 7 EUR... How much extra for a seat? And how much on top of that for a seat belt? And how much more on top of that for a pressurised cabin? I believe these are included. I still don't know how they earn any money and I've never actually tried RyanAir which is aid to be the cheapest. Maybe being profitable not the reason of the exercise. My last trip a few weeks ago was Berlin-London for ~50 EUR (one way, including taxes) with a company called buzz and it was ok. No food on board (well, there was, but you would have to pay extra) but I really don't care about that for a two hours journey... 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: Angus, Asger, Jean-Marc...! (was: Re: [patch]: pass $...$ and$$...$$ through reLyX unchanged)
On Wed, 12 Feb 2003, Andre Poenitz wrote: My last trip a few weeks ago was Berlin-London for ~50 EUR (one way, including taxes) with a company called buzz and it was ok. No food on board (well, there was, but you would have to pay extra) but I really don't care about that for a two hours journey... That's about what we pay here for a similar length domestic flight (between capital cities -- Brisbane to Melbourne (usually 2hrs in a 767)). That's flying about half the length of the eastern seaboard of Australia -- just so you get some feel for the scale. Flying anywhere other than between capital cities the prices get much more hideous. Allan. (ARRae)
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} \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_cast(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
