"Clapp, Craig" writes:
> I have been encountering trouble with importing LaTeX files into LyX -
> up to the severity of program crashes.
>
> Attached is an example which causes tex2lyx.exe to crash and an empty
> .lyx file to be produced. The file 'journal.tex'
On Mon, Jul 13, 2009 at 6:46 PM, Pavel Sanda wrote:
>> Prehaps you could use the following description:
>> "When attempting to select a Math Inset, LyX unselects the inset
>> after a fraction of a second, which is clearly quite annoying when
>> trying to copy math insets. This occurred in r30414
On Mon, Jul 13, 2009 at 6:46 PM, Pavel Sanda wrote:
>> Prehaps you could use the following description:
>> "When attempting to select a Math Inset, LyX unselects the inset
>> after a fraction of a second, which is clearly quite annoying when
>> trying to copy math insets. This occurred in r30414
John McCabe-Dansted wrote:
> > what bug description should i fill into our status file? was that crash?
> > pavel
>
> No it wasn't a crash. It wouldn't let me select MathInsets, whenever I
> tried to select one it would unselect it under me. This seems to be
> arch dependent, it occurred in 64bit
On Mon, Jul 13, 2009 at 6:03 PM, Pavel Sanda wrote:
> John McCabe-Dansted wrote:
>> On Mon, Jul 13, 2009 at 5:37 PM, Pavel Sanda wrote:
>> >> On Sat, Jul 11, 2009 at 4:37 PM, John McCabe-Dansted
>> >> wrote:
>> >> > $ cat TestSelectInset.kt
>> >> > KEYCODE="\Ca\[BackSpace]\Cmasdf\[Right]\D9\S\[Le
John McCabe-Dansted wrote:
> On Mon, Jul 13, 2009 at 5:37 PM, Pavel Sanda wrote:
> >> On Sat, Jul 11, 2009 at 4:37 PM, John McCabe-Dansted
> >> wrote:
> >> > $ cat TestSelectInset.kt
> >> > KEYCODE="\Ca\[BackSpace]\Cmasdf\[Right]\D9\S\[Left]\D9X\Cs\D9"
> >> > TEST="! grep asdf $F.lyx"
> >> > DESC
On Mon, Jul 13, 2009 at 5:37 PM, Pavel Sanda wrote:
>> On Sat, Jul 11, 2009 at 4:37 PM, John McCabe-Dansted
>> wrote:
>> > $ cat TestSelectInset.kt
>> > KEYCODE="\Ca\[BackSpace]\Cmasdf\[Right]\D9\S\[Left]\D9X\Cs\D9"
>> > TEST="! grep asdf $F.lyx"
>> > DESC="r30414 unselects insets after a fractio
John McCabe-Dansted wrote:
> I was thinking that a big advantage of an automatically reproducible
> bug would be an automatic svn/git-bisect to identify exactly where the
> regression occurred.
>
> I have attached do_bisect.sh and do_bisect_nosvn.sh. I'll mention that
> these are only proof-of-con
I was thinking that a big advantage of an automatically reproducible
bug would be an automatic svn/git-bisect to identify exactly where the
regression occurred.
I have attached do_bisect.sh and do_bisect_nosvn.sh. I'll mention that
these are only proof-of-concepts, are not ready for real use, and
Am Samstag, 16. Juni 2007 06:31 schrieb hzluo:
> 2. I also dislike current tex2lyx structure. But I also
>dislike the idea of python script. If let me make the
>choice, I will choose flex, or flex+bison. Flex syntax
>is extremely suitable for parsers, for both programming
>and main
I'm glad to receive so many feedbacks for my patch :-)
And here I have to tell you some of my thoughts:
1. I made this patch is because I need it. I have to
convert .tex files including those features, and
convert between .tex and .lyx back and forth. I met
these problems addressed in the p
Abdelrazak Younes wrote:
> Georg Baum wrote:
> > The integration might have advantages (e.g. inplace tex2lyx for
clipboard
> > snippets), but file format changes will only play a marginal role. The
> > reason why it is some work to update tex2lyx to the newest file format
does
> > not lie in synta
Georg Baum wrote:
Abdelrazak Younes wrote:
Georg Baum wrote:
(and it would even be better if the python
phantom would be killed).
A phantom cannot be killed, it is not alive ;-)
Well, it is alive enough to have real world effects.
FYI Hangzai I have written somewhere in my TODO list that
Abdelrazak Younes wrote:
> Georg Baum wrote:
>> (and it would even be better if the python
>> phantom would be killed).
>
> A phantom cannot be killed, it is not alive ;-)
Well, it is alive enough to have real world effects.
> FYI Hangzai I have written somewhere in my TODO list that tex2lyx sh
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> FYI Hangzai I have written somewhere in my TODO list that
Abdelrazak> tex2lyx should be integrated into LyX. This would ease the
Abdelrazak> maintenance as we won't have to care about the LyX file
Abdelrazak> format co
Georg Baum wrote:
This might all sound very negative, please don't get that wrong. It is good
that somebody works on tex2lyx
+1
(and it would even be better if the python
phantom would be killed).
A phantom cannot be killed, it is not alive ;-)
FYI Hangzai I have written somewhere in my TO
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> 1) Jose plans to rewrite tex2lyx in python, so be aware that
Georg> all your work is wasted if he ever does that. The threat of the
Georg> python rewrite is the only reason why I did not convert tex2lyx
Georg> to the unicode file forma
hzluo wrote:
> Please test and give me feedback. Thanks!
I have a couple of comments you might want to consider or ignore:
1) Jose plans to rewrite tex2lyx in python, so be aware that all your work
is wasted if he ever does that. The threat of the python rewrite is the
only reason why I did not
Please test the attached.
First import enhance.tex and see the result, then use the patched version to
import it,
you can recognize the difference immediately.
And texTurnRound.lyx is a .lyx file with cases that lyx exports some latex
features
but tex2lyx can't read back. Please export it to .t
Lars Gullik Bjønnes wrote:
> John Levon <[EMAIL PROTECTED]> writes:
>
> | On Mon, Jul 21, 2003 at 06:21:17PM +0200, Lars Gullik Bj?nnes wrote:
> |
> | > boost::filesystem.
> |
> | You were against replacing our stuff with that last time I asked about
> | it.
> |
> | Besides, that's an absolute
John Levon <[EMAIL PROTECTED]> writes:
| On Mon, Jul 21, 2003 at 06:21:17PM +0200, Lars Gullik Bj?nnes wrote:
|
| > boost::filesystem.
|
| You were against replacing our stuff with that last time I asked about
| it.
|
| Besides, that's an absolutely massive patch (and I am strongly against
| on
Lars Gullik Bjønnes wrote:
> | Do people think this is a clean solution? Should I move the class into
> | its own files rather than putting it in support/filetools.[Ch]?
>
> Well... I think the boost::path stuff would do this...
>
> | Comments please.
>
> boost::filesystem.
My proposal:
On Mon, Jul 21, 2003 at 06:21:17PM +0200, Lars Gullik Bj?nnes wrote:
> boost::filesystem.
You were against replacing our stuff with that last time I asked about
it.
Besides, that's an absolutely massive patch (and I am strongly against
only using bits of boost::filesystem and bits of our support
Angus Leeming <[EMAIL PROTECTED]> writes:
| I remember having a rant sometime ago about the need for something better
| than our current handling of file names. My proposal was to have a helper
| class that would enable us to 'do the right thing' when reading/writing the
| buffer to file:
|
|
On Mon, Jul 21, 2003 at 03:40:15PM +, Angus Leeming wrote:
> Shrug. No, but this is a sample, encoding only the graphics inset with a
> FileName member. I can't see what can go wrong with write given that
> FileName stores the absolute path to the file and a flag save_abs_p
John Levon wrote:
> On Mon, Jul 21, 2003 at 12:28:29PM +, Angus Leeming wrote:
>
>> Might help if you had the patch...
>
> Have you tested this with things like "Save As" ?
>
> regards
> john
Shrug. No, but this is a sample, encoding only the grap
On Mon, Jul 21, 2003 at 12:28:29PM +, Angus Leeming wrote:
> Might help if you had the patch...
Have you tested this with things like "Save As" ?
regards
john
On Monday 21 July 2003 11:39 am, Andre Poenitz wrote:
> + void absFilename(string const abs_filename);
> string const &?
Umm. Yes. Thanks.
> @@ -144,7 +144,10 @@ void InsetGraphicsParams::Write(ostream
> // Do not write the default values
>
> if (!filename.empty()) {
> -
Angus Leeming wrote:
> Comments please.
Might help if you had the patch...
--
AngusIndex: src/support/filetools.h
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/support/filetools.h,v
retrieving revision 1.47
diff -u -p -r1.47 fil
On Mon, Jul 21, 2003 at 12:24:02PM +, Angus Leeming wrote:
> Comments please.
Patch please.
Andre'
--
Those who desire to give up Freedom in order to gain Security, will not have,
nor do they deserve, either one. (T. Jefferson or B. Franklin or both...)
I remember having a rant sometime ago about the need for something better
than our current handling of file names. My proposal was to have a helper
class that would enable us to 'do the right thing' when reading/writing the
buffer to file:
class FileName {
public:
FileName();
/*
Attached file:
Attached file:
"Untitled1.pif
Description: Binary data
Attached file:
"Document003.pif
Description: Binary data
Attached file:
"Movie_0074.mpeg.pif
Description: Binary data
Attached file:
"Document003.pif
Description: Binary data
Attached file:
"Document003.pif
Description: Binary data
Attached file:
"Movie_0074.mpeg.pif
Description: Binary data
Attached file:
Attached file:
"Movie_0074.mpeg.pif
Description: Binary data
Andre Poenitz wrote:
>
> > I had a fast look and what I don't like is all this some option
> > stuff couldn't that be handled with something like ,
> > as this seems much nicer too me!
>
This is precisely why this output is handled by a small function that I
can redefine at will.
> I think Pi
> I had a fast look and what I don't like is all this some option
> stuff couldn't that be handled with something like ,
> as this seems much nicer too me!
I think Pierre-Olivier got it right in general. It is some kind of
religious debate on what goes in ... and what goes in "...".
The best ru
On 12-Oct-2000 Gaillard Pierre-Olivier wrote:
> Hello,
Hello Pierre-Olivier!
>
> Here is a sample output of the new XML output I have added to my LyX
> copy.
> This has been produced by a patched version of LyX that uses
> XMLSAXPrettifier (which at the moment does not make
Hello,
Here is a sample output of the new XML output I have added to my LyX
copy.
This has been produced by a patched version of LyX that uses
XMLSAXPrettifier (which at the moment does not make pretty output, so
please bear with the poor formatting). I have added XMLWrite methods to
classes
garst gabbed,
> Hi rick, stupid question, but... did you run texhash and then
> reconfigure in LyX?
I wish I could say "no," but I did.
The problem continues with raw latex. I'm about ready to pull tre
plug on this machine and use my own box running freebsd, but I *really*
want to have t
"Richard E. Hawkins" wrote:
>
>
> > As it seems your dvips is misconfigured You must add parkave there.
> > Browse CTAN for docu and (perhaps) pre-configured packages with *.tfm.
>
> mmm, we figured out that debian's dvi was misconfigured a year or two ago. I wish
>they'd leave it misconf
arnd added,
> On Fri, 03 Sep 1999 13:36:54 -0500, Richard E. Hawkins wrote:
> >hawkinsttyp0:Jobs>locate parkave
> >/usr/X11R6/lib/X11/fonts/freefont/parkave.pfb
> Ha! Got you.
not quite :)
> This is a type 1 (postscript) font. Handling this is all
> very special. You won't survive without goo
On Fri, 03 Sep 1999 13:36:54 -0500, Richard E. Hawkins wrote:
>
>hawkinsttyp0:Jobs>locate parkave
>/usr/X11R6/lib/X11/fonts/freefont/parkave.pfb
Ha! Got you. This is a type 1 (postscript) font. Handling this is all
very special. You won't survive without good docu. First of all you
need the park
Arnd added,
> You need to tell metafont where to find parkave.mf etc. Locate this
> with
> locate parkave
> and modifiy your environment accordingly (syntax depends on your TeX
> distribution).
> Here for emTeX it is:
> set
> mfinput=D:\XFREE86\USR\EMTEX\mfinput!!;D:\XFREE86\USR\EMT
On Fri, 03 Sep 1999 10:04:28 -0500, Richard E. Hawkins wrote:
>When I export as latex, and run latex, I get errors for assorted sizes
>such as:
>
>(/usr/lib/texmf/tex/latex/base/ifthen.sty)kpathsea: Running mktextfm
>parkave
>mktextfm: Running mf \mode:=ljfour; mag:=1; nonstopmode; input parka
I've put debian on my "new" office machine--a 16mb P120, with about a
600 mb partition.
I can no longer get my fonts for letterhead and the like to work. Lyx
returns no errors, but the parkave stuff simply shows up as blank.
When I export as latex, and run latex, I get errors for assorted s
51 matches
Mail list logo
