Re: find/replace with lyx objects (such as ERTs, footnotes, etc.) [ regexes]
On Fri, 27 May 2005, Sven Schreiber wrote: So Kevin, have you opened a bug for that yet? If so, I would like to add a comment/ interim suggestion: I have just discovered that using the Navigate - Note menu item is very useful to do just that, navigate from note to note. Is there any reason why not all inset types have entries in the Navigate menu? (Especially footnotes and ERT.) I missed the earlier part of this thread, but the suggestion sound useful.. perhaps you could make a separate bugzilla entry for it? Btw, as far as I know, the developers usually prefer small and separate bugzilla entries. Please direct me to the appropriate bugzilla entries if those exist. (I have briefly searched for inset so far.) Thanks. AFAIK, it's not really a problem if you do happen to add a bugzilla entry that's similar to one that already exists - it'll eventually just get marked as a duplicate of that other entry. (I assume someone will correct me if I'm wrong here :-) /Christian -- Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
Re: lyx command for do not indent paragraph?
On 5/20/05, G. Milde [EMAIL PROTECTED] wrote: Is there a way to bind a key combination to an ERT box containing \noindent? (I've never tried to create a key binding to produce ERT -- that I can recall, at least.) command-sequence ert-insert; self-insert \noindent; inset-toggle; And without any insertion of ERT, is it possible the non-indentation of a paragraph, binding a key combination? Paul
Re: Converting from older version
Am Samstag, 28. Mai 2005 11:16 schrieb Christian Payne: I created this file and still get the same error. I downloaded the program suggested also on that page and the same result. I then tried running this program manually from the command line but the results loaded into LyX are totally messed up. This looks like a lyx2lyx bug, assuming you get no errors when you run it. Is this problem caused by the Windows version? Maybe. But unless you tell us the exact errors messages of lyx2lyx we can't know. Would installing a recent Linux version and using this to do the conversion help? Maybe. Or is it simply that files from my old version (1.1.6fix4) are just too old to be accessed in the more recent version? If so, what are my options? lyx2lyx is supposed to convert your files just fine. I'd suggest the following procedure: Run lyx2lyx from the commandline on your file: python lyx2lyx yourfile.lyx convertedfile.lyx Replace python with the full path to your python executable if it is not in your path. If you get errors, post them to the list. If not, try loading the converted file in lyx. If that gives errors, try to reduce your file to a minimal example file that still produces the errors and post that file. Of course the best option would be to find the bug in lyx2lyx and send a patch to fix it ;-) Georg
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
Mike Shell has identified the problem -- it is not a LyX problem, nor is it related to hyperref (as I thought) but a bug relating to the combination babel+fancyhdr+natbib. See http://groups.google.de/group/comp.text.tex/browse_frm/thread/d9bb4d8e289ef353/[EMAIL PROTECTED]rnum=1hl=de#77ad3282f3f8578c He suggests an easy workaround seems to eliminate the problem completely (id did so in my case). Cheers Ekkehart
Re: find/replace with lyx objects (such as ERTs, footnotes, etc.) [ regexes]
On Fri, 27 May 2005, Sven Schreiber wrote: So Kevin, have you opened a bug for that yet? If so, I would like to add a comment/ interim suggestion: I have just discovered that using the Navigate - Note menu item is very useful to do just that, navigate from note to note. Is there any reason why not all inset types have entries in the Navigate menu? (Especially footnotes and ERT.) I missed the earlier part of this thread, but the suggestion sound useful.. perhaps you could make a separate bugzilla entry for it? Btw, as far as I know, the developers usually prefer small and separate bugzilla entries. Please direct me to the appropriate bugzilla entries if those exist. (I have briefly searched for inset so far.) Thanks. AFAIK, it's not really a problem if you do happen to add a bugzilla entry that's similar to one that already exists - it'll eventually just get marked as a duplicate of that other entry. (I assume someone will correct me if I'm wrong here :-) /Christian -- Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
Re: lyx command for do not indent paragraph?
On 5/20/05, G. Milde [EMAIL PROTECTED] wrote: Is there a way to bind a key combination to an ERT box containing \noindent? (I've never tried to create a key binding to produce ERT -- that I can recall, at least.) command-sequence ert-insert; self-insert \noindent; inset-toggle; And without any insertion of ERT, is it possible the non-indentation of a paragraph, binding a key combination? Paul
Re: Converting from older version
Am Samstag, 28. Mai 2005 11:16 schrieb Christian Payne: I created this file and still get the same error. I downloaded the program suggested also on that page and the same result. I then tried running this program manually from the command line but the results loaded into LyX are totally messed up. This looks like a lyx2lyx bug, assuming you get no errors when you run it. Is this problem caused by the Windows version? Maybe. But unless you tell us the exact errors messages of lyx2lyx we can't know. Would installing a recent Linux version and using this to do the conversion help? Maybe. Or is it simply that files from my old version (1.1.6fix4) are just too old to be accessed in the more recent version? If so, what are my options? lyx2lyx is supposed to convert your files just fine. I'd suggest the following procedure: Run lyx2lyx from the commandline on your file: python lyx2lyx yourfile.lyx convertedfile.lyx Replace python with the full path to your python executable if it is not in your path. If you get errors, post them to the list. If not, try loading the converted file in lyx. If that gives errors, try to reduce your file to a minimal example file that still produces the errors and post that file. Of course the best option would be to find the bug in lyx2lyx and send a patch to fix it ;-) Georg
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
Mike Shell has identified the problem -- it is not a LyX problem, nor is it related to hyperref (as I thought) but a bug relating to the combination babel+fancyhdr+natbib. See http://groups.google.de/group/comp.text.tex/browse_frm/thread/d9bb4d8e289ef353/[EMAIL PROTECTED]rnum=1hl=de#77ad3282f3f8578c He suggests an easy workaround seems to eliminate the problem completely (id did so in my case). Cheers Ekkehart
Re: find/replace with lyx objects (such as ERTs, footnotes, etc.) [& regexes]
On Fri, 27 May 2005, Sven Schreiber wrote: > So Kevin, have you opened a bug for that yet? If so, I would like to add > a comment/ interim suggestion: > > I have just discovered that using the "Navigate - Note" menu item is > very useful to do just that, navigate from note to note. Is there any > reason why not all inset types have entries in the Navigate menu? > (Especially footnotes and ERT.) I missed the earlier part of this thread, but the suggestion sound useful.. perhaps you could make a separate bugzilla entry for it? Btw, as far as I know, the developers usually prefer small and separate bugzilla entries. > Please direct me to the appropriate bugzilla entries if those exist. (I > have briefly searched for "inset" so far.) Thanks. AFAIK, it's not really a problem if you do happen to add a bugzilla entry that's similar to one that already exists - it'll eventually just get marked as a duplicate of that other entry. (I assume someone will correct me if I'm wrong here :-) /Christian -- Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
Re: lyx command for "do not indent paragraph"?
On 5/20/05, G. Milde <[EMAIL PROTECTED]> wrote: > > Is there a way to bind a key combination to an ERT box containing > > \noindent? (I've never tried to create a key binding to produce ERT -- > > that I can recall, at least.) > > "command-sequence ert-insert; self-insert \noindent; inset-toggle;" And without any insertion of ERT, is it possible the non-indentation of a paragraph, binding a key combination? Paul
Re: Converting from older version
Am Samstag, 28. Mai 2005 11:16 schrieb Christian Payne:
> I created this file and still get the same error. I downloaded the
> program suggested also on that page and the same result. I then tried
> running this program manually from the command line but the results
> loaded into LyX are totally messed up.
This looks like a lyx2lyx bug, assuming you get no errors when you run it.
> Is this problem caused by the Windows version?
Maybe. But unless you tell us the exact errors messages of lyx2lyx we
can't know.
> Would installing a recent
> Linux version and using this to do the conversion help?
Maybe.
> Or is it simply
> that files from my old version ("1.1.6fix4") are just too old to be
> accessed in the more recent version? If so, what are my options?
lyx2lyx is supposed to convert your files just fine. I'd suggest the
following procedure:
Run lyx2lyx from the commandline on your file:
python lyx2lyx yourfile.lyx > convertedfile.lyx
Replace python with the full path to your python executable if it is not
in your path.
If you get errors, post them to the list.
If not, try loading the converted file in lyx.
If that gives errors, try to reduce your file to a minimal example file
that still produces the errors and post that file.
Of course the best option would be to find the bug in lyx2lyx and send a
patch to fix it ;-)
Georg
Re: Strange behavior LyxWin qt 1.3.5 - possibly relating to Bibtex
Mike Shell has identified the problem -- it is not a LyX problem, nor is it related to hyperref (as I thought) but a bug relating to the combination babel+fancyhdr+natbib. See http://groups.google.de/group/comp.text.tex/browse_frm/thread/d9bb4d8e289ef353/[EMAIL PROTECTED]=1=de#77ad3282f3f8578c He suggests an easy workaround seems to eliminate the problem completely (id did so in my case). Cheers Ekkehart
