Re: SIGSEV in CVS
Allan Rae wrote: > I took an extra seven seconds to look further and found it was a doddle to > fix so this will be committed in a couple of minutes. > > Allan. (ARRae) That problem fixed. Now, how about another 7 sec? This one came in yesterday. I insert a hard space, that works. Backspace over it and it does not go away. Delete adds another hard space (Ctrl space). Here's -dbk key Workarea event: KEYBOARD XLookupBoth WorkArea: Key is `' [0] WorkArea: Keysym is `space' [32] KeySym is space[32] Key [66][C-space] LyX: X11 color RoyalBlue allocated for special char Workarea event: KEYBOARD XLookupBoth WorkArea: Key is `' [8] WorkArea: Keysym is `BackSpace' [65288] KeySym is BackSpace[65288] Key [67][BackSpace] Workarea event: KEYBOARD XLookupKeySym WorkArea: Key is `Left' [65361] WorkArea: Keysym is `Left' [65361] KeySym is Left[65361] Key [39][Left] Workarea event: KEYBOARD XLookupBoth WorkArea: Key is `' [127] WorkArea: Keysym is `Delete' [65535] KeySym is Delete[65535] Key [66][Delete] TextCache::add 0x833e358 deleted TextCache: BufferView::buffer TextCache: buffer delete all Running QuitLyX.
RE: Any Plans on Using My Pspell Library Soon
On 31-Aug-2000 Kevin Atkinson wrote: > > Well, I download the cvs version, Unfortunately I can't get a useful core > dump because LyX catches SIGSERV, how can I avoid this > On what system type are you working on? I GET useful core-dumps and have no problem starting lyx with gdb and see what happens after a segfault (also with a library if I have the library sources and it's compiled with debug info!) Lars do you understand what he means? I have to admit that I'm clueless! 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 aims are high, and you are capable of much.
Re: Any Plans on Using My Pspell Library Soon
Juergen Vigna <[EMAIL PROTECTED]> writes: | On 31-Aug-2000 Kevin Atkinson wrote: | > | > Well, I download the cvs version, Unfortunately I can't get a useful core | > dump because LyX catches SIGSERV, how can I avoid this | > | | On what system type are you working on? I GET useful core-dumps and | have no problem starting lyx with gdb and see what happens after a | segfault (also with a library if I have the library sources and it's | compiled with debug info!) | | Lars do you understand what he means? I have to admit that I'm clueless! I guess tat if he runs LyX from inside gdb instead of trying to attach gdb to a core file he will have no problem. Lgb
patch for DEC c++
Hello all. I've returned to work, having had a wonderful time in Canada for a couple of weeks. Attached is a small patch to allow compilation of the current CVS with DEC c++. I'm not yet subscribed to the list again, so please CC me with any replies/queries. Angus patch31Aug2000.bz2
[dgalanak@hotmail.com] [Lyx-feedback] Feedback from www.lyx.org
Dimitris Galanakis ([EMAIL PROTECTED]) entered the following feedback message on the LyX home page: Hello, I am trying to use lyx for writting greek. I noticed that I can use reasonably well the babel package (through lyx) and write greek with latin characters. Unfortunately Lyx does not seem to support the greek encoding ( Layout->Document->Encoding). I am wondering if it is possible to also add the iso-8859-7 encoding in lyx options. Is this something I can also do? or should I wait for an updated version. Thanx for your time bye ___ Lyx-feedback mailing list [EMAIL PROTECTED] http://www.lyx.org/mailman/listinfo/lyx-feedback
casting and enums (ButtonPolicies)
Seems to me that someone has not quite understood how to avoid casting
when working with enums.
First: whenevery you have to use a cast you should think: "Something fishy is going
on, how can I avoid this."
Remember also when working with enums: c++ can overload operators so
that:
enum Button { one, two three };
inline Button operator|(Button a, Button b) {
return Button(a | b);
}
Button all = one | two | three;
will compile without warning, anoter option in this case is to use a
more special kind of "cast":
Button all = Button(one | two | three);
I have removed all casts from ButtonPolicies + changed what Angus did
you work around wrong use of casts. (casting a enum val to a ref to
int is _bad_)
Please try it out.
Lgb
Patch
Attached is a patch to add some features to InsetGraphics. This is an initial work, it includes several things: 1. Automatic conversion of graphics to PDF and EPS, currently it does them both everytime, needed is a differentiation, it depends on knowledge of the intended result and the used programs (pdflated versus ps2pdf) 2. LyXImage - a platform independent container of images. 3. Fix for lyx_cb.C (ShowMessage) to add a const. -- Baruch Even http://techst02.technion.ac.il/~sbaruch/ (My Site) http://www.redrival.com/jindor/(My brothers AD&D site) " Learn to laugh ... it's the path to true love! " - The Angel in the movie Michael patch.diff.gz
Re: Patch
Baruch Even <[EMAIL PROTECTED]> writes: | Attached is a patch to add some features to InsetGraphics. You changelog is weird... You have small inserts in several places in the file. Please put all you changes at the top. Even if they were written some time ago. Lgb
Re: New export code
On 30-Aug-2000 Lars Gullik Bjønnes wrote:
>| Did you forgot tex has if/then clauses ?
>| It is possible to use the same file with both latex/pdflatex:
>|
>| \newif \ifpdf
>|\ifx \pdfoutput \undefined
>| \pdffalse
>|\else
>| \pdftrue
>| \fi
>|
>| \ifpdf
>| \usepackage[pdftex]{hyperref}
>| \else
>| \usepackage[dvips]{hyperref}
>| \fi
>
> Yes, let's make the latex code as ugly as possible...
> It is a solution but it is not a nice one.
>
Well I like this solution (and already used it for foils Allan send
me for a Linux Meeting where I have to talk about LyX ;), so that I
can produce pdf and ps files with the same preamble!
AND I don't think this makes LaTeX files more ugly!
Jürgen
P.S.: Thanks Dekel for this solution! :)
P.P.S.: I also fixed the figinset to accept names without .eps extension
so that if you have the .eps AND .png files you have LyX inline
viewing AND also can produce pdffiles with the same latex output!
--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
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 education begins where what is called your education is over.
Re: New export code
Juergen Vigna <[EMAIL PROTECTED]> writes:
| On 30-Aug-2000 Lars Gullik Bjønnes wrote:
| >| Did you forgot tex has if/then clauses ?
| >| It is possible to use the same file with both latex/pdflatex:
| >|
| >| \newif \ifpdf
| >|\ifx \pdfoutput \undefined
| >| \pdffalse
| >|\else
| >| \pdftrue
| >| \fi
| >|
| >| \ifpdf
| >| \usepackage[pdftex]{hyperref}
| >| \else
| >| \usepackage[dvips]{hyperref}
| >| \fi
| >
| > Yes, let's make the latex code as ugly as possible...
| > It is a solution but it is not a nice one.
| >
|
| Well I like this solution (and already used it for foils Allan send
| me for a Linux Meeting where I have to talk about LyX ;), so that I
| can produce pdf and ps files with the same preamble!
|
| AND I don't think this makes LaTeX files more ugly!
It is ugly... especialy since the examply above is a very simplified
one, we get this same problem with url (the IfFileExists is ugly),
also pdflatex will almost require parameters tt are different feom the
latex' ones for hyperref.
_and_ that you have to do this in the preamble at all just shows that
support _in_ LyX is lacking. Changes to the preamble is often needed,
but it is still a hack and is ugly.
| P.S.: Thanks Dekel for this solution! :)
I fear that this is more of a pillow that will keep us from doing it
right fast... instead it will take a really long time.
Lgb
Re: New export code
On 31-Aug-2000 Lars Gullik Bjønnes wrote:
> also pdflatex will almost require parameters tt are different feom the
> latex' ones for hyperref.
You're right about the parameters I've used:
\ifpdf
\usepackage[pdftex=true,pdftitle={The Open Development of LyX},pdfauthor={Allan
Rae<[EMAIL PROTECTED]>}]{hyperref}
\else
\usepackage[dvips]{hyperref}
\fi
> _and_ that you have to do this in the preamble at all just shows that
> support _in_ LyX is lacking. Changes to the preamble is often needed,
> but it is still a hack and is ugly.
> I fear that this is more of a pillow that will keep us from doing it
> right fast... instead it will take a really long time.
The above code should be produced by LyX, so that the resulting LaTeX
file is portable and can be processed with pdflatex AND latex. If we
don't do this we can process the LaTeX file ONLY with one of the two
and that IMO IS bad.
Jürgen
P.S.: Have a nice weekend (I make a long on this week ;)
--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
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
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
We secure our friends not by accepting favors but by doing them.
-- Thucydides
Re: New export code
Juergen Vigna <[EMAIL PROTECTED]> writes:
| You're right about the parameters I've used:
|
| \ifpdf
| \usepackage[pdftex=true,pdftitle={The Open Development of LyX},pdfauthor={Allan
| Rae<[EMAIL PROTECTED]>}]{hyperref}
| \else
| \usepackage[dvips]{hyperref}
| \fi
Suspected that :-)
| The above code should be produced by LyX, so that the resulting LaTeX
| file is portable and can be processed with pdflatex AND latex. If we
| don't do this we can process the LaTeX file ONLY with one of the two
| and that IMO IS bad.
I strongly disagree. If you export to latex you are supposed to know
what you are doing. And this argument can also be used for other
latex's, f.ex. lambda (for omega what latex is to tex). And when we
move into more mulitiling. this will happen.
| P.S.: Have a nice weekend (I make a long on this week ;)
I thought you were on a full time vaction always, with some occasional
days of work mingled in :-)
Lgb
Re: bug: citations in figure floats
On Wed, Aug 30, 2000 at 03:35:42PM -0500, Chris Eliasmith wrote: > Hi, > > I didn't find this as a bug in the help section, so I > thought I should mention it. Whenever I include a citation > (M-i i) in a figure float, I get the following errors > on compile (at the end of the float): > Illegal parameter number in definition of \reserved@a > You meant to type ## instead of #, right? Or > maybe you forgot a } somewhere earlier? I'm going to assume you meant ##. Did you use the citation inset, or used some other cite command (e.g. \citen) ? To solve your problem, put \protect (in latex mode) before the citation.
LyX servers are changing ip addresses
The LyX servers are changing ip addresses and the might we some interuptions of services because of that. Hopefully this will be quickly done. I expect everything to be working ok quite soon. Lgb
Re: SIGSEGV Segmentation fault with 1.1.5 ) (more info)
On Thu, 31 Aug 2000, Allan Rae wrote:
Thank you very much for your info.
Here I'm sending more information in the attached file.
Sincerely,
Sasa
(gdb) bt
#0 0x402b01c8 in main_arena () from /lib/libc.so.6
#1 0x40215f7b in buffered_vfprintf (s=0x402b0120, format=0x4007e9f4 "%s%s\n",
args=0xb4f8) at vfprintf.c:1767
#2 0x402117c4 in vfprintf () at vfprintf.c:1565
#3 0x402192c7 in fprintf () at fprintf.c:36
#4 0x40073a74 in P_errmsg () from /usr/X11R6/lib/libforms.so.0.88
#5 0x400390a2 in fl_init_colormap () from /usr/X11R6/lib/libforms.so.0.88
#6 0x4003f217 in fl_initialize () from /usr/X11R6/lib/libforms.so.0.88
#7 0x80a843a in LyXGUI::LyXGUI (this=0x81d8ba0, owner=0xb84c,
argc=0xb8f4, argv=0xb954, GUI=true) at lyx_gui.C:127
#8 0x80aaa71 in LyX::LyX (this=0xb84c, argc=0xb8f4, argv=0xb954)
at ../src/lyx_main.C:77
#9 0x80c9fa3 in main (argc=1, argv=0xb954) at ../src/main.C:75
(gdb) up
#2 0x402117c4 in vfprintf () at vfprintf.c:1565
1565in vfprintf.c
(gdb)
(gdb) info args
No symbol table info available.
(gdb) info locals
_IO_helper_jumps = {__dummy = 0, __dummy2 = 0,
__finish = 0x402229b0 <_IO_default_finish>,
__overflow = 0x40215e00 <_IO_helper_overflow>,
__underflow = 0x40222530 <_IO_default_underflow>,
__uflow = 0x40222540 <_IO_default_uflow>,
__pbackfail = 0x40222e60 <_IO_default_pbackfail>,
__xsputn = 0x40222590 <_IO_default_xsputn>,
__xsgetn = 0x402226a0 <_IO_default_xsgetn>,
__seekoff = 0x40222a60 <_IO_default_seekoff>,
__seekpos = 0x40222810 <_IO_default_seekpos>,
__setbuf = 0x40222760 <_IO_default_setbuf>,
__sync = 0x402229a0 <_IO_default_sync>,
__doallocate = 0x40222860 <_IO_default_doallocate>,
__read = 0x40222fc0 <_IO_default_read>,
__write = 0x40222fd0 <_IO_default_write>,
__seek = 0x40222f90 <_IO_default_seek>,
__close = 0x402229a0 <_IO_default_sync>,
__stat = 0x40222fb0 <_IO_default_stat>, __showmanyc = 0, __imbue = 0}
null = "(null)"
(gdb)
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /usr/src/packages/SOURCES/lyx-1.1.5/src/lyx
Program received signal SIGSEGV, Segmentation fault.
0x402b01c8 in main_arena () from /lib/libc.so.6
(gdb)
Re: New export code
> I strongly disagree. If you export to latex you are supposed to know > what you are doing. Well. I usually export to LaTeX to hand out the result to people without LyX. They hand it out to other people etc. It will almost always be used on systems that I don't know. Maybe some of them don't have pdflatex installed, maybe some of those people use pdflatex exclusively. Being able to hand out .tex files that can be used in all circumstances is a big advantage. > And this argument can also be used for other > latex's, f.ex. lambda (for omega what latex is to tex). And when we > move into more mulitiling. Sure. But even 30 auto-generated lines in the created .tex is a small price when it buys flexibility... Andre' -- It'll take a long time to eat 63.000 peanuts. André Pönitz . [EMAIL PROTECTED]
Re: What is table-insert renamed to?
On Wed, Aug 30, 2000 at 09:05:20PM -0300, Garst R. Reese wrote: > I did not have *that* problem, but Ctrl space inserted a hard space > which backspace could not remove. Trying delete just inserted another > hard space. > Also, enabling NEW_EXPORT resulted in a failure to compile with a msg > about > Run_scripts or the like being missing. What did you do to enable the NEX_EXPORT ? You need to uncomment the "//#define NEW_EXPORT 1" in exporter.h Perhaps you did it in commandtags.h, which also might explain the delete problem you mentioned above (to fix it, just do make clean and recompile).
Re: LyX and PDF file generation
On Wed, Aug 30, 2000 at 10:53:33PM -0600, Michael O'Brien wrote:
> A little experimentation has shown that the incompatability lies within
> the default LyX preamble. The lines
> \usepackage[T1]{fontenc}
> \usepackage[latin1]{inputenc}
>
> create all the problems. If I export my document as a LaTeX file and
> remove these two lines, everything works perfectly. The computer modern
> fonts are embedded properly as Type1 fonts. I have also been able to
> use the "times" style package.
Only the first line is the cause of the problem.
You can prevent LyX from generating this line by adding
"\font_encoding default" to ~/.lyx/lyxrc
However, if you use European languages, you better use the T1 font encoding,
so leave lyxrc unchanged, and add "\usepackage{ae,aecompl}" to the preamble of
the LyX file.
See http://www.mail-archive.com/lyx-users@lists.lyx.org/msg06029.html
For more details
A note for lyx-devel list: Wouldn't it be better to make LyX automatically
add "\usepackage{ae,aecompl}" to the latex file if the font encoding is T1 ?
Just think of the endless questions on this subject we will get if LyX 1.1.6
do not do that (assuming that 1.1.6 will include my new view/export code,
which allows PDF file viewing/exporting).
Re: New export code
On Thu, Aug 31, 2000 at 04:45:14PM +0200, Juergen Vigna wrote: > > P.S.: Thanks Dekel for this solution! :) Actually, I got this code from lyx-users (it was posted by Matej Cepl).
Re: Feedback from www.lyx.org
> Dimitris Galanakis ([EMAIL PROTECTED]) entered the
> following feedback message on the LyX home page:
>
>
> Hello,
> I am trying to use lyx for writting greek. I noticed that I can use
> reasonably well the babel package (through lyx) and write greek with
> latin characters. Unfortunately Lyx does not seem to support the greek
> encoding ( Layout->Document->Encoding). I am wondering if it is possible
> to also add the iso-8859-7 encoding in lyx options. Is this something
> I can also do? or should I wait for an updated version.
> Thanx for your time
The CVS version automatically selects the encoding according to the language
of the document (it also allow multi-lingual documents with paragraph with
different encodings).
However, I don't know what is the latex name for Greek encoding (i.e. the
name you give pass to the fontenc package), so please provide it to me.
In the meantime, you can just select default encoding, and add
"\usepackage[greek-encoding-name]{fontenc}" to the preamble.
Re: What is table-insert renamed to?
Dekel Tsur wrote: > > On Wed, Aug 30, 2000 at 09:05:20PM -0300, Garst R. Reese wrote: > > > I did not have *that* problem, but Ctrl space inserted a hard space > > which backspace could not remove. Trying delete just inserted another > > hard space. > > Also, enabling NEW_EXPORT resulted in a failure to compile with a msg > > about > > Run_scripts or the like being missing. > > What did you do to enable the NEX_EXPORT ? > You need to uncomment the "//#define NEW_EXPORT 1" in exporter.h > Perhaps you did it in commandtags.h, which also might explain the delete > problem you mentioned above (to fix it, just do make clean and recompile). Do I uncomment it in both, or just exporter.h? Well, I guess I'll find out soon enough. OK, I uncommented in exporter.h only. The Ctrl space problem went away :) Should I also uncomment the line in commandtags.h? A comment in the code might be helpful in both places. Thanks Dekel Garst
RE: Any Plans on Using My Pspell Library Soon
On Thu, 31 Aug 2000, Juergen Vigna wrote: > > On 31-Aug-2000 Kevin Atkinson wrote: > > > > Well, I download the cvs version, Unfortunately I can't get a useful core > > dump because LyX catches SIGSERV, how can I avoid this > > > > Jürgen Kevin, Do you have a limit set on the coredumpsize? Type 'limit' [for sh/csh/tcsh], and see. Possibly you have core dumps disabled (limit=0 or something). If so, you can re-enable them with 'unlimit coredumpsize'. There is a manual page for these commands. HTH, Lior.
Math macro patch
After having some frustration from math macros bugs, I've decided to take a deep breath and dive into the mathed code. I've managed to fix two bugs: 1) If a math macro is used in subscript/superscript, or if the argument of a macro contains a big operator, there are display bugs. I've fixed it by adding "tmplate->SetStyle(size)" to MathMacro::Metrics, to match the corresponding line in MathMacro::draw. 2) If there are math macros in the document, the positioning of latex/checktex error insets is wrong. This happens as InsetFormulaMacro::Latex returns the wrong value (1). I changed the return value to 2. The patch should also go into the 1.1.5 branch. patch.gz
Re: What is table-insert renamed to?
On Thu, Aug 31, 2000 at 03:00:51PM -0300, Garst R. Reese wrote: > Dekel Tsur wrote: > > What did you do to enable the NEX_EXPORT ? > > You need to uncomment the "//#define NEW_EXPORT 1" in exporter.h > > Perhaps you did it in commandtags.h, which also might explain the delete > > problem you mentioned above (to fix it, just do make clean and recompile). > Do I uncomment it in both, or just exporter.h? Well, I guess I'll find > out soon enough. > OK, I uncommented in exporter.h only. The Ctrl space problem went away > :) > Should I also uncomment the line in commandtags.h? That is unnecessary. And please keep in mind that the new export code is still incomplete.
Re: What is table-insert renamed to?
Dekel Tsur wrote: > > On Thu, Aug 31, 2000 at 03:00:51PM -0300, Garst R. Reese wrote: > > Dekel Tsur wrote: > > > What did you do to enable the NEX_EXPORT ? > > > You need to uncomment the "//#define NEW_EXPORT 1" in exporter.h > > > Perhaps you did it in commandtags.h, which also might explain the delete > > > problem you mentioned above (to fix it, just do make clean and recompile). > > Do I uncomment it in both, or just exporter.h? Well, I guess I'll find > > out soon enough. > > OK, I uncommented in exporter.h only. The Ctrl space problem went away > > :) > > Should I also uncomment the line in commandtags.h? > > That is unnecessary. > And please keep in mind that the new export code is still incomplete. Yes, thanks. I don't have immediate needs, so just wanted to play and test. Let me know if you have specific things you want tried. Garst
Re: casting and enums (ButtonPolicies)
On 31 Aug 2000, Lars Gullik Bjønnes wrote: > Seems to me that someone has not quite understood how to avoid casting > when working with enums. > > First: whenever you have to use a cast you should think: "Something > fishy is going on, how can I avoid this." That's what I was thinking. I was also concerned why Dekel was getting the warnings he was so we had some private discussions. I was more concerned with why he was getting warnings and I couldn't with any compiler I have no matter what flags I used. Although I can get a warning from 2.95.2 when using -pedantic, complaining about using SMI_TOTAL where it wants an integer. Maybe that should be ButtonPolicy::SMI_TOTAL instead? > I have removed all casts from ButtonPolicies + changed what Angus did > you work around wrong use of casts. Thanks. This looks more sensible. > (casting a enum val to a ref to int is _bad_) Definitely agree here. Allan. (ARRae)
Re: What is table-insert renamed to?
On Fri, 1 Sep 2000, Dekel Tsur wrote: > On Thu, Aug 31, 2000 at 03:00:51PM -0300, Garst R. Reese wrote: > > Dekel Tsur wrote: > > > What did you do to enable the NEX_EXPORT ? > > > You need to uncomment the "//#define NEW_EXPORT 1" in exporter.h > > > Perhaps you did it in commandtags.h, which also might explain the delete > > > problem you mentioned above (to fix it, just do make clean and recompile). > > Do I uncomment it in both, or just exporter.h? Well, I guess I'll find > > out soon enough. > > OK, I uncommented in exporter.h only. The Ctrl space problem went away > > :) > > Should I also uncomment the line in commandtags.h? > > That is unnecessary. Then remove it. Isn't this arguement enough for a --with-cucumber configure option? Then the appropriate NEW_IMPROVED_BUT_NOT_QUITE_WORKING_FEATURE flag could be set in config.h instead of some arbitrary file or files. Allan. (ARRae)
Re: LyX and PDF file generation
On Thu, 31 Aug 2000, Dekel Tsur wrote:
> A note for lyx-devel list: Wouldn't it be better to make LyX automatically
> add "\usepackage{ae,aecompl}" to the latex file if the font encoding is T1 ?
> Just think of the endless questions on this subject we will get if LyX 1.1.6
> do not do that (assuming that 1.1.6 will include my new view/export code,
> which allows PDF file viewing/exporting).
what if I want to \usepackage{pslatex} instead?
Allan. (ARRae)
anoncvs.lyx.org && www.lyx.org down?
ping does nothing, traceroute to aussie.lyx.org (195.0.254.205), 30 hops max, 38 byte packets ... 11 Norge2.NO.eu.net (193.71.71.17) 34.076 ms 33.891 ms 36.877 ms 12 storeslem.troll.no (195.139.0.102) 42.640 ms 46.310 ms 36.874 ms 13 * * * Marko
Re: anoncvs.lyx.org && www.lyx.org down?
The recent change of IP addresses hasn't filtered through yet. Or dns is incorrect somewhere in norway. Lars, baywatch is fine so maybe there is a small problem. FWIW aussie.lyx.org is now at 213.203.58.30 so you can just make an entry in your local machines /etc/hosts if you like (assuming you have access) On Fri, 1 Sep 2000, Marko Vendelin wrote: > ping does nothing, > traceroute to aussie.lyx.org (195.0.254.205), 30 hops max, 38 byte packets Allan. (ARRae)
Gnome: FormCitation
Hi! this patch adds FormCitation implementation for Gnome frontend. I've extended the standard features of this dialog by (1) adding a small BibTeX parser for presenting authors, title, journal name and year in the bibliography list; (2) adding the possibility for search the records that contain user-specified word(s). The dialog remembers its size, sizes of the paned views, and sizes of the columns in the list. I had to implement the BibTeX parser since I am not familiar with YACC which is used by other BibTeX-parsing programs. At least, it parsed all my BibTeX files. There is one performance issue which I would like to outline. It seems to me that LyX loads BibTeX files every time when FormCitation is called. It might be OK if the files are small, but for databases with more than 1000 records the loading takes several seconds. Can't we cache the BibTeX files as it is done by Emacs with reftex package, for example? Finally, is there anybody working on natbib support? Marko gnome.formcitation.patch.gz gnome.formcitation.newfiles.tar.gz
