Re: misc guii
On Wed, 18 Jul 2001, Angus Leeming wrote: Allan. (ARRae) Who feels retirement or at least a sabatical coming on. What's this? Are you feeling burnt out from writing a thesis or bored of LyX. Not enough thesis and too many LyX emails to read each day. Maybe I should do like Amir did and unsubscribe from lyx-devel and subscribe to the digest instead... hmmm... maybe procmail would be a better idea and filter out anything that doesn't mention me... What about that shoulder to lean on I've been relying on all this time. I'm not sure I can stand on my own two feet after all this time!!! I have a hundred and one different things I'd love to fix or break or whatever in LyX but my thesis really should get to be my first priority at some stage during my candidature. Doesn't mean I don't want to continue supporting the effort but I am wondering what is the best move at this point (five years into my PhD). Stuff like: finish my thesis versus fix up the guii class hierarchy? I finished my employment with the Uni two weeks ago (although I have another week or two of consulting that they want me for) and have only done LyX website and some hiking in that time. No thesis. No LDN. No code. I can pay rent and buy food until perhaps Christmas with my savings. But, then I need to work again and I know for a fact that in the two years of part/full time work I did until now I never got any useful work done on my thesis. So perhaps that should be a warning to other postgrads. Make the most of your scholarship while it lasts. I'll finish breaking www.devel.lyx.org before I bugger off (if I do) but if anyone out there wants to read LDN in future they might have to consider writing it themselves. I'll try once again to get an LDN written for next week but at present my back is not happy with me after I hurt it weight lifting. That was supposed to be helping strengthen my back so it was less likely to get hurt... ironic isn't it? Allan. (ARRae)
Re: Preference's Save/Apply button anomalities
On Thu, 19 Jul 2001, R. Lahaye wrote: Allan Rae wrote: On Wed, 18 Jul 2001, R. Lahaye wrote: I believe that the Save Apply button of the Preferences lights up or doesn't, when it should or shouldn't: 1) It doesn't when I type a new Backup path or LyXServer pipe in Inputs-Paths, but it should! If the path doesn't include existing directories this will fail. That is, if you enter /home/me/temp/lyx/ and /home/me/temp doesn't exist then the validity test will fail. What are the entries you are trying to use? And how much of those paths actually exists? Earlier I had set LyXServer-pipe to /home/lahaye/.lyx/pipe. When I then open the preferences dialog and manually change that into /home/lahaye/.lyx/mypipe (simply typing my infront of pipe), I cannot [Save] or [Apply] that change because both buttons are still disabled. This is not the correct behaviour to my opinion, since I have changed the pipe in a legitimate way. Or what do you think? In this example, I have to change (and change back) something else in order to enable the [Save/Apply] buttons to save my new LyXServer-pipe. Strange. 2) It does, when I select a line in the list of the LyX objects in Look Feel - Colors, although it shouldn't because I do not make any changes. This is a problem of the what is an input and what isn't variety we have had elsewhere. Problem of input? I don't understand. Talking about coding rather than user input. IMO, these fields of the dialog shouldn't be going anywhere near the input() function. Simply looking at the default top Object GUI background doesn't affect the [Save/Apply] buttons. So why then enable [Restore/Save/Apply] buttons when I LOOK AT the colour settings of (for example) latex text. That implies no changes at all (just looking!), so it should not enable the [Restore/Save/Apply] buttons. Only when I change one of the colour settings, I should be able to Save/Apply this change. Sure. If you haven't pressed Modify in the colour tab then you can't have changed anything. So Modify is argueably the only button there that should be calling the input() callback. Allan. (ARRae)
Re: Natbib announcement (and 666 inset gripes)
On 18-Jul-2001 Mike Ressler wrote: This is not a stunning example of WYSIWYM. Please, please, (Lars?) change the appearance back to the old behavior!!! I don't think this will happen. What will happen is that we will change the InsetERT to be inlined. What will NOT happen is that a inlined ERT inset breaks row, so this is really thought only for short stuff! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Might as well be frank, monsieur. It would take a miracle to get you out of Casablanca and the Germans have outlawed miracles. -- Casablanca
[gunix@telia.com] Feedback from www.lyx.org
Hello, I forwarded your message to the developpers list. JMarc Gunnar ([EMAIL PROTECTED]) entered the following feedback message on the LyX home page: Hello. I've always liked lyx, but now I must say that I do not like how the tables works in 1.1.6-fix2. To move the cursor between two adjecent boxes I have to press the arrowkey twice. WHY?? It was so much better in earlier versions.
Re: Natbib announcement (and 666 inset gripes)
On Thu, 19 Jul 2001, Juergen Vigna wrote: On 18-Jul-2001 Mike Ressler wrote: This is not a stunning example of WYSIWYM. Please, please, (Lars?) change the appearance back to the old behavior!!! I don't think this will happen. What will happen is that we will change the InsetERT to be inlined. What will NOT happen is that a inlined ERT inset breaks row, so this is really thought only for short stuff! I don't care what the underlying mechanism is (insets, fonts, etc.). I would like the _appearance_ to resemble the old style. Having it appear like a math inset would be fine. Maybe that is the model: an inlined ERT box and a display ERT box, for longer chunks of LaTeX code. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: misc guii
Priorities, priorities. I'd suggest that LyX is fun but that if you stop work on it, it'll magically continue on it's own happy course. Is the same true of a thesis? Unfortumately not. You've invested five years into this labour of love, but you'll get nothing tangible in return unless you finish it. So do as Amir did and finish it. Angus On Thursday 19 July 2001 07:55, Allan Rae wrote: On Wed, 18 Jul 2001, Angus Leeming wrote: Allan. (ARRae) Who feels retirement or at least a sabatical coming on. What's this? Are you feeling burnt out from writing a thesis or bored of LyX. Not enough thesis and too many LyX emails to read each day. Maybe I should do like Amir did and unsubscribe from lyx-devel and subscribe to the digest instead... hmmm... maybe procmail would be a better idea and filter out anything that doesn't mention me... What about that shoulder to lean on I've been relying on all this time. I'm not sure I can stand on my own two feet after all this time!!! I have a hundred and one different things I'd love to fix or break or whatever in LyX but my thesis really should get to be my first priority at some stage during my candidature. Doesn't mean I don't want to continue supporting the effort but I am wondering what is the best move at this point (five years into my PhD). Stuff like: finish my thesis versus fix up the guii class hierarchy? I finished my employment with the Uni two weeks ago (although I have another week or two of consulting that they want me for) and have only done LyX website and some hiking in that time. No thesis. No LDN. No code. I can pay rent and buy food until perhaps Christmas with my savings. But, then I need to work again and I know for a fact that in the two years of part/full time work I did until now I never got any useful work done on my thesis. So perhaps that should be a warning to other postgrads. Make the most of your scholarship while it lasts. I'll finish breaking www.devel.lyx.org before I bugger off (if I do) but if anyone out there wants to read LDN in future they might have to consider writing it themselves. I'll try once again to get an LDN written for next week but at present my back is not happy with me after I hurt it weight lifting. That was supposed to be helping strengthen my back so it was less likely to get hurt... ironic isn't it? Allan. (ARRae) -- Dr Angus Leeming Dept. of Bioengineering Imperial College London SW7 2BX Tel +44 (0) 20 7594 5186 Fax +44 (0) 20 7584 6897
Re: Re-implementing open-stuff [questions about insets and signals]
Angus == Angus Leeming [EMAIL PROTECTED] writes: I will also need a way of toggling or, alternatively, to know whether an inset is open or closed. Is that possible? JMarc Angus Does this cover it? Angus Angus, I tried yesterday to implement this stuff, and miserably failed :( It would help me a lot if you could do a sample implementation of this idea for one inset (pick the one you prefer :). Currently, I have implemented inset toggling for collapsable insets only. What remains to be done is 1/ implement it for insets which have a dialog 2/ see what to do with others, like math inset. What would be a reasonable open/close action? Toggle the math panel? JMarc
About allowed/forbidden insets
Hello, I have expanded the logic to handle disabling of inset insertion depending on context. Now the relevant menu entries are disabled when they should. Please check that this disabling occurs when it should. Something that seems suspicious to me is that floats are allowed in footnotes. Note that it is still possible to have a footnote in a float, which does not make sense for LaTeX. For that, one just has to copy/paste this footnote in the float. Insetead of trying to catch all the instances where this can happen, I propose to do the following: 1/ do not export these insets in LaTeX code (maybe replace by some text, like '[inset suppressed]' or whatever 2/ show on screen that the inset is disabled, probably by drawing a big red cross all over it. I'll try to experiment with that, and see if I can come up with something zhich is both easy and resistant to redraw problems. JMarc
Re: Natbib announcement (and 666 inset gripes)
On Thu, 19 Jul 2001, Juergen Vigna wrote: On 19-Jul-2001 Mike Ressler wrote: like a math inset would be fine. Maybe that is the model: an inlined ERT box and a display ERT box, for longer chunks of LaTeX code. That's exactly what we plan to do :) Excellent! Why didn't you just say so :-) Sorry if I sounded overly loud - I was just shocked by the appearance of those 666 boxes, and hadn't really followed the previous discussion closely enough to realize what was going on. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Re-implementing open-stuff [questions about insets and signals]
On Thursday 19 July 2001 09:56, Jean-Marc Lasgouttes wrote:
Angus == Angus Leeming [EMAIL PROTECTED] writes:
I will also need a way of toggling or, alternatively, to know
whether an inset is open or closed. Is that possible?
JMarc
Angus Does this cover it? Angus
Angus, I tried yesterday to implement this stuff, and miserably failed
:( It would help me a lot if you could do a sample implementation of
this idea for one inset (pick the one you prefer :).
Currently, I have implemented inset toggling for collapsable insets
only. What remains to be done is
1/ implement it for insets which have a dialog
2/ see what to do with others, like math inset. What would be a
reasonable open/close action? Toggle the math panel?
Aren't things as simple as this:
We want a member variable in the inset:
enum DialogStatus {
DIALOG_OPEN,
DIALOG_CLOSED
};
DialogStatus status;
I think that things will be cleanest if this variable is set by the dialog:
template class Inset, class Params
void ControlInsetInset, Params::hide()
{
if (params_) {
delete params_;
params_ = 0;
}
clearDaughterParams();
if (inset_) {
inset_.status = DIALOG_CLOSED;
inset_ = 0;
}
ih_.disconnect();
disconnect();
view().hide();
}
template class Inset, class Params
void ControlInsetInset, Params::connectInset(Inset * inset)
{
// If connected to another inset, disconnect from it.
if (inset_) {
ih_.disconnect();
inset_ = 0;
}
if (inset) {
inset_ = inset;
inset_.status = DIALOG_OPEN;
ih_ = inset-hideDialog.connect(
SigC::slot(this, ControlInset::hide));
}
connect();
}
Finally, we need a method Inset::toggle():
void Inset::toggle()
{
if (status == DIALOG_OPEN)
hideDialog();
else
emit();
}
Angus
Re: Nasty core dump with Lyx 1.1.6fix1
On Wed, Jul 18, 2001 at 06:42:18PM -0600, Fernando Pérez wrote: I found an ugly coredump with 1.1.6f1: if I have a simple lyx file with an included eps figure (in a float, it so happens), and try to export to latex with lyx --export latex file.lyx all goes well. However, if I use lyx -dbg anything --export latex file.lyx I get a nice coredump. I tried -dbg any to see how far it got, and this is Fixed.
Re: Natbib
On Thu, Jul 19, 2001 at 12:11:59AM +0200, Jean-Marc Lasgouttes wrote: And the good design is to have ALL packages in a dialog and be able what LaTeX code I want produce! AND this then should be honored by the LaTeX methods! In this dialog we would have a button to receck the LaTeX packages installed and also to save our actual will or to apply it only to the current session! Dekel I don't understand why you want this. Can you give an example ? The idea is that I should be able not to use natbib/amsfoo although they are present. I should also be able to do as if they were present even if they are not. So LyX discovers the available features, shows them to me, and I decide whether to keep these defaults. I still don't understand this. For example, what does lyx is supposed to do when you diable longtable ? Should it forbid you from inserting longtables ? What about longtables which were already present in the document ? If you don't want to use the longtable package then just don't use longtables in the document.
Patch: version build info added.
Hi, I thought it'll be useful to have an option lyx -version (or: lyx --version ) that will tell appropriate information on the system/build/compilation. This is very useful when reporting bug reports; once as executable, it is not so easy to find out how it was generated. Currently I have added this version and build info to my CVS-version, which outputs on my PC: -- $ lyx -version LyX 1.2.0cvs of Thu, Jan 11, 2001 FreeBSD 4.3-RELEASE i386 Compilers: | C CFlags: gcc (2.95.3) -g -O2 | C++ Flags: g++ (2.95.3) -g -O -fno-exceptions -W -Wall | Special flags: frontend-xforms warnings included-libsigc assertions | LD Flags: | Build time: Jul 19 2001 18:49:41 FrontEnd: | GUI lib : xforms/libxforms.la | LD flags: | Includes: | Libs: $ - I realize that this is not yet the most useful output, but it might be a setup to what it should become after the necessary improvements to lyx-devel/configure.in (currently around line 300). If this is considered to be a useful addition, please apply the attached patch. The following files are patched therein: lyx-devel/acconfig.h : "#undef BUILD_INFO" added lyx-devel/configure.in : build/version output added lyx-devel/lyx.man : "-version" described lyx-devel/src/lyx_main.C : "-version flag" described and added The main output part is in configure.in, and that needs some more tweeking to improve the quality of the output (some of which I don't know how to produce, e.g. FrontEnd version/XForms version). Regards, Rob. versionAddPatch.gz
Re: Silly Email address fix
Kayvan == Kayvan Sylvan [EMAIL PROTECTED] writes: Kayvan My bad. An internal Email address shows up in the ChangeLogs. Applied. JMarc
Re: Latex on Lyx
Sung-Kwan == Sung-Kwan Kim [EMAIL PROTECTED] writes: Sung-Kwan Hi Previously, I tried to use Scientific Workplace to write Sung-Kwan my paper. But I found an inconvenience that I had to keep Sung-Kwan using either mouse or short key to type mathematical Sung-Kwan expressions. Then I switched to Latex with an editor. It Sung-Kwan has passed three months since I tried to learn Latex. My Sung-Kwan question regarding Lyx is that is it possible to work with Sung-Kwan Latex commands directly on Lyx when I compose my paper ? In math editor mode, you can mostly use the latex macros directly (type \frac to get a fraction). However, you will have a adapt a bit your sequence of keys to get what you want inside LyX. JMarc
Re: Import ASCII as Verse
Garst == Garst R Reese [EMAIL PROTECTED] writes: Garst Jean-Marc Lasgouttes wrote: Garst == Garst R Reese [EMAIL PROTECTED] writes: Garst Yet another feature request. Verse gets e-mailed me as groups Garst of lines (stanzas) Garst Separated by a blank line. With the next stanza continuing. And how should this be changed? linebreaks between lines and paragraph breaks between stanzas? Hmmm... This means import as lines should keep line break as line breaks and change double line breaks to paragraph break. This seems reasonable, in fact. Why don't we do that always? I'd like to know what people think about that... Garst Yes. It also would have been nice if when in paragraph=verse, Garst an [enter] would have been interpreted as a line break and Garst C-[enter] as a paragraph break, but changing the behaviour now Garst is probably a bad idea. Yes, it is probably a very very bad idea :) If we do that, next time tou will ask that in verses footnote are output as tabulars and tabulars as footnotes... JMarc
Re: Re-implementing open-stuff [questions about insets and signals]
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus Aren't things as simple as this:
Angus We want a member variable in the inset:
Angus enum DialogStatus { DIALOG_OPEN, DIALOG_CLOSED }; DialogStatus
Angus status;
If you want. A bool would probably be fine too.
Angus I think that things will be cleanest if this variable is set by
Angus the dialog:
Angus template class Inset, class Params void ControlInsetInset,
Angus Params::hide() { if (params_) { delete params_; params_ = 0; }
Angus clearDaughterParams();
Angus if (inset_) { inset_.status = DIALOG_CLOSED; inset_ = 0; }
Angus ih_.disconnect(); disconnect(); view().hide(); }
If you say so... :)
Angus Finally, we need a method Inset::toggle(): void Inset::toggle()
Angus { if (status == DIALOG_OPEN) hideDialog(); else emit(); }
We already have the methods
void Inset::open(BufferView*, bool)
bool Inset::isOpen()
which should be enough. Currently they do something only for
collapsable inset, but I'd want to implement them for inset who have a
popup too. If you could show me some working code, I'd finish the
adaptation.
JMarc
Re: Natbib
On 19-Jul-2001 Dekel Tsur wrote: I still don't understand this. For example, what does lyx is supposed to do when you diable longtable ? Should it forbid you from inserting longtables ? What about longtables which were already present in the document ? If you don't want to use the longtable package then just don't use longtables in the document. What if you don't have all extra super truper latest packages installed on your actual machine but would like to be able to preview at least normal text? Just check of that feature in the dialog, the resulting LaTeX will not use that feature, and your able to preview the document (obviously not with that feature). So in your case all tables would be normal tabels and go over the height of one page, but I just don't care at the moment for this as I would like to have a printout of the document without this longtables and without the need of special features to say grammer-check on a printout. Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ I smell a wumpus.
Re: Re-implementing open-stuff [questions about insets and signa
On 19-Jul-2001 Jean-Marc Lasgouttes wrote: We already have the methods void Inset::open(BufferView*, bool) bool Inset::isOpen() which should be enough. Currently they do something only for collapsable inset, but I'd want to implement them for inset who have a popup too. If you could show me some working code, I'd finish the adaptation. What does this do if a collapsable inset has a dialog (InsetMinipage f.ex)? Then we say we're open and our dialog is open too? I would say we should split this! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Never eat more than you can lift. -- Miss Piggy
Re: Natbib announcement
On Wednesday, 18. July 2001 19:39, Angus Leeming wrote: Those willing to help save the CVS head repository from contamination with junk code should: cvs checkout -r BRANCH_NATBIB lyx-devel To get natbib support you'll need to set some parameters in the Document-Extra tab It should be obvious which ones! Hm, I really would like to test, but I can't get Natbib in. I did (without concept ;-) cvs checkout -r BRANCH_NATBIB lyx-devel make distclean ./autogen.sh ./configure ; make start lyx from the cvs directory. But there is no Natbib (still have the huge citation dialog and nothing in Document - Extra. I'm a CVS newbie, so any help is appreciated! Thanks, Jürgen.
Re: Natbib
On Thu, Jul 19, 2001 at 12:56:46PM +0200, Juergen Vigna wrote: What if you don't have all extra super truper latest packages installed on your actual machine but would like to be able to preview at least normal text? Just check of that feature in the dialog, the resulting LaTeX will not use that feature, and your able to preview the document (obviously not with that feature). Why do you need a dialog ? LyX should read the packages.lst file.
Re: Re-implementing open-stuff [questions about insets and signa
Juergen == Juergen Vigna [EMAIL PROTECTED] writes: Juergen On 19-Jul-2001 Jean-Marc Lasgouttes wrote: We already have the methods void Inset::open(BufferView*, bool) bool Inset::isOpen() which should be enough. Currently they do something only for collapsable inset, but I'd want to implement them for inset who have a popup too. If you could show me some working code, I'd finish the adaptation. Juergen What does this do if a collapsable inset has a dialog Juergen (InsetMinipage f.ex)? Then we say we're open and our dialog Juergen is open too? I would say we should split this! Good point. What I was trying to reproduce is the behaviour of 1.1.6, which nobody complained about :) The idea is that inset-toggle should be the keyboard equivalent of clicking on an inset. The example that you propose shows that our UI is bad: left-clicking on an inset brings up the popup if there is one, *except* if it is a collapsable inset. In this case, it expands the inset (which arguably is a way to edit it). Then the right-click to edit minipage properties is just weird. BTW, what is the keyboard shortcut which provides this feature? I surely hope we have one... JMArc
Re: Natbib
On 19-Jul-2001 Dekel Tsur wrote: On Thu, Jul 19, 2001 at 12:56:46PM +0200, Juergen Vigna wrote: What if you don't have all extra super truper latest packages installed on your actual machine but would like to be able to preview at least normal text? Just check of that feature in the dialog, the resulting LaTeX will not use that feature, and your able to preview the document (obviously not with that feature). Why do you need a dialog ? LyX should read the packages.lst file. Yes and that tells me that the package is not available and I'm not able to produce LaTeX code which includes that package, isn't it? Or do you propse to edit the packages.lst file by hand then? Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Term, holidays, term, holidays, till we leave school, and then work, work, work till we die. -- C.S. Lewis
Re: Re-implementing open-stuff [questions about insets and signa
On 19-Jul-2001 Jean-Marc Lasgouttes wrote: The example that you propose shows that our UI is bad: left-clicking on an inset brings up the popup if there is one, *except* if it is a collapsable inset. In this case, it expands the inset (which arguably Well make it better ;) is a way to edit it). Then the right-click to edit minipage properties is just weird. BTW, what is the keyboard shortcut which provides this feature? I surely hope we have one... Sure we have one, don't we?! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ If you would keep a secret from an enemy, tell it not to a friend.
Re: Re-implementing open-stuff [questions about insets and signa
Juergen == Juergen Vigna [EMAIL PROTECTED] writes: Juergen On 19-Jul-2001 Jean-Marc Lasgouttes wrote: The example that you propose shows that our UI is bad: left-clicking on an inset brings up the popup if there is one, *except* if it is a collapsable inset. In this case, it expands the inset (which arguably Juergen Well make it better ;) Well, I am looking for ideas about agood interface, right now... is a way to edit it). Then the right-click to edit minipage properties is just weird. BTW, what is the keyboard shortcut which provides this feature? I surely hope we have one... Juergen Sure we have one, don't we?! It seems that we don't. Tabulars have layout-tabular, but there does not seem to be anything for minipages. JMarc
buglet with insettext (collapsable insets?)
I know nobody cares about this kind of bug, but it be asign of something worse 1/ create a document with an empty open footnote. 2/ save it 3/ when going through the (empty) footnote, the document gets the (changed) status; this does not happen if there is text in the footnote. JMarc
Re: Re-implementing open-stuff [questions about insets and signa
On 19-Jul-2001 Jean-Marc Lasgouttes wrote: Juergen Sure we have one, don't we?! It seems that we don't. Tabulars have layout-tabular, but there does not seem to be anything for minipages. You'll make it, won't you ;) (btw.: I did know we don't have it) Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Household hint: If you are out of cream for your coffee, mayonnaise makes a dandy substitute.
RE: buglet with insettext (collapsable insets?)
On 19-Jul-2001 Jean-Marc Lasgouttes wrote: 3/ when going through the (empty) footnote, the document gets the (changed) status; this does not happen if there is text in the footnote. I'll have a look at this! BTW.: Find/Search actions do the same I'll have a look at that right now ;) Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ The purpose of Physics 7A is to make the engineers realize that they're not perfect, and to make the rest of the people realize that they're not engineers.
Re: Re-implementing open-stuff [questions about insets and signa
Juergen == Juergen Vigna [EMAIL PROTECTED] writes: Juergen On 19-Jul-2001 Jean-Marc Lasgouttes wrote: Juergen Sure we have one, don't we?! It seems that we don't. Tabulars have layout-tabular, but there does not seem to be anything for minipages. Juergen You'll make it, won't you ;) (btw.: I did know we don't have Juergen it) Making one is not a problem, but I'm looking for ideas on a convenient interface... JMarc
Re: Patch: version build info added.
R == R Lahaye [EMAIL PROTECTED] writes: R Hi, R I thought it'll be useful to have an option Rlyx -version (or: lyx --version ) R that will tell appropriate information on the R system/build/compilation. This is very useful when reporting bug R reports; once as executable, it is not so easy to find out how it R was generated. Looks like an excellent idea. A simpler solution would probably be to generate this data in a file that would be installed along with LyX. This way the information would be available even when LyX cannot be launched. JMarc
Re: mathed103.diff
On Thu, Jul 19, 2001 at 06:29:16AM +0200, Andre Poenitz wrote: The standard 'spreadsheet' rules for never deleting cells in their complexity may be elegant (and they are), but the flexibility to join/split/pad rows just by inserting or deleting and \\ sequences is one of the main things that drives me out of LyX into xemacs/TeX. It would be very nice to have the flexibility you get in a text editor in LyX. I think you both understand this, though :) So what scheme do you propose? Now you've put me on the spot. Fair enough. I want to be able to break cells (split this column into two, moving everything to the right of the cursor one cell to the right), break lines (thats enough for this row, everything currently in this row becomes part of a new row) and shift everything to the right. The first and third of these are the equivalent to typing the one character sequence '' in the TeX source, the middle is like typing '\\'. I also want to be able to join cells (equivalent to deleting ) and rows (more rarely). It's just a lot less convenient to have to use cut and paste for these (especially if I have to bring up a dialog box if I want to modify the number of columns there are). I honestly do this stuff quite a lot. Imagine an equation x = f(g(blah...)) + h(...foo) suppose it gets too long. Then I put my insertion point before the plus, and type \\ ret and get x = f(g(blah...)) \\ + h(...foo) (this is in an eqnarray, as an example). Jules
Re: Import ASCII as Verse
Jean-Marc Lasgouttes wrote: Garst == Garst R Reese [EMAIL PROTECTED] writes: Hmmm... This means import as lines should keep line break as line breaks and change double line breaks to paragraph break. This seems reasonable, in fact. Why don't we do that always? I'd like to know what people think about that... Garst Yes. It also would have been nice if when in paragraph=verse, Garst an [enter] would have been interpreted as a line break and Garst C-[enter] as a paragraph break, but changing the behaviour now Garst is probably a bad idea. Yes, it is probably a very very bad idea :) If we do that, next time tou will ask that in verses footnote are output as tabulars and tabulars as footnotes... JMarc :) But in poetry, linebreaks function as end of sentence or phrase and stanzas as paragraphs. Considering all of the wierd stuff you let mathematicians do, I don't think it out of line to cater to poets aussi. Garst (who does both)
Re: Natbib announcement
On Thursday 19 July 2001 12:21, Jürgen Spitzmüller wrote: On Wednesday, 18. July 2001 19:39, Angus Leeming wrote: Those willing to help save the CVS head repository from contamination with junk code should: cvs checkout -r BRANCH_NATBIB lyx-devel To get natbib support you'll need to set some parameters in the Document-Extra tab It should be obvious which ones! Hm, I really would like to test, but I can't get Natbib in. I did (without concept ;-) cvs checkout -r BRANCH_NATBIB lyx-devel make distclean ./autogen.sh ./configure ; make start lyx from the cvs directory. But there is no Natbib (still have the huge citation dialog and nothing in Document - Extra. I'm a CVS newbie, so any help is appreciated! Thanks, Jürgen. Well, now it's in head so just update and play. Angus
Re: mathed103.diff
(this is in an eqnarray, as an example). It looks as C-Tab, C-Return and Backspace at the beginning of an cell is what you are looking for. Andre' -- André Pönitz . [EMAIL PROTECTED]
Re: Natbib announcement (and 666 inset gripes)
On Thu, Jul 19, 2001 at 09:21:51AM +0200, Juergen Vigna wrote: On 18-Jul-2001 Mike Ressler wrote: This is not a stunning example of WYSIWYM. Please, please, (Lars?) change the appearance back to the old behavior!!! I don't think this will happen. What will happen is that we will change the InsetERT to be inlined. What will NOT happen is that a inlined ERT inset breaks row, so this is really thought only for short stuff! can't you un-inline the ert inset automagically when it extends beyond the right margin of the workarea ? john -- Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything. - Karl Lehenbauer
Re: Re-implementing open-stuff [questions about insets and signa
On Thu, Jul 19, 2001 at 03:26:42PM +0200, Jean-Marc Lasgouttes wrote: Making one is not a problem, but I'm looking for ideas on a convenient interface... why not a settings key/lyxfunc which will automagically do -edit() to bring up the right dialog in any circumstance ? It could even bring up the Paragraph dial in a para. Or am I missing the discussion ? it would quite nice if the inset button had an ? button next to it which brought up the dialog perhaps regards john -- Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything. - Karl Lehenbauer
Re: Natbib announcement (and 666 inset gripes)
On 19-Jul-2001 John Levon wrote: can't you un-inline the ert inset automagically when it extends beyond the right margin of the workarea ? Probably yes, but do I want to do this? Probably no, as then I would get complaints about this automatic behaviour someone surely doesn't like! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Life sucks, but death doesn't put out at all. -- Thomas J. Kopp
Re: Natbib announcement (and 666 inset gripes)
On Thu, Jul 19, 2001 at 05:08:12PM +0200, Juergen Vigna wrote: On 19-Jul-2001 John Levon wrote: can't you un-inline the ert inset automagically when it extends beyond the right margin of the workarea ? Probably yes, but do I want to do this? Probably no, as then I would get complaints about this automatic behaviour someone surely doesn't like! Think about the alternative - I add a lot of ert into the inset, so it is drawn off the side, and I can't even read it ! Surely we dont really have/want a choice in this circumstance. john -- Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything. - Karl Lehenbauer
Re: Natbib announcement (and 666 inset gripes)
On Thursday 19 July 2001 16:08, Juergen Vigna wrote: On 19-Jul-2001 John Levon wrote: can't you un-inline the ert inset automagically when it extends beyond the right margin of the workarea ? Probably yes, but do I want to do this? Probably no, as then I would get complaints about this automatic behaviour someone surely doesn't like! Well it seems like a good suggestion to me because it only affects the users ability to see what's on LyX's screen. Who's going to complain loudly about LyX won't let me write text off the end of the screen when I want to? Anyway, that's the joy of being an open source developer: you can tell the user to get used to this behaviour I've implemented or change it yourself if you decide they're being a PITA. As I probably am. Enough, Angus
Re: mathed103.diff
On Thu, Jul 19, 2001 at 04:13:41PM +0200, Andre Poenitz wrote: (this is in an eqnarray, as an example). It looks as C-Tab, C-Return and Backspace at the beginning of an cell is what you are looking for. That works, does it? (Don't have up to date version here). Well, kudos, and apologies for wasting your time ! :-) Jules
Re: Natbib announcement (and 666 inset gripes)
On 19-Jul-2001 Angus Leeming wrote: Probably yes, but do I want to do this? Probably no, as then I would get complaints about this automatic behaviour someone surely doesn't like! Well it seems like a good suggestion to me because it only affects the users The only change to the above I would admit is making it displayed as soon as it is Larger then the screen, all other cases have to have a user interaction. Anyway before we have to implement the inlined stuff then we can discuss about this :) Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Lots of folks are forced to skimp to support a government that won't.
Re: Re-implementing open-stuff [questions about insets and signa
John == John Levon [EMAIL PROTECTED] writes: John On Thu, Jul 19, 2001 at 03:26:42PM +0200, Jean-Marc Lasgouttes John wrote: Making one is not a problem, but I'm looking for ideas on a convenient interface... John why not a settings key/lyxfunc which will automagically do John -edit() to bring up the right dialog in any circumstance ? It John could even bring up the Paragraph dial in a para. John Or am I missing the discussion ? My problem is that there are two ways to 'open' a minipage: uncollapse it or open its dialog. We need two different ways of doing these two things. For other insets, clicking with left button (or using C-o) is supposed to open them, and until now this meant doing _one_ of these actions. John it would quite nice if the inset button had an ? button next John to it which brought up the dialog perhaps Yes, maybe something like that. JMarc
Re: Natbib announcement (and 666 inset gripes)
On Thursday 19 July 2001 16:14, Juergen Vigna wrote: On 19-Jul-2001 John Levon wrote: Think about the alternative - I add a lot of ert into the inset, so it is drawn off the side, and I can't even read it ! Surely we dont really have/want a choice in this circumstance. Well we have already the inset will scroll to the right if the cursor exits to the left ;) (try this in a tabular cell where the InsetText IS inlined). Oh you bugger! I've just done this and now I'm getting infinite redraws of the table and can do nothing useful at all. Phew! LyX has just crashed on me. Road test to infinite redraws: 1. Insert table, I row, 2 columns 2. Type in first (leftmost) column until the table gets bigger than the width Bingo! Actually, If you leave this on screen doing its stuff then you'll crash LyX in malloc. Presumably it just runs out of memory therefore. Angus
Re: Natbib announcement (and 666 inset gripes)
On 19-Jul-2001 Angus Leeming wrote: Road test to infinite redraws: 1. Insert table, I row, 2 columns 2. Type in first (leftmost) column until the table gets bigger than the width Well this is well known and as developer you should have looked at the buglist on SourceForge.net ;) Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Your aim is high and to the right.
Re: submenu entry for Lastfiles (patch provided) still autogen problems
R == R Lahaye [EMAIL PROTECTED] writes: R Hi, R The File-menu entry gets very long when the list of Lastfiles is R added at the end. I suggest to add a new entry Open previous R which contains the Lastfiles as a submenu: As Juergen explained, this change means that the enties are more difficult to get to. Since they are supposed to be a shortcut... R (This patch also makes R as the shortcut to Revert to saved and R removes a redudant newline somewhere in the file). I took this one. BTW, feel free to 'audit' the menus and propose changes. In particular, the Insert menu is getting very large IMO. JMarc
Re: Natbib announcement (and 666 inset gripes)
On Thu, Jul 19, 2001 at 05:50:43PM +0200, Juergen Vigna wrote: On 19-Jul-2001 Angus Leeming wrote: Road test to infinite redraws: 1. Insert table, I row, 2 columns 2. Type in first (leftmost) column until the table gets bigger than the width Well this is well known and as developer you should have looked at the buglist on SourceForge.net ;) actually it's changed behaviour recently - a 1x2 table didn't used to trigger it ... john -- Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything. - Karl Lehenbauer
Re: Natbib announcement (and 666 inset gripes)
On Thursday 19 July 2001 16:50, Juergen Vigna wrote: On 19-Jul-2001 Angus Leeming wrote: Road test to infinite redraws: 1. Insert table, I row, 2 columns 2. Type in first (leftmost) column until the table gets bigger than the width Well this is well known and as developer you should have looked at the buglist on SourceForge.net ;) I still think that this was a sly way to get help, but anyway I've played further. The infinite redraws are the result of a recursive cycling 18 updateLocal__C12InsetTabularXP10BufferView11UpdateCodesjb(0x28e, 0x0, 0x12034b334, 0x1401e4900, 0x1401814b0) [0x120348320] 19 resetPos__C12InsetTabularXP10BufferView(0x1401814b0, 0x1401e4938, 0x36, 0x1401e4968, 0x26a) [0x12034b330] 20 updateLocal__C12InsetTabularXP10BufferView11UpdateCodesjb(0x26a, 0x0, 0x12034b334, 0x1401e4900, 0x1401814b0) [0x120348320] 21 resetPos__C12InsetTabularXP10BufferView(0x1401814b0, 0x1401e4938, 0x1d, 0x1401e4968, 0x28e) [0x12034b330] 22 updateLocal__C12InsetTabularXP10BufferView11UpdateCodesjb(0x28e, 0x0, 0x12034b334, 0x1401e4900, 0x1401814b0) [0x120348320] Note that 18 and 22 are identical. As are 19 and 23 etc. So it's not just a simple oscillation between the two methods. Interestingly, if I create my table so that it reaches the width of the screen (just less) and then paste in some more text, then I CAN scroll. But doing so, I get a new problem. Effectively, I scroll off the end and into a segmentation fault. Backtrace below, but physically what happens is: Create a new document. Insert a table, 1row, 2cols Type e e e e e e in the first column until just before the table reaches screen width. Exit the table and on the line above type elephant elephant Cut this text, move the cursor around so only the line with the table on it exists. Paste the cut text into the leftmost column of the table so that the width is greater than the screen width. Scroll happily to the end of the first column (of two) with the right arrow key. Leave it and enter second column. Continue scrolling til we leave this column, continue scrolling (one more arrow press) to leave the table. The table is now redrawn with its left-most edge showing (fine), but the cursor is invisible. Pressing the arrow keys (some combination, any combo), to try and get the cursor visible again and eventually we get the segmentation fault and backtrace below. Angus signal Segmentation fault at *[GetCellNumber__C10LyXTabularXii, 0x1202aaa08] ldl r0, 0(r0) (dbx) where 0 GetCellNumber__C10LyXTabularXii(0x3ff801151ac, 0x, 0x12034ad68, 0x1401e2600, 0x397) [0x1202aaa08] 1 setPos__C12InsetTabularXP10BufferViewii(0x1401814b0, 0x397, 0xa, 0x0, 0x1400a80d8) [0x12034ad64] 2 edit__12InsetTabularXP10BufferViewiiUi(0x1201e83b8, 0x120348170, 0x1401e2600, 0x32, 0x1401814b0) [0x120348264] 3 Dispatch__Q110BufferView5PimplX9kb_actionRCQ13std60basic_string__TcQ13std15char_traits__TcQ13std13allocator__Tv(0x0, 0x0, 0x1201e56f0, 0x1400f6ed8, 0x1201dc100) [0x1201e83b4] 4 Dispatch__10BufferViewX9kb_actionRCQ13std60basic_string__TcQ13std15char_traits__TcQ13std13allocator__Tv(0x1201e56f0, 0x1400f6ed8, 0x1201dc100, 0x1400ac4c0, 0x120275bb0) [0x1201dc304] 5 dispatch__7LyXFuncXiRCQ13std60basic_string__TcQ13std15char_traits__TcQ13std13allocator__Tv(0x3ff801151ac, 0x1, 0x1ff51, 0x0, 0x1400f6e48) [0x120275bac] 6 processKeySym__7LyXFuncXUiUi(0x3ff801151ac, 0x1400a8000, 0x12042f700, 0x1400ac4c0, 0x120425108) [0x12027058c] 7 workAreaKeyPress__Q110BufferView5PimplXUiUi(0x12042f700, 0x1400ac4c0, 0x120425108, 0x140186658, 0x1201e02dc) [0x1201e288c] 8 (unknown)() [0x1201e02d8] 9 emit__Q14SigC38Signal2__Tv__TUiUiQ14SigC11Marshal__TvXRCUiRCUi(0x120219a30, 0x140186658, 0x61, 0x1400a5924, 0xcbff0c51) [0x120150a90] 10 work_area_handler__8WorkAreaXP7flobjs_Pv(0x540006f, 0xff51, 0xff51, 0xff51, 0x140186658) [0x120219a2c] 11 C_WorkArea_work_area_handler(0xff51, 0xff51, 0x140186658, 0x140178080, 0x3ffbff8c494) [0x120218370] 12 (unknown)() [0x3ffbff8c490] 13 fl_handle_object(0x140187600, 0x140187600, 0x3fc6300, 0xff51, 0x3ffbff51e90) [0x3ffbff8c584] 14 (unknown)() [0x3ffbff51e8c] 15 (unknown)() [0x3ffbff52504] 16 (unknown)() [0x3ffbff52970] 17 (unknown)() [0x3ffbff530fc] 18 fl_treat_interaction_events(0x13365100022641, 0x1336510001233d, 0x143954000d314c, 0x116320001233d, 0xa2c4500052a44) [0x3ffbff5386c] 19 fl_check_forms(0x143954000d314c, 0x116320001233d, 0xa2c4500052a44, 0x1233d00072739, 0x12037728c) [0x3ffbff538bc] 20 runTime__10GUIRunTimeXv(0x14019c260, 0x0, 0x14019c2c0, 0x3a017422, 0x140176690) [0x120377288] 21 runTime__6LyXGUIXv(0x14019c2c0, 0x3a017422, 0x140176690, 0x1400a8000, 0x120263e30) [0x12026047c] 22 __ct__3LyXXPiPPc(0x140065820, 0x3ffc00802a0, 0x12024cc6c, 0x140027148, 0x116c8) [0x120263e2c] 23 main(0x0, 0x80084600, 0x1400ecda0, 0x11748, 0x10001) [0x12028db2c]
latest cvs - ert
maybe that this is reported earlier.
- open new doc, click on tex, insert from tex newsgroup
\begin{gather}\text{x} = \aaa{x}\\ \text{X} = \aaa{X}\end{gather}
- insert three cr's:
\begin{gather}
\text{x} = \aaa{x}\\
\text{X} = \aaa{X}
\end{gather}
- run dvi, gives errors! export to latex gives
... preamble stuff ...
\begin{document}
\begin{gather} \begin{gather} \begin{gather} \begin{gather}
...
- curious ... ;-)
Herbert
--
http://www.educat.hu-berlin.de/~voss/lyx/
Re: Natbib announcement
On Thursday, 19. July 2001 16:17, Angus Leeming wrote: Well, now it's in head so just update and play. Angus Thanks, I got it now ;-) Looks great! A few comments, though: - Citation Dialog size is much better now, but now a little bit too wide (about 1cm) for 800x600. Well, not really tragic but a little bit annoying ;-) - Your WYSIWYG-Choice of the citestyle is not really WYSIWYG: The surnames are not cited, so don't parse Leeming, Angus (2001) but Leeming (2001) if possible - In layout - document you can choose the option Author-Year or Numerical. But what about the other Natbib Options apart from numbered (e.g. sortcompress)? I guess I have to insert them into Layout Document Document Options. Wouldn't a separate Options field be better? Today there was a discussion about a dialog for all supported packages (thread Natbib). I guess one pro for this dialog would be that you could have an options-field for each of these packages (or support some Options directly via menue). Inserting all Options from the global options field to each and any package is not the ideal solution IMHO. This could really lead to trouble if two packages use the same name for an option. As a hardcore natbib user I really like how you implemented this from what I've seen on a first view. Thank you very much! I will try to help you by testing this feature as good as I can, Greets, Jürgen
Re: Natbib
On Thu, Jul 19, 2001 at 02:15:53PM +0200, Juergen Vigna wrote: On 19-Jul-2001 Dekel Tsur wrote: On Thu, Jul 19, 2001 at 12:56:46PM +0200, Juergen Vigna wrote: What if you don't have all extra super truper latest packages installed on your actual machine but would like to be able to preview at least normal text? Just check of that feature in the dialog, the resulting LaTeX will not use that feature, and your able to preview the document (obviously not with that feature). Why do you need a dialog ? LyX should read the packages.lst file. Yes and that tells me that the package is not available and I'm not able to produce LaTeX code which includes that package, isn't it? Or do you propse to edit the packages.lst file by hand then? What I don't understand is why you don't want to use longtable (or other packages) if it is available ?
Breaking ligatrues
Breaking ligatures should be done with {}, \hbox{} or soemthing like that.
Using an italic correction, \/, will do the *wrong thing* on slanted or italic
words that are not split where you hide the ligature. In upright fonts allmost
all the italic corrections are zero so you will not notice the potential brain
damage most of the time.
An empty group or box is a method of hiding ligatures sanvctioned by the
TeXbook and gauranteed to be invisble. Itaiic corrections might not be
invisble and are thus the *wrong thing*. I sippose that \/\unskip might be OK
but an empty group or box seems to make more sense. Before you ask \unskip is
a plain TeX operation that removes a preceding skip.
--
Duncan (-:
software industry, the: unique industry where selling substandard goods is
legal and you can charge extra for fixing the problems.
Re: core dump
John Levon wrote: clicking on e.g. greek in math panel core dumps lyx for me. anyone else ? 0.88, rh7 thanks john The problem persists. Any box from greek to Misc. If I go into math mode first I get an emergency save, otherwise not. Maybe this bug will disappear with the math panel. Can't seem to get to lyxbugs ATM. Garst
crash importing latex
I still haven't manually made changes in my make file, so my lys is a
few weeks old. I've tried importing a tex file of an errata, as the
latex itself prints in mostly bold. Lyx crashes, and the backtrace is
(gdb) run
Starting program: /usr/local/bin/lyx
Program received signal SIGSEGV, Segmentation fault.
{anonymous}::yylex () at math_parser.C:238
warning: Source file is more recent than executable.
238 if (!init_done) {
(gdb) bt
#0 {anonymous}::yylex () at math_parser.C:238
#1 0x814ea41 in mathed_parse (array=@0xbfbfe8d8, par=@0x836c21c, flags=0)
at math_parser.C:981
#2 0x8139bde in InsetFormula::Read (this=0x836c200, buffer=0x8350400,
lex=@0xbfbfedc0) at formula.C:319
#3 0x8090477 in Buffer::readInset (this=0x8350400, lex=@0xbfbfedc0,
par=@0xbfbfec48, pos=@0xbfbfebfc, font=@0xbfbfec0c) at buffer.C:1277
#4 0x808dbe1 in Buffer::parseSingleLyXformat2Token (this=0x8350400,
lex=@0xbfbfedc0, par=@0xbfbfec48, return_par=@0xbfbfebf8,
token=@0xbfbfec08, pos=@0xbfbfebfc, depth=@0xbfbfec03, font=@0xbfbfec0c)
at buffer.C:944
#5 0x8088a62 in Buffer::readLyXformat2 (this=0x8350400, lex=@0xbfbfedc0,
par=0x8362800) at buffer.C:334
#6 0x8090a37 in Buffer::readFile (this=0x8350400, lex=@0xbfbfedc0, par=0x0)
at buffer.C:1319
#7 0x80a0960 in BufferList::readFile (this=0x82bc150, s=@0xbfbfeea4,
ronly=false) at bufferlist.C:406
#8 0x80a16bb in BufferList::loadLyXFile (this=0x82bc150,
filename=@0xbfbff070, tolastfiles=true) at bufferlist.C:509
#9 0x80e3bc6 in LyXFunc::Open (this=0x8338480, fname=@0xbfbff224)
at lyxfunc.C:1684
#10 0x80dd314 in LyXFunc::Dispatch (this=0x8338480, ac=157,
do_not_use_this_arg=@0xbfbff264) at lyxfunc.C:1127
---Type return to continue, or q return to quit---
#11 0x80d882f in LyXFunc::processKeySym (this=0x8338480, keysym=111, state=4)
at lyxfunc.C:351
#12 0x805563a in BufferView::Pimpl::workAreaKeyPress (this=0x8328300,
keysym=111, state=4) at BufferView_pimpl.C:507
#13 0x8226e3f in SigC::ObjectSlot2_void, unsigned long, unsigned int,
BufferView::Pimpl::callback (d=0x8338134, p1=111, p2=4) at ../sigc++/object_slot.h:250
#14 0x82343ff in SigC::Signal2void, unsigned long, unsigned int, SigC::Marshalvoid
::emit (this=0x8328334, p1=@0xbfbff348, p2=@0xbfbff344)
at ../sigc++/slot.h:456
#15 0x80868e3 in WorkArea::work_area_handler (ob=0x8328a00, event=9, key=15,
xev=0x2834737c) at WorkArea.C:432
#16 0x80859de in C_WorkArea_work_area_handler (ob=0x8328a00, event=9, key=15,
xev=0x2834737c) at WorkArea.C:58
#17 0x2830c4ff in fl_handle_it () from /usr/X11R6/lib/libforms.so.0.88
#18 0x2830c5a5 in fl_handle_object () from /usr/X11R6/lib/libforms.so.0.88
#19 0x282fefba in fl_keyboard () from /usr/X11R6/lib/libforms.so.0.88
#20 0x282ff382 in fl_handle_form () from /usr/X11R6/lib/libforms.so.0.88
#21 0x282ff64d in do_keyboard () from /usr/X11R6/lib/libforms.so.0.88
#22 0x282ffc29 in do_interaction_step () from /usr/X11R6/lib/libforms.so.0.88
#23 0x2830024a in fl_treat_interaction_events ()
from /usr/X11R6/lib/libforms.so.0.88
#24 0x28300284 in fl_check_forms () from /usr/X11R6/lib/libforms.so.0.88
#25 0x81a2324 in GUIRunTime::runTime () at GUIRunTime.C:85
--
Prof. Richard E. Hawkins, Esq. /\ 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. / \
--
Prof. Richard E. Hawkins, Esq. /\ 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. / \
--
Prof. Richard E. Hawkins, Esq. /\ 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: Breaking ligatrues
Duncan == Duncan Simpson [EMAIL PROTECTED] writes:
Duncan Breaking ligatures should be done with {}, \hbox{} or
Duncan soemthing like that. Using an italic correction, \/, will do
Duncan the *wrong thing* on slanted or italic words that are not
Duncan split where you hide the ligature. In upright fonts allmost
Duncan all the italic corrections are zero so you will not notice the
Duncan potential brain damage most of the time.
Except that {} can just disappear in some situations :(
I have implemented the feature using \textcompwordmark, which does
whatever is needed in this case. I'll commit tomorrow.
JMarc
Re: core dump
On Thu, Jul 19, 2001 at 05:30:22PM -0300, Garst R. Reese wrote: John Levon wrote: clicking on e.g. greek in math panel core dumps lyx for me. anyone else ? 0.88, rh7 thanks john The problem persists. Any box from greek to Misc. If I go into math mode first I get an emergency save, otherwise not. what compiler ? I get this with gcc 3.0 Maybe this bug will disappear with the math panel. what do you mean ? Can't seem to get to lyxbugs ATM. grr, damned sf ... john -- Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything. - Karl Lehenbauer
Re: core dump
John Levon wrote: what do you mean ? There have been rumblings for some time about the math panel and replacing it with some sort of tool bar, so I figured breaking it might be on the path. It's friday somewhere eh? Garst
Re: core dump
On Thu, Jul 19, 2001 at 09:34:25PM -0300, Garst R. Reese wrote: John Levon wrote: what do you mean ? There have been rumblings for some time about the math panel and replacing it with some sort of tool bar, so I figured breaking it might be on the path. I see. The weird thing is there's been no real change to that code recently as far as I can see, since it was moved into frontends/xforms directory, so I don't know why it's stopped working. I compile w/o optimisation so I think it's less likely to be a compiler bug, I don't know ... john -- Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything. - Karl Lehenbauer
View-TOC buglet
The Close button in the TOC panel changes to Cancel after you use the window to jump around. Why? Shouldn't it just stay Close. This is with the lyx-1.1.6fix3 CVS branch. Haven't tried 1.2.0 CVS ... Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Traditional look website
On Mon, 9 Jul 2001, John Levon wrote: On Thu, Jul 05, 2001 at 09:58:55PM +1000, Allan Rae wrote: Since the default should be the new look (?name=0) so people can read the pages and because I'm doing the work I guess I can choose from: slow, bgimage, old, ugly, unreadable, green, traditional, higraphics, bwhog, why, enriched, rich, prehistoric, 1994, classic, retro :rotfl looks like Allan has won the LDN post prize to me ! If you want to see something with too much graphics take a peek at: http://www.elec.uq.edu.au/~rae/test.html I managed to get the body and the main text to have different images behind them. I'm also thinking it might be fun to add different images for the menubar if people wanted to be really extreme. Anyway, the menus don't work on the page so don't complain about that. The images are just for testing so don't complain about them either. The menubar scrolls with the text because Galeon/Mozilla don't render it properly otherwise. The menu is rendered with a black background in Netscape -- the simple fixes for this we've used in the past don't seem to be working now. Too many images now perhaps? This was just an experiment to see what could be done. It isn't necessarily a suggested scheme for use on www.lyx.org. Allan. (ARRae)
Re: Patch: version build info added.
Jean-Marc Lasgouttes wrote:
"R" == R Lahaye [EMAIL PROTECTED] writes:
R Hi,
R I thought it'll be useful to have an option
Rlyx -version (or: lyx --version )
R that will tell appropriate information on the
R system/build/compilation. This is very useful when reporting bug
R reports; once as executable, it is not so easy to find out how it
R was generated.
Looks like an excellent idea. A simpler solution would probably be to
generate this data in a file that would be installed along with LyX.
This way the information would be available even when LyX cannot be
launched.
I then would opt for both: allow a version flag to the lyx executable
and generate a file or script ("lyx-config") with the version info.
Many software handles a "-version" (and/or "--version") flag, so I
thought it'll be useful to add this to LyX as well. For software under
development this flag should output all necessary info for the developers.
This output added to a bug report, could be most helpful.
Rob.
RE: Feedback from www.lyx.org
On 19-Jul-2001 [EMAIL PROTECTED] wrote: Gunnar ([EMAIL PROTECTED]) entered the following feedback message on the LyX home page: Hello. I've always liked lyx, but now I must say that I do not like how the tables works in 1.1.6-fix2. To move the cursor between two adjecent boxes I have to press the arrowkey twice. WHY?? It was so much better in earlier versions. I guess this is fixed in the cvs version and upcoming 1.2.0 (with a lot of other stuff and enhancements to the whole tabular stuff) BTW.: Could you write paragraps in the old tabular stuff? Could you change the layouts of this tabulars? Could you automatically define a with on a column and the text was automatically wraped around? Could you scroll the tabular to one side if it was to large to fit on the screen? (I could go on asking for more ;) IMO we have to live with small changes to the user-interface if this permits us to do a lot more stuff for advanced use of tabulars! I however admit that tabular stuff in 1.1.6 was not really finished, but it helped me A LOT to enhance and fix a lot of stuff from User Feedback, which I could not have done with the little feedback you get from Users and/or developers using the CVS (development version)! Greets, Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ There's a way out of any cage. -- Captain Christopher Pike, The Menagerie (The Cage), stardate unknown.
Updated (Lyx/Latex) - (ps/pdf/html) script
Hi All, I have updated/documented quite a bit my Perl script to automate producing PostScript, PDF and HTML from a Latex or Lyx source file. I've tested it a fair bit and it seems to be working well (famous last words), to the point where I've replaced the normal calls to pdflatex and latex2html with it in my Converters dialog. Its whole purpose is to work around the quirks of pdflatex and latex2html to be a bit more robust and convenient. There is now full documentation and an installation makefile, so it should be usable by non-coders. I know it still chokes on very complex files (Thomas...) but some of those problems seem to be things that kill latex2html or pdflatex themselves. I've put up a bare bones web page for it at http://www-hep.colorado.edu/~fperez/lyxport I post this to both lists b/c I think it may be useful to others, and it can certainly use more testing and bugfixing by more brains than mine. All comments and suggestions are welcome, as well as code with improvements. Jean-Marc, you are welcome to include the latest version from the web page in lyx/contrib if you find it good enough for general use. The code is GPL. Cheers, Fernando PS: Please cc your replies to me or to lyx-users, as I'm not subscribed to lyx-devel (though I read the archives).
Re: misc guii
On Wed, 18 Jul 2001, Angus Leeming wrote: > > Allan. (ARRae) Who feels retirement or at least a sabatical coming on. > > What's this? Are you feeling burnt out from writing a thesis or bored of LyX. Not enough thesis and too many LyX emails to read each day. Maybe I should do like Amir did and unsubscribe from lyx-devel and subscribe to the digest instead... hmmm... maybe procmail would be a better idea and filter out anything that doesn't mention me... > What about that shoulder to lean on I've been relying on all this time. I'm > not sure I can stand on my own two feet after all this time!!! I have a hundred and one different things I'd love to fix or break or whatever in LyX but my thesis really should get to be my first priority at some stage during my candidature. Doesn't mean I don't want to continue supporting the effort but I am wondering what is the best move at this point (five years into my PhD). Stuff like: finish my thesis versus fix up the guii class hierarchy? I finished my employment with the Uni two weeks ago (although I have another week or two of consulting that they want me for) and have only done LyX website and some hiking in that time. No thesis. No LDN. No code. I can pay rent and buy food until perhaps Christmas with my savings. But, then I need to work again and I know for a fact that in the two years of part/full time work I did until now I never got any useful work done on my thesis. So perhaps that should be a warning to other postgrads. Make the most of your scholarship while it lasts. I'll finish breaking www.devel.lyx.org before I bugger off (if I do) but if anyone out there wants to read LDN in future they might have to consider writing it themselves. I'll try once again to get an LDN written for next week but at present my back is not happy with me after I hurt it weight lifting. That was supposed to be helping strengthen my back so it was less likely to get hurt... ironic isn't it? Allan. (ARRae)
Re: Preference's Save/Apply button anomalities
On Thu, 19 Jul 2001, R. Lahaye wrote: > Allan Rae wrote: > > > > On Wed, 18 Jul 2001, R. Lahaye wrote: > > > > > I believe that the Save & Apply button of the Preferences > > > lights up or doesn't, when it should or shouldn't: > > > > > > 1) It doesn't when I type a new Backup path or LyXServer pipe > > >in Inputs->Paths, but it should! > > > > If the path doesn't include existing directories this will fail. > > That is, if you enter /home/me/temp/lyx/ and /home/me/temp doesn't exist > > then the validity test will fail. What are the entries you are trying to > > use? And how much of those paths actually exists? > > Earlier I had set LyXServer-pipe to "/home/lahaye/.lyx/pipe". When I then open > the preferences dialog and manually change that into "/home/lahaye/.lyx/mypipe" > (simply typing "my" infront of "pipe"), I cannot [Save] or [Apply] that change > because both buttons are still disabled. This is not the correct behaviour to > my opinion, since I have changed the pipe in a legitimate way. > Or what do you think? > In this example, I have to change (and change back) something else in order > to enable the [Save/Apply] buttons to save my new LyXServer-pipe. Strange. > > > 2) It does, when I select a line in the list of the LyX objects > > >in Look & Feel -> Colors, although it shouldn't because I do not > > >make any changes. > > > > This is a problem of the "what is an input and what isn't" variety we have > > had elsewhere. > > Problem of input? I don't understand. Talking about coding rather than user input. IMO, these fields of the dialog shouldn't be going anywhere near the input() function. > Simply looking at the default top Object "GUI background" doesn't affect the > [Save/Apply] buttons. > So why then enable [Restore/Save/Apply] buttons when I LOOK AT the colour settings > of (for example) "latex text". That implies no changes at all (just looking!), so > it should not enable the [Restore/Save/Apply] buttons. > Only when I change one of the colour settings, I should be able to Save/Apply this > change. Sure. If you haven't pressed Modify in the colour tab then you can't have changed anything. So Modify is argueably the only button there that should be calling the input() callback. Allan. (ARRae)
Re: Natbib announcement (and 666 inset gripes)
On 18-Jul-2001 Mike Ressler wrote: > This is not a stunning example of WYSIWYM. Please, please, (Lars?) change > the appearance back to the old behavior!!! I don't think this will happen. What will happen is that we will change the InsetERT to be inlined. What will NOT happen is that a inlined ERT inset breaks row, so this is really thought only for short stuff! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Might as well be frank, monsieur. It would take a miracle to get you out of Casablanca and the Germans have outlawed miracles. -- Casablanca
[gunix@telia.com] Feedback from www.lyx.org
Hello, I forwarded your message to the developpers list. JMarc Gunnar ([EMAIL PROTECTED]) entered the following feedback message on the LyX home page: Hello. I've always liked lyx, but now I must say that I do not like how the tables works in 1.1.6-fix2. To move the cursor between two adjecent "boxes" I have to press the arrowkey twice. WHY?? It was so much better in earlier versions.
Re: Natbib announcement (and 666 inset gripes)
On Thu, 19 Jul 2001, Juergen Vigna wrote: > On 18-Jul-2001 Mike Ressler wrote: > > This is not a stunning example of WYSIWYM. Please, please, (Lars?) change > > the appearance back to the old behavior!!! > > I don't think this will happen. What will happen is that we will change > the InsetERT to be inlined. What will NOT happen is that a inlined ERT > inset breaks row, so this is really thought only for short stuff! I don't care what the underlying mechanism is (insets, fonts, etc.). I would like the _appearance_ to resemble the old style. Having it appear like a math inset would be fine. Maybe that is the model: an inlined ERT box and a "display" ERT box, for longer chunks of LaTeX code. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: misc guii
Priorities, priorities. I'd suggest that LyX is fun but that if you stop work on it, it'll magically continue on it's own happy course. Is the same true of a thesis? Unfortumately not. You've invested five years into this labour of love, but you'll get nothing tangible in return unless you finish it. So do as Amir did and finish it. Angus On Thursday 19 July 2001 07:55, Allan Rae wrote: > On Wed, 18 Jul 2001, Angus Leeming wrote: > > > > Allan. (ARRae) Who feels retirement or at least a sabatical coming on. > > > > What's this? Are you feeling burnt out from writing a thesis or bored of LyX. > > Not enough thesis and too many LyX emails to read each day. > > Maybe I should do like Amir did and unsubscribe from lyx-devel and > subscribe to the digest instead... hmmm... maybe procmail would be a > better idea and filter out anything that doesn't mention me... > > > What about that shoulder to lean on I've been relying on all this time. I'm > > not sure I can stand on my own two feet after all this time!!! > > I have a hundred and one different things I'd love to fix or break or > whatever in LyX but my thesis really should get to be my first priority at > some stage during my candidature. Doesn't mean I don't want to continue > supporting the effort but I am wondering what is the best move at this > point (five years into my PhD). Stuff like: finish my thesis versus fix > up the guii class hierarchy? > > I finished my employment with the Uni two weeks ago (although I have > another week or two of consulting that they want me for) and have only > done LyX website and some hiking in that time. No thesis. No LDN. No > code. > > I can pay rent and buy food until perhaps Christmas with my savings. But, > then I need to work again and I know for a fact that in the two years of > part/full time work I did until now I never got any useful work done on my > thesis. So perhaps that should be a warning to other postgrads. Make the > most of your scholarship while it lasts. > > I'll finish breaking www.devel.lyx.org before I bugger off (if I do) but > if anyone out there wants to read LDN in future they might have to > consider writing it themselves. I'll try once again to get an LDN written > for next week but at present my back is not happy with me after I hurt it > weight lifting. That was supposed to be helping strengthen my back so it > was less likely to get hurt... ironic isn't it? > > Allan. (ARRae) > > -- Dr Angus Leeming Dept. of Bioengineering Imperial College London SW7 2BX Tel +44 (0) 20 7594 5186 Fax +44 (0) 20 7584 6897
Re: Re-implementing open-stuff [questions about insets and signals]
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: >> I will also need a way of toggling or, alternatively, to know >> whether an inset is open or closed. Is that possible? >> >> JMarc Angus> Does this cover it? Angus Angus, I tried yesterday to implement this stuff, and miserably failed :( It would help me a lot if you could do a sample implementation of this idea for one inset (pick the one you prefer :). Currently, I have implemented inset toggling for collapsable insets only. What remains to be done is 1/ implement it for insets which have a dialog 2/ see what to do with others, like math inset. What would be a reasonable open/close action? Toggle the math panel? JMarc
About allowed/forbidden insets
Hello, I have expanded the logic to handle disabling of inset insertion depending on context. Now the relevant menu entries are disabled when they should. Please check that this disabling occurs when it should. Something that seems suspicious to me is that floats are allowed in footnotes. Note that it is still possible to have a footnote in a float, which does not make sense for LaTeX. For that, one just has to copy/paste this footnote in the float. Insetead of trying to catch all the instances where this can happen, I propose to do the following: 1/ do not export these insets in LaTeX code (maybe replace by some text, like '[inset suppressed]' or whatever 2/ show on screen that the inset is disabled, probably by drawing a big red cross all over it. I'll try to experiment with that, and see if I can come up with something zhich is both easy and resistant to redraw problems. JMarc
Re: Natbib announcement (and 666 inset gripes)
On Thu, 19 Jul 2001, Juergen Vigna wrote: > On 19-Jul-2001 Mike Ressler wrote: > > > like a math inset would be fine. Maybe that is the model: an inlined ERT > > box and a "display" ERT box, for longer chunks of LaTeX code. > > That's exactly what we plan to do :) Excellent! Why didn't you just say so :-) Sorry if I sounded overly loud - I was just shocked by the appearance of those 666 boxes, and hadn't really followed the previous discussion closely enough to realize what was going on. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Re-implementing open-stuff [questions about insets and signals]
On Thursday 19 July 2001 09:56, Jean-Marc Lasgouttes wrote:
> > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> >> I will also need a way of toggling or, alternatively, to know
> >> whether an inset is open or closed. Is that possible?
> >>
> >> JMarc
>
> Angus> Does this cover it? Angus
>
> Angus, I tried yesterday to implement this stuff, and miserably failed
> :( It would help me a lot if you could do a sample implementation of
> this idea for one inset (pick the one you prefer :).
>
> Currently, I have implemented inset toggling for collapsable insets
> only. What remains to be done is
>
> 1/ implement it for insets which have a dialog
>
> 2/ see what to do with others, like math inset. What would be a
> reasonable open/close action? Toggle the math panel?
Aren't things as simple as this:
We want a member variable in the inset:
enum DialogStatus {
DIALOG_OPEN,
DIALOG_CLOSED
};
DialogStatus status;
I think that things will be cleanest if this variable is set by the dialog:
template
void ControlInset::hide()
{
if (params_) {
delete params_;
params_ = 0;
}
clearDaughterParams();
if (inset_) {
inset_.status = DIALOG_CLOSED;
inset_ = 0;
}
ih_.disconnect();
disconnect();
view().hide();
}
template
void ControlInset::connectInset(Inset * inset)
{
// If connected to another inset, disconnect from it.
if (inset_) {
ih_.disconnect();
inset_ = 0;
}
if (inset) {
inset_ = inset;
inset_.status = DIALOG_OPEN;
ih_ = inset->hideDialog.connect(
SigC::slot(this, ::hide));
}
connect();
}
Finally, we need a method Inset::toggle():
void Inset::toggle()
{
if (status == DIALOG_OPEN)
hideDialog();
else
emit();
}
Angus
Re: Nasty core dump with Lyx 1.1.6fix1
On Wed, Jul 18, 2001 at 06:42:18PM -0600, Fernando Pérez wrote: > I found an ugly coredump with 1.1.6f1: if I have a simple lyx file with an > included eps figure (in a float, it so happens), and try to export to latex > with > lyx --export latex file.lyx > > all goes well. However, if I use > > lyx -dbg --export latex file.lyx > > I get a nice coredump. I tried -dbg any to see how far it got, and this is Fixed.
Re: Natbib
On Thu, Jul 19, 2001 at 12:11:59AM +0200, Jean-Marc Lasgouttes wrote: > >> And the good design is to have ALL packages in a dialog and be able > >> what LaTeX code I want produce! AND this then should be honored by > >> the LaTeX methods! In this dialog we would have a button to receck > >> the LaTeX packages installed and also to save our actual will or to > >> apply it only to the current session! > > Dekel> I don't understand why you want this. Can you give an example ? > > The idea is that I should be able not to use natbib/amsfoo although > they are present. I should also be able to do as if they were present > even if they are not. So LyX discovers the available features, shows > them to me, and I decide whether to keep these defaults. I still don't understand this. For example, what does lyx is supposed to do when you "diable longtable" ? Should it forbid you from inserting longtables ? What about longtables which were already present in the document ? If you don't want to use the longtable package then just don't use longtables in the document.
Patch: version build info added.
Hi, I thought it'll be useful to have an option lyx -version (or: lyx --version ) that will tell appropriate information on the system/build/compilation. This is very useful when reporting bug reports; once as executable, it is not so easy to find out how it was generated. Currently I have added this version and build info to my CVS-version, which outputs on my PC: -- $ lyx -version LyX 1.2.0cvs of Thu, Jan 11, 2001 FreeBSD 4.3-RELEASE i386 Compilers: | C CFlags: gcc (2.95.3) -g -O2 | C++ Flags: g++ (2.95.3) -g -O -fno-exceptions -W -Wall | Special flags: frontend-xforms warnings included-libsigc assertions | LD Flags: | Build time: Jul 19 2001 18:49:41 FrontEnd: | GUI lib : xforms/libxforms.la | LD flags: | Includes: | Libs: $ - I realize that this is not yet the most useful output, but it might be a setup to what it should become after the necessary improvements to lyx-devel/configure.in (currently around line 300). If this is considered to be a useful addition, please apply the attached patch. The following files are patched therein: lyx-devel/acconfig.h : "#undef BUILD_INFO" added lyx-devel/configure.in : build/version output added lyx-devel/lyx.man : "-version" described lyx-devel/src/lyx_main.C : "-version flag" described and added The main output part is in configure.in, and that needs some more tweeking to improve the quality of the output (some of which I don't know how to produce, e.g. FrontEnd version/XForms version). Regards, Rob. versionAddPatch.gz
Re: Silly Email address fix
> "Kayvan" == Kayvan Sylvan <[EMAIL PROTECTED]> writes: Kayvan> My bad. An internal Email address shows up in the ChangeLogs. Applied. JMarc
Re: Latex on Lyx
> "Sung-Kwan" == Sung-Kwan Kim <[EMAIL PROTECTED]> writes: Sung-Kwan> Hi Previously, I tried to use Scientific Workplace to write Sung-Kwan> my paper. But I found an inconvenience that I had to keep Sung-Kwan> using either mouse or short key to type mathematical Sung-Kwan> expressions. Then I switched to Latex with an editor. It Sung-Kwan> has passed three months since I tried to learn Latex. My Sung-Kwan> question regarding Lyx is that is it possible to work with Sung-Kwan> Latex commands directly on Lyx when I compose my paper ? In math editor mode, you can mostly use the latex macros directly (type \frac to get a fraction). However, you will have a adapt a bit your sequence of keys to get what you want inside LyX. JMarc
Re: Import ASCII as Verse
> "Garst" == Garst R Reese <[EMAIL PROTECTED]> writes: Garst> Jean-Marc Lasgouttes wrote: >> > "Garst" == Garst R Reese <[EMAIL PROTECTED]> writes: >> Garst> Yet another feature request. Verse gets e-mailed me as groups Garst> of lines (stanzas) >> Garst> Separated by a blank line. With the next stanza continuing. >> And how should this be changed? linebreaks between lines and >> paragraph breaks between stanzas? Hmmm... This means import as lines should keep line break as line breaks and change double line breaks to paragraph break. This seems reasonable, in fact. Why don't we do that always? I'd like to know what people think about that... Garst> Yes. It also would have been nice if when in paragraph=verse, Garst> an [enter] would have been interpreted as a line break and Garst> C-[enter] as a paragraph break, but changing the behaviour now Garst> is probably a bad idea. Yes, it is probably a very very bad idea :) If we do that, next time tou will ask that in verses footnote are output as tabulars and tabulars as footnotes... JMarc
Re: Re-implementing open-stuff [questions about insets and signals]
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Aren't things as simple as this:
Angus> We want a member variable in the inset:
Angus> enum DialogStatus { DIALOG_OPEN, DIALOG_CLOSED }; DialogStatus
Angus> status;
If you want. A bool would probably be fine too.
Angus> I think that things will be cleanest if this variable is set by
Angus> the dialog:
Angus> template void ControlInset Params>::hide() { if (params_) { delete params_; params_ = 0; }
Angus> clearDaughterParams();
Angus> if (inset_) { inset_.status = DIALOG_CLOSED; inset_ = 0; }
Angus> ih_.disconnect(); disconnect(); view().hide(); }
If you say so... :)
Angus> Finally, we need a method Inset::toggle(): void Inset::toggle()
Angus> { if (status == DIALOG_OPEN) hideDialog(); else emit(); }
We already have the methods
void Inset::open(BufferView*, bool)
bool Inset::isOpen()
which should be enough. Currently they do something only for
collapsable inset, but I'd want to implement them for inset who have a
popup too. If you could show me some working code, I'd finish the
adaptation.
JMarc
Re: Natbib
On 19-Jul-2001 Dekel Tsur wrote: > I still don't understand this. > For example, what does lyx is supposed to do when you "diable longtable" ? > Should it forbid you from inserting longtables ? What about longtables which > were already present in the document ? > > If you don't want to use the longtable package then just don't use longtables > in the document. What if you don't have all extra super truper latest packages installed on your actual machine but would like to be able to preview at least normal text? Just check of that feature in the dialog, the resulting LaTeX will not use that feature, and your able to preview the document (obviously not with that feature). So in your case all tables would be normal tabels and go over the height of one page, but I just don't care at the moment for this as I would like to have a printout of the document without this longtables and without the need of special features to say "grammer-check" on a printout. Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ I smell a wumpus.
Re: Re-implementing open-stuff [questions about insets and signa
On 19-Jul-2001 Jean-Marc Lasgouttes wrote: > We already have the methods > void Inset::open(BufferView*, bool) > bool Inset::isOpen() > which should be enough. Currently they do something only for > collapsable inset, but I'd want to implement them for inset who have a > popup too. If you could show me some working code, I'd finish the > adaptation. What does this do if a collapsable inset has a dialog (InsetMinipage f.ex)? Then we say we're open and our dialog is open too? I would say we should split this! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Never eat more than you can lift. -- Miss Piggy
Re: Natbib announcement
On Wednesday, 18. July 2001 19:39, Angus Leeming wrote: > Those willing to help save the CVS head repository from contamination > with junk code should: > > cvs checkout -r BRANCH_NATBIB lyx-devel > > To get natbib support you'll need to set some parameters in the > Document->Extra tab > It should be obvious which ones! Hm, I really would like to test, but I can't get Natbib in. I did (without concept ;-) cvs checkout -r BRANCH_NATBIB lyx-devel make distclean ./autogen.sh ./configure ; make start lyx from the cvs directory. But there is no Natbib (still have the huge citation dialog and nothing in Document -> Extra. I'm a CVS newbie, so any help is appreciated! Thanks, Jürgen.
Re: Natbib
On Thu, Jul 19, 2001 at 12:56:46PM +0200, Juergen Vigna wrote: > What if you don't have all extra super truper latest packages installed on > your actual machine but would like to be able to preview at least normal text? > > Just check of that feature in the dialog, the resulting LaTeX will not use > that feature, and your able to preview the document (obviously not with > that feature). Why do you need a dialog ? LyX should read the packages.lst file.
Re: Re-implementing open-stuff [questions about insets and signa
> "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes: Juergen> On 19-Jul-2001 Jean-Marc Lasgouttes wrote: >> We already have the methods void Inset::open(BufferView*, bool) >> bool Inset::isOpen() which should be enough. Currently they do >> something only for collapsable inset, but I'd want to implement >> them for inset who have a popup too. If you could show me some >> working code, I'd finish the adaptation. Juergen> What does this do if a collapsable inset has a dialog Juergen> (InsetMinipage f.ex)? Then we say we're open and our dialog Juergen> is open too? I would say we should split this! Good point. What I was trying to reproduce is the behaviour of 1.1.6, which nobody complained about :) The idea is that inset-toggle should be the keyboard equivalent of clicking on an inset. The example that you propose shows that our UI is bad: left-clicking on an inset brings up the popup if there is one, *except* if it is a collapsable inset. In this case, it expands the inset (which arguably is a way to edit it). Then the right-click to edit minipage properties is just weird. BTW, what is the keyboard shortcut which provides this feature? I surely hope we have one... JMArc
Re: Natbib
On 19-Jul-2001 Dekel Tsur wrote: > On Thu, Jul 19, 2001 at 12:56:46PM +0200, Juergen Vigna wrote: >> What if you don't have all extra super truper latest packages installed on >> your actual machine but would like to be able to preview at least normal text? >> >> Just check of that feature in the dialog, the resulting LaTeX will not use >> that feature, and your able to preview the document (obviously not with >> that feature). > > Why do you need a dialog ? > LyX should read the packages.lst file. Yes and that tells me that the package is not available and I'm not able to produce LaTeX code which includes that package, isn't it? Or do you propse to edit the packages.lst file by hand then? Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Term, holidays, term, holidays, till we leave school, and then work, work, work till we die. -- C.S. Lewis
Re: Re-implementing open-stuff [questions about insets and signa
On 19-Jul-2001 Jean-Marc Lasgouttes wrote: > The example that you propose shows that our UI is bad: left-clicking > on an inset brings up the popup if there is one, *except* if it is a > collapsable inset. In this case, it expands the inset (which arguably Well make it better ;) > is a way to edit it). Then the right-click to edit minipage properties > is just weird. BTW, what is the keyboard shortcut which provides this > feature? I surely hope we have one... Sure we have one, don't we?! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ If you would keep a secret from an enemy, tell it not to a friend.
Re: Re-implementing open-stuff [questions about insets and signa
> "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes: Juergen> On 19-Jul-2001 Jean-Marc Lasgouttes wrote: >> The example that you propose shows that our UI is bad: >> left-clicking on an inset brings up the popup if there is one, >> *except* if it is a collapsable inset. In this case, it expands the >> inset (which arguably Juergen> Well make it better ;) Well, I am looking for ideas about agood interface, right now... >> is a way to edit it). Then the right-click to edit minipage >> properties is just weird. BTW, what is the keyboard shortcut which >> provides this feature? I surely hope we have one... Juergen> Sure we have one, don't we?! It seems that we don't. Tabulars have layout-tabular, but there does not seem to be anything for minipages. JMarc
buglet with insettext (collapsable insets?)
I know nobody cares about this kind of bug, but it be asign of something worse 1/ create a document with an empty open footnote. 2/ save it 3/ when going through the (empty) footnote, the document gets the (changed) status; this does not happen if there is text in the footnote. JMarc
Re: Re-implementing open-stuff [questions about insets and signa
On 19-Jul-2001 Jean-Marc Lasgouttes wrote: > Juergen> Sure we have one, don't we?! > > It seems that we don't. Tabulars have layout-tabular, but there does > not seem to be anything for minipages. You'll make it, won't you ;) (btw.: I did know we don't have it) Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Household hint: If you are out of cream for your coffee, mayonnaise makes a dandy substitute.
RE: buglet with insettext (collapsable insets?)
On 19-Jul-2001 Jean-Marc Lasgouttes wrote: > 3/ when going through the (empty) footnote, the document gets the > (changed) status; this does not happen if there is text in the > footnote. I'll have a look at this! BTW.: Find/Search actions do the same I'll have a look at that right now ;) Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ The purpose of Physics 7A is to make the engineers realize that they're not perfect, and to make the rest of the people realize that they're not engineers.
Re: Re-implementing open-stuff [questions about insets and signa
> "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes: Juergen> On 19-Jul-2001 Jean-Marc Lasgouttes wrote: Juergen> Sure we have one, don't we?! >> It seems that we don't. Tabulars have layout-tabular, but there >> does not seem to be anything for minipages. Juergen> You'll make it, won't you ;) (btw.: I did know we don't have Juergen> it) Making one is not a problem, but I'm looking for ideas on a convenient interface... JMarc
Re: Patch: version build info added.
> "R" == R Lahaye <[EMAIL PROTECTED]> writes: R> Hi, R> I thought it'll be useful to have an option R>lyx -version (or: lyx --version ) R> that will tell appropriate information on the R> system/build/compilation. This is very useful when reporting bug R> reports; once as executable, it is not so easy to find out how it R> was generated. Looks like an excellent idea. A simpler solution would probably be to generate this data in a file that would be installed along with LyX. This way the information would be available even when LyX cannot be launched. JMarc
Re: mathed103.diff
On Thu, Jul 19, 2001 at 06:29:16AM +0200, Andre Poenitz wrote: > > The standard 'spreadsheet' rules for never deleting cells in their > > complexity may be elegant (and they are), but the flexibility to > > join/split/pad rows just by inserting or deleting & and \\ sequences > > is one of the main things that drives me out of LyX into xemacs/TeX. > > It would be very nice to have the flexibility you get in a text editor > > in LyX. > > > > I think you both understand this, though :) > > So what scheme do you propose? Now you've put me on the spot. Fair enough. I want to be able to break cells (split this column into two, moving everything to the right of the cursor one cell to the right), break lines (thats enough for this row, everything currently in this row becomes part of a new row) and shift everything to the right. The first and third of these are the equivalent to typing the one character sequence '&' in the TeX source, the middle is like typing '\\'. I also want to be able to join cells (equivalent to deleting &) and rows (more rarely). It's just a lot less convenient to have to use cut and paste for these (especially if I have to bring up a dialog box if I want to modify the number of columns there are). I honestly do this stuff quite a lot. Imagine an equation x & = & f(g(blah...)) + h(...foo) suppose it gets too long. Then I put my insertion point before the plus, and type \\ & & and get x & = & f(g(blah...)) \\ & & + h(...foo) (this is in an eqnarray, as an example). Jules
Re: Import ASCII as Verse
Jean-Marc Lasgouttes wrote: > > > "Garst" == Garst R Reese <[EMAIL PROTECTED]> writes: > Hmmm... This means import as lines should keep line break as line > breaks and change double line breaks to paragraph break. This seems > reasonable, in fact. Why don't we do that always? I'd like to know > what people think about that... > > Garst> Yes. It also would have been nice if when in paragraph=verse, > Garst> an [enter] would have been interpreted as a line break and > Garst> C-[enter] as a paragraph break, but changing the behaviour now > Garst> is probably a bad idea. > > Yes, it is probably a very very bad idea :) If we do that, next time > tou will ask that in verses footnote are output as tabulars and > tabulars as footnotes... > > JMarc :) But in poetry, linebreaks function as end of sentence or phrase and stanzas as paragraphs. Considering all of the wierd stuff you let mathematicians do, I don't think it out of line to cater to poets aussi. Garst (who does both)
Re: Natbib announcement
On Thursday 19 July 2001 12:21, Jürgen Spitzmüller wrote: > On Wednesday, 18. July 2001 19:39, Angus Leeming wrote: > > Those willing to help save the CVS head repository from contamination > > with junk code should: > > > > cvs checkout -r BRANCH_NATBIB lyx-devel > > > > To get natbib support you'll need to set some parameters in the > > Document->Extra tab > > It should be obvious which ones! > > Hm, I really would like to test, but I can't get Natbib in. > I did (without concept ;-) > cvs checkout -r BRANCH_NATBIB lyx-devel > make distclean > ./autogen.sh > ./configure ; make > start lyx from the cvs directory. But there is no Natbib (still have > the huge citation dialog and nothing in Document -> Extra. > > I'm a CVS newbie, so any help is appreciated! > > Thanks, > Jürgen. Well, now it's in head so just update and play. Angus
Re: mathed103.diff
> (this is in an eqnarray, as an example). It looks as , and at the beginning of an cell is what you are looking for. Andre' -- André Pönitz . [EMAIL PROTECTED]
Re: Natbib announcement (and 666 inset gripes)
On Thu, Jul 19, 2001 at 09:21:51AM +0200, Juergen Vigna wrote: > > On 18-Jul-2001 Mike Ressler wrote: > > > This is not a stunning example of WYSIWYM. Please, please, (Lars?) change > > the appearance back to the old behavior!!! > > I don't think this will happen. What will happen is that we will change > the InsetERT to be inlined. What will NOT happen is that a inlined ERT > inset breaks row, so this is really thought only for short stuff! can't you un-inline the ert inset automagically when it extends beyond the right margin of the workarea ? john -- "Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything." - Karl Lehenbauer
Re: Re-implementing open-stuff [questions about insets and signa
On Thu, Jul 19, 2001 at 03:26:42PM +0200, Jean-Marc Lasgouttes wrote: > Making one is not a problem, but I'm looking for ideas on a convenient > interface... why not a settings key/lyxfunc which will automagically do ->edit() to bring up the right dialog in any circumstance ? It could even bring up the Paragraph dial in a para. Or am I missing the discussion ? it would quite nice if the inset button had an "?" button next to it which brought up the dialog perhaps regards john -- "Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything." - Karl Lehenbauer
Re: Natbib announcement (and 666 inset gripes)
On 19-Jul-2001 John Levon wrote: > can't you un-inline the ert inset automagically when it extends beyond the right >margin > of the workarea ? Probably yes, but do I want to do this? Probably no, as then I would get complaints about this automatic behaviour someone surely doesn't like! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Life sucks, but death doesn't put out at all. -- Thomas J. Kopp
Re: Natbib announcement (and 666 inset gripes)
On Thu, Jul 19, 2001 at 05:08:12PM +0200, Juergen Vigna wrote: > > On 19-Jul-2001 John Levon wrote: > > > can't you un-inline the ert inset automagically when it extends beyond the right >margin > > of the workarea ? > > Probably yes, but do I want to do this? Probably no, as then I would get > complaints about this automatic behaviour someone surely doesn't like! Think about the alternative - I add a lot of ert into the inset, so it is drawn off the side, and I can't even read it ! Surely we dont really have/want a choice in this circumstance. john -- "Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything." - Karl Lehenbauer
