Crash running spellcheck

[Algernon]

Hi Devs,

I'm giving minimal info because I want to report this before I forget,
as I can live with things as they are.

I did a google search on the web - couldn't find errors sufficiently
similar (and I'm not a 'C' programmer).

Just installed LyX 1.4.0pre3.  My first install, but I'll give a pre3 a shot.

After creating a new *short* (two lines) document, with one spelling
error and running spellcheck, LyX *may* crash (not always) with:

--
ControlSpellchecker::replace(description)
Assertion triggered in T* boost::scoped_ptrT::operator-() const
[with T = SpellBase] by failing check ptr != 0 in file
../../../boost/boost/scoped_ptr.hpp:94
LyX: Attempting to save document /home/mtlski/newfile1.lyx
  /home/mtlski/newfile1.lyx.emergency
  Save seems successful. Phew.
Aborted
--

I believe it is the same error every time, regardless of the word
misspelled.  Sometimes there is no error, but no suggested word list
either (although then a misspelled word will still be highlighted).

The suggested word list box when it appears always appears without a
window decoration.  Selecting on a word causes the crash.

Window manager is sWM.

I'll report more later as I play with this if a pre4 doesn't come out first.

- bernard

Re: Bugs status

[Jean-Marc Lasgouttes]

 Bo == Bo Peng [EMAIL PROTECTED] writes:

  Also, if you keep the extension to .lyx, you are going to
 overwrite  the file. What about exporting to .lyx13?
 
 Fine with me.

Bo But a more common approach is that the user is prompted for a new
Bo filename.

Yes, but this is more work :)

JMarc

Re: [Patch] (Re: Screen update improvements)

[Jean-Marc Lasgouttes]

 Michael == Michael Gerz [EMAIL PROTECTED] writes:

Michael I think we have to speed up selections and reduce flickering
Michael for 1.4.0. Right now, it is not a great joy to select text if
Michael the LyX windows covers the full screen.

Could you test the small patch posted by Abdel? I am curious to see
whether it helps on qt/win 3.

JMarc

beamer layout

[Jose' Matos]

Hi,
is there any reason why we are not shipping the beamer layout?

I know that the beamer carries the layout there but it is not 
automatically 
installed. If we carried such file it would work as soon as lyx detected the 
presence of beamer.

Someone asked for it in fedora devel list and I proposed to add the 
beamer 
layout to the lyx package there since in fedora beamer is packaged with 
tetex.

Best regards,
-- 
José Abílio

Re: beamer layout

[Uwe Stöhr]

Jose' Matos wrote:


is there any reason why we are not shipping the beamer layout?


I asked for this some time ago and Georg argumented that it is a special 
package for its own on some Linux systems that could cause problems. 
Georg is this still the case?


regards Uwe

p.s. I currently ship beamer.layout with my installer.

Re: beamer layout

[Jean-Marc Lasgouttes]

 Jose' == Jose' Matos [EMAIL PROTECTED] writes:

Jose' Hi, is there any reason why we are not shipping the beamer
Jose' layout?

It would be reasonable. I guess you should ask the beamer author what
he prefers.

JMarc

Re: Screen update improvements

[Jean-Marc Lasgouttes]

 Abdel == Abdel  [EMAIL PROTECTED] writes:

Abdel I guess so yes. Following patch will do so.

Do you see some improvement with the patch? I guess only qt3 could
benefit.

JMarc

Re: Linking failure on Mac

[Jean-Marc Lasgouttes]

 Bennett == Bennett Helm [EMAIL PROTECTED] writes:

Bennett Most recent cvs fails to link on Mac with gcc-3.3. Any hints?

Did you run autogen.sh over your 1.4.0pre3 distribution? What happens
of you don't? Nowadays, autogen replaces the automake/libtool files in
config/ and it may be that you replaced working files with non-working
ones...

JMarc

Re: How to speed up LyXText::breakParagraph?

[Jean-Marc Lasgouttes]

 Abdel == Abdel  [EMAIL PROTECTED] writes:

Abdel Oups I just notice a CutPaste problem. The prototype I am
Abdel proposing is as follow, sorry about that. Optionnally, insert
Abdel could return a reference or a pointer to the newly inserted
Abdel paragraph but I think that the get(size_t) function is cleaner.

I guess Lars won't like it because ParagraphList is not a good stl
container anymore... I guess what we are looking after is some
templatized container, and I am actually surprised that it does not
exists already.

BTW, don't you define ParagraphList::Iter twice?

JMarc

Re: How to speed up LyXText::breakParagraph?

[Jean-Marc Lasgouttes]

 Abdel == Abdel  [EMAIL PROTECTED] writes:

Abdel I have compiled this file with -O3 but the slowness is still
Abdel there. Indeed insertion inside a vector is known to be
Abdel inefficient. I have read the history about ParagraphList_fwd.h
Abdel 
(http://www.lyx.org/cgi-bin/viewcvs.cgi/lyx-devel/src/ParagraphList_fwd.h)
Abdel and I guess there might be some valid reason to choose a vector
Abdel instead of a list but performance wise, it shows, definitely. 

You may want also to read this thread about all the problems that
vector creates. I really think we shall get rid of it somehow, but it
should be in a transparent manner. I guess what we need is a vector of
pointers that emulates the vector behaviour.

JMarc

Re: beamer layout

[Uwe Stöhr]

Jean-Marc Lasgouttes wrote:


It would be reasonable. I guess you should ask the beamer author what
he prefers.


Some time ago I asked him if we could ship it directly with LyX and he 
allowed it (beamer is also under the GPL).


regards Uwe

Re: Bugs status

[Jean-Marc Lasgouttes]

 Bennett == Bennett Helm [EMAIL PROTECTED] writes:

  Note that you can compile it, but it does not run ;)

Bennett Thbpbpthpt!

I did try to do something after all!

 Did I ask you to try to compile with --disable-optimization
 already?

Bennett No, but it doesn't help:

So, just to make sure, you did a make clean and recompiled, didn't
you? 

JMarc

New Chktex.C patch.

[John C. McCabe-Dansted]

I have been playing with Chktex.C, and have made a patch against
lyx1.4.0pre3/Chktex.C which:
 - Drops the -v0 flag and uses the less cryptic default (-v1) ChkTeX format.
 - Uses error titles more informative than 'Chktex warning # n'.
 - Fixes the bug where filenames containing ':' do not parse correctly.
 - Removes the USE_BOOST_FORMAT #ifdef, and always uses the std C++ code which 
is simpler anyway.

I understand that due to the feature freeze this code is unlikely to included 
before 1.4.1.

-- 
John C. McCabe-Dansted
Masters Student


Chktex.C.patch.gz
Description: GNU Zip compressed data

Re: New Chktex.C patch.

[Jean-Marc Lasgouttes]

 John == John C McCabe-Dansted [EMAIL PROTECTED] writes:

John I have been playing with Chktex.C, and have made a patch against
John lyx1.4.0pre3/Chktex.C which: 

Could you provide a unified diff (diff -u)? It is easier to read.

John - Drops the -v0 flag and uses the less cryptic default (-v1)
John ChkTeX format. 

Would it be possible to use -v3 (lacheck), so that LyX can also use
lacheck for checking? I do not know which format is the best actually.

John - Uses error titles more informative than 'Chktex warning # n'.
John - Fixes the bug where filenames containing ':' do not parse
John correctly. - Removes the USE_BOOST_FORMAT #ifdef, and always
John uses the std C++ code which is simpler anyway.

I'll have to see the unified patch.

John I understand that due to the feature freeze this code is
John unlikely to included before 1.4.1.

Indeed. And for nontrivial features like that, expect 1.4.2 or later
(even 1.5 if there is a risk).

JMarc

Re: How to speed up LyXText::breakParagraph?

[Lars Gullik Bjønnes]

Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:

|  Abdel == Abdel  [EMAIL PROTECTED] writes:
| 
| Abdel Oups I just notice a CutPaste problem. The prototype I am
| Abdel proposing is as follow, sorry about that. Optionnally, insert
| Abdel could return a reference or a pointer to the newly inserted
| Abdel paragraph but I think that the get(size_t) function is cleaner.
| 
| I guess Lars won't like it because ParagraphList is not a good stl
| container anymore... I guess what we are looking after is some
| templatized container, and I am actually surprised that it does not
| exists already.

I don't don't like it, it is close to a solution I already had
thought of.

BUT I am not ready even to begin thinking about it, I want 1.4.1
finished first.

-- 
Lgb

Re: How to speed up LyXText::breakParagraph?

[Jean-Marc Lasgouttes]

 Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:

Lars I don't don't like it, it is close to a solution I already had
Lars thought of.

Good.

Lars BUT I am not ready even to begin thinking about it, I want 1.4.1
Lars finished first.

I could not agree more :)

JMarc

Re: How to speed up LyXText::breakParagraph?

[Lars Gullik Bjønnes]

Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:

|  Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
| 
| Lars I don't don't like it, it is close to a solution I already had
| Lars thought of.
| 
| Good.
| 
| Lars BUT I am not ready even to begin thinking about it, I want 1.4.1
| Lars finished first.
| 
| I could not agree more :)

except that I meant 1.4.0 of course...

-- 
Lgb

Re: How to speed up LyXText::breakParagraph?

[Jean-Marc Lasgouttes]

 Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:

| I could not agree more :)

Lars except that I meant 1.4.0 of course...

Damn!

JMarc

Re: Screen update improvements

[Abdel]

Jean-Marc Lasgouttes a écrit :

Abdel == Abdel  [EMAIL PROTECTED] writes:


Abdel I guess so yes. Following patch will do so.

Do you see some improvement with the patch? I guess only qt3 could
benefit.


Right now, I cannot compile with qt3, sorry. With my Qt4 port, there is 
no flicker but I have tested this nonetheless with a different syntax:


viewport()-setAttribute(Qt::WA_OpaquePaintEvent);

The result is not good: all the float buttons (foot, figure, table, 
etc) are black on black. The weird thing is that this behavior affects 
also my previously compiled Qt3 version. I presume that floats are not 
painted by the lyx core but use the background color instead, aren't 
they? Apparently setting this attribute is propagated system wide by Qt4.


Abdel.




JMarc

Re: How to speed up LyXText::breakParagraph?

[Abdel]

Jean-Marc Lasgouttes a écrit :

Abdel == Abdel  [EMAIL PROTECTED] writes:


Abdel Oups I just notice a CutPaste problem. The prototype I am
Abdel proposing is as follow, sorry about that. Optionnally, insert
Abdel could return a reference or a pointer to the newly inserted
Abdel paragraph but I think that the get(size_t) function is cleaner.

I guess Lars won't like it because ParagraphList is not a good stl
container anymore... I guess what we are looking after is some
templatized container, and I am actually surprised that it does not
exists already.


Well, if the class provide insert, erase and find, isn't that enought?
I think it is even possible to derive ParagraphList from 
vectorlistParagraph::iterator if we need the container interface. I 
can write a new proposal if you want.



BTW, don't you define ParagraphList::Iter twice?


Typo, sorry. I haven't tested this, I wrote the class within the email.



JMarc

[PATCH] Fix bibliography layout for CV textclass.

[Jean-Marc Lasgouttes]

The following change was probably forgotten by whoever introduced the
Bib_Environment tag.

Georg, is this something layout2layout c/should do?

I'll commit it, since it is trivial and fixes a regression (latex
output was \item \bibitem{foo}).

JMarc

Index: lib/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/ChangeLog,v
retrieving revision 1.752
diff -u -p -r1.752 ChangeLog
--- lib/ChangeLog	2 Jan 2006 19:15:25 -	1.752
+++ lib/ChangeLog	5 Jan 2006 11:48:20 -
@@ -1,3 +1,8 @@
+2006-01-05  Jean-Marc Lasgouttes  [EMAIL PROTECTED]
+
+	* layouts/cv.layout (Bibliography): change latextype to
+	Bib_Environment.
+
 2006-01-02  Michael Gerz  [EMAIL PROTECTED]
 
 	* layouts/amsart-seq.layout: fix typo in counter
Index: lib/layouts/cv.layout
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/layouts/cv.layout,v
retrieving revision 1.14
diff -u -p -r1.14 cv.layout
--- lib/layouts/cv.layout	21 Oct 2005 16:11:33 -	1.14
+++ lib/layouts/cv.layout	5 Jan 2006 11:48:20 -
@@ -143,6 +143,7 @@ End
 Style Bibliography
 	CopyStyle Topic
 	LatexName thebibliography
+	LatexType Bib_Environment
 	LabelType Bibliography
 	LabelString   
 	LabelBottomSep0.7

Bug reading layout files (layout2layout?)

[Juergen Spitzmueller]

LyX 1.4 seems to have major problems reading layout files containing capital 
letters. The attached layout file is just a copy of article.layout, renamed  
articleX.layout. If you try to switch to that layout, LyX is entering a long 
busy stage before it eventually returns the message Could not convert 
document class to articleX.

The console messages read: 

RunCommand:: could not start child process
Could not run layout conversion script layout2layout.py.
Error reading `~/.lyx-cvs/layouts/articleX.layout'
(Check `articleX')
Check your installation and try Options/Reconfigure...
RunCommand:: could not start child process
Could not run layout conversion script layout2layout.py.
Error reading `~/.lyx-cvs/layouts/articleX.layout'
(Check `articleX')
Check your installation and try Options/Reconfigure...
RunCommand:: could not start child process
Could not run layout conversion script layout2layout.py.
Error reading `~/.lyx-cvs/layouts/articleX.layout'
(Check `articleX')
Check your installation and try Options/Reconfigure...
RunCommand:: could not start child process
Could not run layout conversion script layout2layout.py.
Error reading `~/.lyx-cvs/layouts/articleX.layout'
(Check `articleX')
Check your installation and try Options/Reconfigure...

If you change the name to articlex.layout, everything is fine.

Jürgen
#% Do not delete the line below; configure depends on this
#  \DeclareLaTeXClass[article]{articleX}
# Article textclass definition file. Taken from initial LyX source code
# Author : Matthias Ettrich [EMAIL PROTECTED]
# Transposed by Pascal André [EMAIL PROTECTED]
# Heavily modifed and enhanced by serveral developers.

Format 2
Input stdclass.inc
Input numarticle.inc

SecNumDepth 3
TocDepth3

NoStyle Chapter
NoStyle Chapter*


Style Part
Align Left
AlignPossible Left
TopSep2
BottomSep 1.5
Font
  SizeLarger
EndFont
End


Style Part*
Align Left
AlignPossible Left
TopSep2
BottomSep 1.5
Font
  SizeLarger
EndFont
End

Re: Bug reading layout files (layout2layout?)

[Jose' Matos]

On Thursday 05 January 2006 11:53, Juergen Spitzmueller wrote:
 LyX 1.4 seems to have major problems reading layout files containing
 capital letters. The attached layout file is just a copy of article.layout,
 renamed articleX.layout. If you try to switch to that layout, LyX is
 entering a long busy stage before it eventually returns the message Could
 not convert document class to articleX.

Although not completely related I am writing a set of python parsers for 
layout files. The purpose is to use those lessons to simply their grammar for 
1.5 while at same allow the creation of tools to ease their creation.

It is really amazing the complexity of layout files now, article has more than 
300 lines (without blanks and comments)!

 Jürgen

-- 
José Abílio

Re: Instant preview in LyX/Win 1.4.0pre3

[Angus Leeming]

Enrico Forestieri wrote:

 Angus Leeming [EMAIL PROTECTED] writes:
 
 Oh, that's horrid and the one that follows is worse.
 What I think you should do is talk to David Kastrup and Jan-Åke Larsson
 on the AucTeX mailing list (gmane.emacs.auc-tex) and see why they're
 messing up the output that they devised for us.
 
 I tried dvipng 1.7 on linux and its output is exactly equal to what that
 RE matches. So it is not a problem with dvipng itself but seemingly with
 the dvipng shipped with MikTeX.

;-) Then I guess you know who to complain to.

I wonder if the MikTeX version is piping its stderr stream to stdout? (For
reasons unknown.)

-- 
Angus

[PATCH 13x, 14x] squash bug 2193

[Angus Leeming]

The attached patches fix bug 2193, just reported, but raised originally by
Uwe on 7 December. See thread
http://thread.gmane.org/gmane.editors.lyx.devel/50473

(instant preview fails if the path to the ghostscript executable contains
spaces.)

I guess the fix fell below the radar screen...

Anyway, the patch is obvious and works for me, so I'll just commit it.

-- 
AngusIndex: status.13x
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/Attic/status.13x,v
retrieving revision 1.1.2.282
diff -u -p -r1.1.2.282 status.13x
--- status.13x	12 Dec 2005 10:08:37 -	1.1.2.282
+++ status.13x	5 Jan 2006 14:02:13 -
@@ -69,6 +69,9 @@ What's new
 - On exit, don't attempt to unlock a mutex in the Qt library --- it
   causes undefined behaviour and leads to a crash on NetBSD.
 
+- Enable Instant Preview to work if the path to the external GhostScript
+  executable contains spaces. (bug 2193).
+
 * Configuration/Installation:
 
 - Enable TeXFiles.sh to run when its path contains spaces.
Index: lib/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/ChangeLog,v
retrieving revision 1.363.2.134
diff -u -p -r1.363.2.134 ChangeLog
--- lib/ChangeLog	19 Dec 2005 11:08:08 -	1.363.2.134
+++ lib/ChangeLog	5 Jan 2006 14:02:16 -
@@ -1,3 +1,9 @@
+2006-01-05  Angus Leeming  [EMAIL PROTECTED]
+
+	* scripts/lyxpreview2ppm.py (find_exe): return only the basename of
+	the executable to avoid problems when the path to the exe contains
+	spaces. Fixes bug 2193.
+
 2005-12-16  Georg Baum  [EMAIL PROTECTED]
 
 	* symbols: avoid use of symbol font if cmsy is available.
Index: lib/scripts/lyxpreview2ppm.py
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/scripts/Attic/lyxpreview2ppm.py,v
retrieving revision 1.1.2.7
diff -u -p -r1.1.2.7 lyxpreview2ppm.py
--- lib/scripts/lyxpreview2ppm.py	16 Jun 2005 13:15:11 -	1.1.2.7
+++ lib/scripts/lyxpreview2ppm.py	5 Jan 2006 14:02:17 -
@@ -93,7 +93,11 @@ def find_exe(candidates, path):
 full_path = os.path.join(directory, prog)
 
 if os.access(full_path, os.X_OK):
-return full_path
+# The thing is in the PATH already (or we wouldn't
+# have found it). Return just the basename to avoid
+# problems when the path to the executable contains
+# spaces.
+return os.path.basename(full_path)
 
 return None
 
Index: lib/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/ChangeLog,v
retrieving revision 1.752
diff -u -p -r1.752 ChangeLog
--- lib/ChangeLog	2 Jan 2006 19:15:25 -	1.752
+++ lib/ChangeLog	5 Jan 2006 14:04:44 -
@@ -1,3 +1,9 @@
+2006-01-05  Angus Leeming  [EMAIL PROTECTED]
+
+	* scripts/lyxpreview_tools.py (find_exe): return only the basename of
+	the executable to avoid problems when the path to the exe contains
+	spaces. Fixes bug 2193.
+
 2006-01-02  Michael Gerz  [EMAIL PROTECTED]
 
 	* layouts/amsart-seq.layout: fix typo in counter
Index: lib/scripts/lyxpreview_tools.py
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/scripts/lyxpreview_tools.py,v
retrieving revision 1.1
diff -u -p -r1.1 lyxpreview_tools.py
--- lib/scripts/lyxpreview_tools.py	9 Aug 2004 11:31:18 -	1.1
+++ lib/scripts/lyxpreview_tools.py	5 Jan 2006 14:04:44 -
@@ -52,7 +52,11 @@ def find_exe(candidates, path):
 full_path = os.path.join(directory, prog)
 
 if os.access(full_path, os.X_OK):
-return full_path
+# The thing is in the PATH already (or we wouldn't
+# have found it). Return just the basename to avoid
+# problems when the path to the executable contains
+# spaces.
+return os.path.basename(full_path)
 
 return None
 

Re: [PATCH 13x, 14x] squash bug 2193

[Jean-Marc Lasgouttes]

 Angus == Angus Leeming [EMAIL PROTECTED] writes:

Angus The attached patches fix bug 2193, just reported, but raised
Angus originally by Uwe on 7 December. See thread
Angus http://thread.gmane.org/gmane.editors.lyx.devel/50473

Angus (instant preview fails if the path to the ghostscript
Angus executable contains spaces.)

Angus I guess the fix fell below the radar screen...

Angus Anyway, the patch is obvious and works for me, so I'll just
Angus commit it.

Looks OK.

JMarc

Re: Crash running spellcheck

[Jean-Marc Lasgouttes]

 Algernon == Algernon  [EMAIL PROTECTED] writes:

Algernon I'll report more later as I play with this if a pre4 doesn't
Algernon come out first.

It would be nice if you could tell us what spellchecker is in used
(output of lyx -version would be fine) and give a precise recipe for
the crash.

JMarc

Re: Instant preview in LyX/Win 1.4.0pre3

[Enrico Forestieri]

Angus Leeming [EMAIL PROTECTED] writes:
 
 Enrico Forestieri wrote:
 
  I tried dvipng 1.7 on linux and its output is exactly equal to what that
  RE matches. So it is not a problem with dvipng itself but seemingly with
  the dvipng shipped with MikTeX.
 
  Then I guess you know who to complain to.
 
 I wonder if the MikTeX version is piping its stderr stream to stdout? (For
 reasons unknown.)

No, it is not like that. I can separately capture stderr and stdout.
I tried compiling dvipng 1.7 under cygwin, which should be more
reliable, and I am seeing a similar problem:

$ dvipng ...
This is dvipng 1.7 Copyright 2002-2005 Jan-Ake Larsson
dvipng warning: cannot find ps2pk.map, nor psfonts.map
[1 (preview-latex version 11.81) depth=6 height=16]

The warning should not matter. It is due to the fact that I used the
cygwin tetex-devel package (for libkpathsea) and simply did:

$ ln -s /c/texmf /usr/share/texmf

for using the MikTeX texmf tree, but unfortunately ps2pk.map and
psfonts.map are not in /c/texmf:

$ kpsewhich ps2pk.map
C:/localtexmf/dvips/config/ps2pk.map
$ kpsewhich psfonts.map
C:/localtexmf/dvips/config/psfonts.map

So, I am going to read the libkpathsea documentation for setting some
environment variable...

I'll see what it turns out to be. Having the sources, I can use ddd for
debugging dvipng.

--
Enrico

[Patch] speed patch revisited

[Martin Vermeer]

Please find attach the inside-inset speed patch, which now functions and
is as bug-free as I could get it.

There are still some rendering artefacts in corner cases, but none of
them look bad IMHO.

This is a somewhat complex and intrusive patch, and perhaps not for
1.4.0. But for 1.4.1 we should consider this -- together with the
inside-paragraph selection speed patch. I feel good about both.

Note that the patch was diffed from a dirty tree. It contains a
stowaway, the bool multiparsel_cache_ from the selection speed patch,
which should not cause trouble here.

- Martin

Index: BufferView.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/BufferView.C,v
retrieving revision 1.265
diff -u -p -r1.265 BufferView.C
--- BufferView.C	19 Dec 2005 11:47:13 -	1.265
+++ BufferView.C	5 Jan 2006 14:33:29 -
@@ -369,6 +369,18 @@ void BufferView::putSelectionAt(DocItera
 }
 
 
+bool const BufferView::repaintAll() const
+{ 
+	return pimpl_-repaintAll();
+}
+
+	
+void const BufferView::repaintAll(bool r) const
+{ 
+	pimpl_-repaintAll(r);
+}
+
+
 LCursor  BufferView::cursor()
 {
 	return pimpl_-cursor_;
Index: BufferView.h
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/BufferView.h,v
retrieving revision 1.189
diff -u -p -r1.189 BufferView.h
--- BufferView.h	1 Dec 2005 10:28:47 -	1.189
+++ BufferView.h	5 Jan 2006 14:33:29 -
@@ -198,7 +199,10 @@ public:
 	 */
 	void putSelectionAt(DocIterator const  cur,
 		int length, bool backwards);
-
+	///
+	bool const repaintAll() const;
+	///
+	void const repaintAll(bool r) const;
 
 private:
 	///
Index: BufferView_pimpl.h
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/BufferView_pimpl.h,v
retrieving revision 1.129
diff -u -p -r1.129 BufferView_pimpl.h
--- BufferView_pimpl.h	7 Nov 2005 15:06:42 -	1.129
+++ BufferView_pimpl.h	5 Jan 2006 14:33:29 -
@@ -103,6 +105,10 @@ public:
 	FuncStatus getStatus(FuncRequest const  cmd);
 	/// a function should be executed
 	bool dispatch(FuncRequest const  ev);
+	/// Flag: do a full redraw of inside text of inset
+	bool repaintAll() { return refresh_inside_; }
+	///
+	void repaintAll(bool r) {refresh_inside_ = r; }
 private:
 	/// An error list (replaces the error insets)
 	ErrorList errorlist_;
@@ -183,13 +189,17 @@ private:
 	///
 	LCursor cursor_;
 	///
+	bool multiparsel_cache_;
	///
 	lyx::pit_type anchor_ref_;
 	///
 	int offset_ref_;
 	///
 	ViewMetricsInfo metrics(bool singlepar = false);
-
-
+	/// Working variable indicating a full screen refresh
+	mutable bool refresh_;
+	/// Inside insets
+	mutable bool refresh_inside_;
+	
 };
 #endif // BUFFERVIEW_PIMPL_H
Index: rowpainter.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/rowpainter.C,v
retrieving revision 1.162
diff -u -p -r1.162 rowpainter.C
--- rowpainter.C	1 Jan 2006 23:06:23 -	1.162
+++ rowpainter.C	5 Jan 2006 14:33:30 -
@@ -164,7 +164,11 @@ void RowPainter::paintInset(pos_type con
 	pi.ltr_pos = (text_.bidi.level(pos) % 2 == 0);
 	pi.erased_ = erased_ || isDeletedText(par_, pos);
 	theCoords.insets().add(inset, int(x_), yo_);
-	inset-drawSelection(pi, int(x_), yo_);
+	InsetText const * in = static_castInsetText const*(inset);
+	if (in  in-isTextInset()  !in-wide_inset_)
+		bv_.repaintAll(true);
+	if (bv_.repaintAll())
+		inset-drawSelection(pi, int(x_), yo_);
 	inset-draw(pi, int(x_), yo_);
 	x_ += inset-width();
 }
@@ -729,8 +733,9 @@ lyx::size_type calculateRowSignature(Row
 }
 
 
-bool isCursorOnRow(PainterInfo  pi, pit_type pit, RowList::const_iterator rit)
+bool CursorOnRow(PainterInfo  pi, pit_type pit, RowList::const_iterator rit)
 {
+	// Is there a cursor on this row (or inside inset on row)
 	LCursor  cur = pi.base.bv-cursor();
 	for (lyx::size_type d = 0; d  cur.depth(); d++)
 		if (cur[d].pit() == pit
@@ -741,6 +746,20 @@ bool isCursorOnRow(PainterInfo  pi, pit
 }
 
 
+bool innerCursorOnRow(PainterInfo  pi, pit_type pit, RowList::const_iterator rit)
+{
+	// Is there a cursor inside an inset on this row, and is this inset
+	// the only character on this row
+	LCursor  cur = pi.base.bv-cursor();
+	if (rit-pos() + 1 != rit-endpos())
+		return false;
+	for (lyx::size_type d = 0; d  cur.depth(); d++)
+		if (cur[d].pit() == pit  cur[d].pos() == rit-pos())
+			return d  cur.depth() - 1;
+	return false;
+}
+
+
 void paintPar
 	(PainterInfo  pi, LyXText const  text, pit_type pit, int x, int y,
 	 bool repaintAll)
@@ -763,14 +782,25 @@ void paintPar
 
 		// Row signature; has row changed since last paint?
 		lyx::size_type const row_sig = calculateRowSignature(*rit, par);
+		bool row_has_changed = par.rowSignature()[rowno] != row_sig;
+		
+		bool cursor_on_row = CursorOnRow(pi, pit, rit);
+		bool in_inset_alone_on_row = innerCursorOnRow(pi, pit, rit);
+
+		// If this is the only 

Re: [Patch] speed patch revisited

[Lars Gullik Bjønnes]

Martin Vermeer [EMAIL PROTECTED] writes:

| Please find attach the inside-inset speed patch, which now functions and
| is as bug-free as I could get it.
| 
| There are still some rendering artefacts in corner cases, but none of
| them look bad IMHO.
| 
| This is a somewhat complex and intrusive patch, and perhaps not for
| 1.4.0. But for 1.4.1 we should consider this -- together with the
| inside-paragraph selection speed patch. I feel good about both.

IMHO, not for 1.4.0 but can be considered for 1.4.1.
(just to make my position clear)

-- 
Lgb

bug 2194: Double clicking in qrefs dialog broken

[Juergen Spitzmueller]

Angus,

do you remember why you did the changes below? Disconnecting those signals 
broke double-clicking in 1.4 as well as in 1.3.7cvs.
Can I re-connect them, please?

Jürgen

[EMAIL PROTECTED] wrote:
 CVSROOT:/usr/local/lyx/cvsroot
 Module name:lyx-devel
 Repository: lyx-devel/src/frontends/qt2/ui/
 Changes by: [EMAIL PROTECTED]05/07/23 23:54:49

 Modified files:
 lyx-devel/src/frontends/qt2/: ChangeLog
 lyx-devel/src/frontends/qt2/ui/: QRefDialogBase.ui

 Log message:
 Disconnect two signals --- forward port from 1.3.x.

 Patches:
 http://www.lyx.org/cgi-bin/viewcvs.cgi/lyx-devel/src/frontends/qt2/ChangeLo
g?r1=1.810r2=1.811
 http://www.lyx.org/cgi-bin/viewcvs.cgi/lyx-devel/src/frontends/qt2/ui/QRefD
ialogBase.ui?r1=1.9r2=1.10

 Complete Diff:
 /usr/bin/cvs -f diff -kk -u -r 1.810 -r 1.811 src/frontends/qt2/ChangeLog
 /usr/bin/cvs -f diff -kk -u -r 1.9 -r 1.10
 src/frontends/qt2/ui/QRefDialogBase.ui

Re: Linking failure on Mac

[Bennett Helm]

On Jan 5, 2006, at 4:40 AM, Jean-Marc Lasgouttes wrote:


Bennett == Bennett Helm [EMAIL PROTECTED] writes:


Bennett Most recent cvs fails to link on Mac with gcc-3.3. Any hints?

Did you run autogen.sh over your 1.4.0pre3 distribution? What happens
of you don't? Nowadays, autogen replaces the automake/libtool files in
config/ and it may be that you replaced working files with non-working
ones...


I'm not understanding here.

1.4.0pre3 works fine (and I did run autogen.sh); it's 1.4.0cvs that  
gives me the trouble. (And I did not manually run autogen.sh on it  
recently.)


Reverting ltmain.sh to the version before 30-Dec-2005 enables me to  
configure and make without problems. Reverting ltmain.sh back to the  
current version, reconfiguring, and making (without running  
autogen.sh) now works as well.


Bennett

Re: bug 2194: Double clicking in qrefs dialog broken

[Angus Leeming]

Juergen Spitzmueller wrote:
 do you remember why you did the changes below? Disconnecting those
 signals broke double-clicking in 1.4 as well as in 1.3.7cvs.
 Can I re-connect them, please?

Hi, Jürgen

No, I don't remember why, but the relevant entries in the ChangeLog are
below.

Angus


===
BRANCH_1_3_X
2005-07-22  Angus Leeming  [EMAIL PROTECTED]

* QRef.C (update_contents): disable the OK button when the dialog is
first shown. The user must first select a reference.

* QRefDialog.C (changed_adaptor): only enable the OK button when
the Label: field is not empty.
(refHighlighted): set the text in the Label: field only when
an item is currently selected in the Available refs browser. (When
th signal connected to this slot is triggered.)

===
Trunk:
2005-07-23  Angus Leeming  leeming AT lyx.org

* QRefDialogBase.ui: disconnect two refsLB signals to the
refSelected and changed_adaptor slots.

2005-07-22  Angus Leeming  leeming AT lyx.org

* QRef.C (update_contents): disable the OK button when the dialog is
first shown. The user must first select a reference.

* QRefDialog.C (changed_adaptor): only enable the OK button when
the Label: field is not empty.
(refHighlighted): set the text in the Label: field only when
an item is currently selected in the Available refs browser. (When
th signal connected to this slot is triggered.)

* QBibtexDialogBase.ui:
* QCharacterDialogBase.ui:
* QERTDialogBase.ui:
* QNoteDialogBase.ui: remove the Alt-C shortcut from the Close button.

* QAskForTextDialog.ui:
* QBibtexDialogBase.ui:
* QBranchDialogBase.ui:
* QERTDialogBase.ui:
* QGraphicsDialogBase.ui:
* QIndexDialogBase.ui:
* QNoteDialogBase.ui:
* QSendtoDialogBase.ui: connect the Alt-O shortcut to the OK button.

* QBibtexDialogBase.ui: change the shortcut to the Content field.
* QERTDialogBase.ui:  change the shortcut to the Open field.
* QGraphicsDialogBase.ui: change the shortcut to the Origin field.
* QNoteDialogBase.ui: change the shortcut to the Comment field.
* QParagraphDialogBase.ui:  change the shortcut to the Longest label
field.
* QPrefConvertersModule.ui: change the shortcut to the From field.
* QPrefLanguageModule.ui: change the shortcut to the Use babel field.
* QPrefUIModule.ui: change the shortcut to the Cursor follows
scrollbar field.
* QRefDialogBase.ui: change the shortcut to the Labels in: field.

-- 
Angus

Re: Bugs status

[Bennett Helm]

On Jan 5, 2006, at 4:51 AM, Jean-Marc Lasgouttes wrote:


Did I ask you to try to compile with --disable-optimization
already?


Bennett No, but it doesn't help:

So, just to make sure, you did a make clean and recompiled, didn't
you?


Yes.

Bennett

Re: Linking failure on Mac

[Jean-Marc Lasgouttes]

 Bennett == Bennett Helm [EMAIL PROTECTED] writes:

Bennett I'm not understanding here.

Bennett 1.4.0pre3 works fine (and I did run autogen.sh); it's
Bennett 1.4.0cvs that gives me the trouble. (And I did not manually
Bennett run autogen.sh on it recently.)

Bennett Reverting ltmain.sh to the version before 30-Dec-2005 enables
Bennett me to configure and make without problems. Reverting
Bennett ltmain.sh back to the current version, reconfiguring, and
Bennett making (without running autogen.sh) now works as well.

So you mean that it works?

JMarc

Re: Linking failure on Mac

[Bennett Helm]

On Jan 5, 2006, at 11:57 AM, Jean-Marc Lasgouttes wrote:


Bennett == Bennett Helm [EMAIL PROTECTED] writes:


Bennett I'm not understanding here.

Bennett 1.4.0pre3 works fine (and I did run autogen.sh); it's
Bennett 1.4.0cvs that gives me the trouble. (And I did not manually
Bennett run autogen.sh on it recently.)

Bennett Reverting ltmain.sh to the version before 30-Dec-2005 enables
Bennett me to configure and make without problems. Reverting
Bennett ltmain.sh back to the current version, reconfiguring, and
Bennett making (without running autogen.sh) now works as well.

So you mean that it works?


Yes ... for now. It's all voodoo and magic incantations to me.

Bennett

Re: Linking failure on Mac

[Bennett Helm]

On Jan 5, 2006, at 12:09 PM, Bennett Helm wrote:


On Jan 5, 2006, at 11:57 AM, Jean-Marc Lasgouttes wrote:


Bennett == Bennett Helm [EMAIL PROTECTED] writes:


Bennett I'm not understanding here.

Bennett 1.4.0pre3 works fine (and I did run autogen.sh); it's
Bennett 1.4.0cvs that gives me the trouble. (And I did not manually
Bennett run autogen.sh on it recently.)

Bennett Reverting ltmain.sh to the version before 30-Dec-2005  
enables

Bennett me to configure and make without problems. Reverting
Bennett ltmain.sh back to the current version, reconfiguring, and
Bennett making (without running autogen.sh) now works as well.

So you mean that it works?


Yes ... for now. It's all voodoo and magic incantations to me.


... But no longer. (I'm not sure what explains why I was able to get  
it to seem to work once; maybe it was just apparent and not real.) To  
be more explicit, here's what I've now done:


cvs up -D 29-Dec-2005 config/ltmain.sh
./autogen.sh
./configure [... with my usual additions ...]
make

And that works fine. However:

touch src/lyx_main.C
cvs up -A config/ltmain.sh
./configure [...]
make

fails as before.

Bennett

Re: Mathfrak fonts broken in Windows version

[Uwe Stöhr]

Paul A. Rubin wrote:

I have LyX 1.3.6-1 installed on a few different windows machines.  The 
mathbb and mathcal fonts display properly, but mathfrak characters 
come out in the standard font.  I tried both bakoma and xft.  Any ideas?


On my systems, in the LyX window mathfrak characters display in a font 
that's different from the standard math font (looks like upright bold 
Arial, Arial being my choice for Sans Serif), but the characters appear 
as mathfrak in the DVI output.  I suspect that there is no screen 
version of mathfrak in either font package.


Mathfrak works for me (LyXWinInstaller version 0.6). I wasn't able to 
find out which font file is used by LyX to display mathfrak characters 
(LyX command line option -dbg fonts or -dbg mathed don't print the 
name.) Any idea where I can get this information?

If I know the fontname I can deliver it with the next installer version.

regards Uwe

Re: Instant preview in LyX/Win 1.4.0pre3

[Enrico Forestieri]

Enrico Forestieri [EMAIL PROTECTED] writes:
 
 Angus Leeming leeming at ... writes:
  
  Enrico Forestieri wrote:
  
   I tried dvipng 1.7 on linux and its output is exactly equal to what that
   RE matches. So it is not a problem with dvipng itself but seemingly with
   the dvipng shipped with MikTeX.
  
   Then I guess you know who to complain to.
  
  I wonder if the MikTeX version is piping its stderr stream to stdout? (For
  reasons unknown.)
 
 No, it is not like that. I can separately capture stderr and stdout.
 I tried compiling dvipng 1.7 under cygwin, which should be more
 reliable, and I am seeing a similar problem:
 
 $ dvipng ...
 This is dvipng 1.7 Copyright 2002-2005 Jan-Ake Larsson
 dvipng warning: cannot find ps2pk.map, nor psfonts.map
 [1 (preview-latex version 11.81) depth=6 height=16]
 
 The warning should not matter. It is due to the fact that I used the
 cygwin tetex-devel package (for libkpathsea) and simply did:
 
 $ ln -s /c/texmf /usr/share/texmf
 
 for using the MikTeX texmf tree, but unfortunately ps2pk.map and
 psfonts.map are not in /c/texmf:
 
 $ kpsewhich ps2pk.map
 C:/localtexmf/dvips/config/ps2pk.map
 $ kpsewhich psfonts.map
 C:/localtexmf/dvips/config/psfonts.map
 
 So, I am going to read the libkpathsea documentation for setting some
 environment variable...
 
 I'll see what it turns out to be. Having the sources, I can use ddd for
 debugging dvipng.

Ok, with the following four soft links I was able to use the cygwin
libkpathsea with MikTeX without messing with env vars:

$ ln -s /c/texmf /usr/share/texmf
$ ln -s /c/localtexmf /usr/share/texmf-local
$ ln -s /c/localtexmf/fonts /var/tmp/texfonts
$ ln -s /c/localtexmf/dvips/config /c/texmf/dvips/config-local

Now to the problem with dvipng. It is related to the version of the
preview-latex package used to produce the dvi file. Indeed, I can
reproduce it in linux when using a dvi file generated by MikTeX,
which uses a more recent version of preview-latex, and conversely,
the problem does not show up when using dvipng on Windows with a
debian testing tetex generated dvi file, which has a previous
version of preview-latex:

$ diff -u preview.sty.tetex preview.sty.miktex
...
@@ -83,6 +85,7 @@
 \DeclareOption{dvips}{%
   [EMAIL PROTECTED]@ne
   [EMAIL PROTECTED]
+  \special{!/[EMAIL PROTECTED]([EMAIL PROTECTED])def}
   \special{!userdict begin/preview-bop-level 0 def%
   /bop-hook{/preview-bop-level dup load dup 0 le{/isls false def%
   /vsize 792 def/hsize 612 def}if 1 add store}bind def%
...


The culprit is the following code from the dvipng special.c source file:

  if (strncmp(buffer,!/[EMAIL PROTECTED](,18)==0) {
buffer+=18;
length-=18;
while (length0  buffer[length]!=')')
  length--;
if (page_imagep==NULL)
  Message(BE_NONQUIET, (preview-latex version %.*s),length,buffer);
return;
  }

  /* preview-latex' tightpage option */
  if (strncmp(buffer,!/[EMAIL PROTECTED],19)==0) {
buffer+=19;
SKIPSPACES(buffer);
if (strncmp(buffer,true,4)==0) {
  if (page_imagep==NULL)
Message(BE_NONQUIET, (preview-latex tightpage option detected, \
will use its bounding box));
  flags |= PREVIEW_LATEX_TIGHTPAGE;
  return;
}
  }
  if (strncmp(buffer,!userdict,9)==0
   strstr(buffer+10,7{currentfile token not{stop}if 65781.76 div)!=NULL)
 {
if (page_imagep==NULL  ~flags  PREVIEW_LATEX_TIGHTPAGE)
  Message(BE_NONQUIET, (preview-latex = 0.9.1 tightpage option detected,\
 will use its bounding box));
flags |= PREVIEW_LATEX_TIGHTPAGE;
return;
  }

and I solved it by replacing BE_NONQUIET with BE_VERBOSE in the
previous code. When the dvi file is generated by tetex the outer if
in the first block is never triggered due to the missing special in
preview.sty

This code is executed several times, but at a certain point page_imap
gets initialized and then nothing is sent to stdout anymore.

Angus, in a previous post you said that they're messing up the output
that they devised for us and indeed this seems to be the case.
However, I don't know what our agreement was, so I would be grateful
if you could report to them the story...

Then, still there is the problem that if a font is missing, the output
of the programs that are in charge to generate it is mixed to the
stdout of dvipng, thus confusing lyxpreview2bitmap.py. I think that
they should be launched redirecting their stdout to stderr.

--
Enrico

Re: Instant preview in LyX/Win 1.4.0pre3

[Angus Leeming]

Enrico Forestieri wrote:
[ snip the results of some impressive detective work ]

 Angus, in a previous post you said that they're messing up the output
 that they devised for us and indeed this seems to be the case.
 However, I don't know what our agreement was, so I would be grateful
 if you could report to them the story...

Our agreement was simply that David Kastrup and, to a lesser extent,
Jan-Åke Larsson created all the hooks needed by LyX in preview.sty and in
dvipng. They'll certainly remember, albeit hazily. I was a PITA (that's
their arses) for a couple of months ;-)

I'm afraid I'm extremely busy tying up lose ends ATM before I start a new
job on Monday. Please contact them on the AucTeX mailing list; you'll tell
the story so much better than I could ;-)

 Then, still there is the problem that if a font is missing, the output
 of the programs that are in charge to generate it is mixed to the
 stdout of dvipng, thus confusing lyxpreview2bitmap.py. I think that
 they should be launched redirecting their stdout to stderr.

Sounds reasonable. Get them to do so and then add a test to
lyxpreview2bitmap.py for dvipng version = 1.8 (as it perhaps will be) and
you're done.

Welcome to the LyX developer team ;-)
-- 
Angus

LyX web site proposal

[Martin Vermeer]

Looking at the LyX web site (thinking of upcoming release) I notice that
the LyX licence isn't mentioned other than open source. Shouldn't
there be a front page link to the licence info?

Then, it says a slightly modified GPL which in my understanding no
longer applies.

Contributers - Contributors

I used to like the text on the front page -- LyX is what?! -- but now
looking at it again, I am struck by the technical nature of the text.
LyX is described as the sum of its nuts and bolts as much as by its
capabilities. I think capabilities, the problems it was designed to
solve, should come here, and the nuts and bolts only later. 

Remember, this is the place where we sell -- or fail to sell -- LyX.
People buy solutions, not code or gadgets.

(I've been reading Karl Fogel's Producing Open Source Software. :)

What about


LyX is an advanced open source (GPL v.2, link) document processor
that encourages an approach to writing based on the structure of your
documents, not their appearance. 

LyX was written for people that write and want their writing to look
great, out of the box. No more endless tinkering with formatting
details, 'finger painting' font attributes or futzing around with page
boundaries. You just write. In the background, LyX's legendary LaTeX
typesetting engine makes _you_ look good.

LyX is stable and fully featured. It is a multi-platform, fully
internationalized application running natively on Unix/Linux and the
Macintosh and modern Windows platforms. 

And later on:

On screen, LyX looks like any word processor; its printed output -- or
richly cross-referenced PDF, just as readily produced -- looks like
nothing else.  Gone are the days of industrially bland .docs, all
looking similarly not-quite-right, yet coming out unpredictably
different on different printer drivers. Gone are the crashes 'eating'
your dissertation the evening before going to press.

LyX was written for scientists by scientists, and it shows, in
world-class support for math and structured document creation. Such
staples of scientific authoring as reference list and index creation
come standard. But _you_ don't have to be a scientist: with LyX you
create just as easily a letter or a novel or a theatre play or film
script. A broad array of ready, well designed document layouts and style
modification and feature support packages are built in.


Is this an idea?

- Martin
 


pgpPEt5GhL7iB.pgp
Description: PGP signature

Re: LyX web site proposal

[Angus Leeming]

Martin Vermeer wrote:
 What about

[ snip some hard sell :-P ]

 Is this an idea?

It's a great idea. Check out the www-user repository, get yourself karma
and go for it.

-- 
Angus

Re: Mathfrak fonts broken in Windows version

[Drop Box]

I managed to fix it myself after a little detective work...
I grepped the source code for cmsy10, which provides mathcal, and found 
qfont_loader.C.  In here, one sees that the missing font is called eufm10:

{ LyXFont::MSB_FAMILY,
msbm10,
-*-msbm10-*-*-*-*-*-*-*-*-*-*-*-* },

{ LyXFont::EUFRAK_FAMILY,
eufm10,
-*-eufm10-medium-*-*-*-*-*-*-*-*-*-*-* },

{ LyXFont::WASY_FAMILY,
wasy10,
-*-wasy10-medium-*-*-*-*-*-*-*-*-*-*-* }

The common name for this font is Euclid Fraktur.
I found it at
http://cardiome.ucsd.edu/mathtype/Mathtype4TTFonts/
under the filename eufrak.ttf.

In order to get LyX to recognize it, we must change the TrueType name, which 
is different from the filename.  I managed to do this using a script called 
ttfname from

http://scripts.sil.org/cms/scripts/page.php?site_id=nrsiitem_id=FontUtils#801ab246
by using the following command:
ttfname -n eufm10 eufrak.ttf eufm10.ttf

Now just install eufm10.ttf, restart LyX, and you should be up and fraking.  
:)  Of course it would be delightful if Uwe managed to add this font with 
the next installer.


-Bob

Re: Mathfrak fonts broken in Windows version

[Uwe Stöhr]

dropbox wrote:

I have LyX 1.3.6-1 installed on a few different windows machines.  The 
mathbb and mathcal fonts display properly, but mathfrak characters 
come out in the standard font.  I tried both bakoma and xft.  Any ideas?


I found the problem: The file eufm10.ttf is missing in the current 
version of the BaKoMa4LyX-package.
I attached the file, so that you can install it manually (you need to 
reconfigure LyX after this).


The next installer version will fix this. I also uploade a new version 
of BaKoMa4LyX.


regards Uwe


eufm10.ttf
Description: Binary data

[patch] updated BaKoMa4LyX package

[Uwe Stöhr]

Hello JMarc,

I uploaded a new version of the BaKoMa4LyX Windows font package to

ftp://ftp.devel.lyx.org/pub/incoming/

Could you please move it to

ftp://ftp.lyx.org/pub/lyx/contrib/

I missed the file eufm10.ttf so that fraktur characters couldn't be 
displayed in mathed.


thanks and regards
Uwe

Re: Instant preview in LyX/Win 1.4.0pre3

[Enrico Forestieri]

Angus Leeming [EMAIL PROTECTED] writes:

 Our agreement was simply that David Kastrup and, to a lesser extent,
 Jan-Åke Larsson created all the hooks needed by LyX in preview.sty and in
 dvipng. They'll certainly remember, albeit hazily. I was a PITA (that's
 their arses) for a couple of months 

I don't think so. You are listed in the credits section of the dvipng docs ;-)

 I'm afraid I'm extremely busy tying up lose ends ATM before I start a new
 job on Monday. Please contact them on the AucTeX mailing list; you'll tell
 the story so much better than I could 

Ok, then. Good luck to you with your new job!

  Then, still there is the problem that if a font is missing, the output
  of the programs that are in charge to generate it is mixed to the
  stdout of dvipng, thus confusing lyxpreview2bitmap.py. I think that
  they should be launched redirecting their stdout to stderr.
 
 Sounds reasonable. Get them to do so and then add a test to
 lyxpreview2bitmap.py for dvipng version = 1.8 (as it perhaps will be) and
 you're done.
 
 Welcome to the LyX developer team 

Wow! I got promoted on the field! ;-)
Then I am sorry that my Christmas holidays are at the end... ;-)

--
Enrico

Re: Instant preview in LyX/Win 1.4.0pre3

[Enrico Forestieri]

Angus Leeming [EMAIL PROTECTED] writes:

 I'm afraid I'm extremely busy tying up lose ends ATM before I start a new
 job on Monday. Please contact them on the AucTeX mailing list; you'll tell
 the story so much better than I could 

Done:

http://article.gmane.org/gmane.emacs.auctex.devel/870

--
Enrico

Crash running spellcheck

[Algernon]

Hi Devs,

I'm giving minimal info because I want to report this before I forget,
as I can live with things as they are.

I did a google search on the web - couldn't find errors sufficiently
similar (and I'm not a 'C' programmer).

Just installed LyX 1.4.0pre3.  My first install, but I'll give a pre3 a shot.

After creating a new *short* (two lines) document, with one spelling
error and running spellcheck, LyX *may* crash (not always) with:

--
ControlSpellchecker::replace(description)
Assertion triggered in T* boost::scoped_ptr::operator->() const
[with T = SpellBase] by failing check "ptr != 0" in file
../../../boost/boost/scoped_ptr.hpp:94
LyX: Attempting to save document /home/mtlski/newfile1.lyx
  /home/mtlski/newfile1.lyx.emergency
  Save seems successful. Phew.
Aborted
--

I believe it is the same error every time, regardless of the word
misspelled.  Sometimes there is no error, but no suggested word list
either (although then a misspelled word will still be highlighted).

The suggested word list box when it appears always appears without a
window decoration.  Selecting on a word causes the crash.

Window manager is sWM.

I'll report more later as I play with this if a pre4 doesn't come out first.

- bernard

Re: Bugs status

[Jean-Marc Lasgouttes]

> "Bo" == Bo Peng <[EMAIL PROTECTED]> writes:

>> > Also, if you keep the extension to ".lyx", you are going to
>> overwrite > the file. What about exporting to ".lyx13"?
>> 
>> Fine with me.

Bo> But a more common approach is that the user is prompted for a new
Bo> filename.

Yes, but this is more work :)

JMarc

Re: [Patch] (Re: Screen update improvements)

[Jean-Marc Lasgouttes]

> "Michael" == Michael Gerz <[EMAIL PROTECTED]> writes:

Michael> I think we have to speed up selections and reduce flickering
Michael> for 1.4.0. Right now, it is not a great joy to select text if
Michael> the LyX windows covers the full screen.

Could you test the small patch posted by Abdel? I am curious to see
whether it helps on qt/win 3.

JMarc

beamer layout

[Jose' Matos]

Hi,
is there any reason why we are not shipping the beamer layout?

I know that the beamer carries the layout there but it is not 
automatically 
installed. If we carried such file it would work as soon as lyx detected the 
presence of beamer.

Someone asked for it in fedora devel list and I proposed to add the 
beamer 
layout to the lyx package there since in fedora beamer is packaged with 
tetex.

Best regards,
-- 
José Abílio

Re: beamer layout

[Uwe Stöhr]

Jose' Matos wrote:


is there any reason why we are not shipping the beamer layout?


I asked for this some time ago and Georg argumented that it is a special 
package for its own on some Linux systems that could cause problems. 
Georg is this still the case?


regards Uwe

p.s. I currently ship beamer.layout with my installer.

Re: beamer layout

[Jean-Marc Lasgouttes]

> "Jose'" == Jose' Matos <[EMAIL PROTECTED]> writes:

Jose'> Hi, is there any reason why we are not shipping the beamer
Jose'> layout?

It would be reasonable. I guess you should ask the beamer author what
he prefers.

JMarc

Re: Screen update improvements

[Jean-Marc Lasgouttes]

> "Abdel" == Abdel  <[EMAIL PROTECTED]> writes:

Abdel> I guess so yes. Following patch will do so.

Do you see some improvement with the patch? I guess only qt3 could
benefit.

JMarc

Re: Linking failure on Mac

[Jean-Marc Lasgouttes]

> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:

Bennett> Most recent cvs fails to link on Mac with gcc-3.3. Any hints?

Did you run autogen.sh over your 1.4.0pre3 distribution? What happens
of you don't? Nowadays, autogen replaces the automake/libtool files in
config/ and it may be that you replaced working files with non-working
ones...

JMarc

Re: How to speed up LyXText::breakParagraph?

[Jean-Marc Lasgouttes]

> "Abdel" == Abdel  <[EMAIL PROTECTED]> writes:

Abdel> Oups I just notice a Cut problem. The prototype I am
Abdel> proposing is as follow, sorry about that. Optionnally, insert
Abdel> could return a reference or a pointer to the newly inserted
Abdel> paragraph but I think that the get(size_t) function is cleaner.

I guess Lars won't like it because ParagraphList is not a good stl
container anymore... I guess what we are looking after is some
templatized container, and I am actually surprised that it does not
exists already.

BTW, don't you define ParagraphList::Iter twice?

JMarc

Re: How to speed up LyXText::breakParagraph?

[Jean-Marc Lasgouttes]

> "Abdel" == Abdel  <[EMAIL PROTECTED]> writes:

Abdel> I have compiled this file with -O3 but the slowness is still
Abdel> there. Indeed insertion inside a vector is known to be
Abdel> inefficient. I have read the history about ParagraphList_fwd.h
Abdel> 
(http://www.lyx.org/cgi-bin/viewcvs.cgi/lyx-devel/src/ParagraphList_fwd.h)
Abdel> and I guess there might be some valid reason to choose a vector
Abdel> instead of a list but performance wise, it shows, definitely. 

You may want also to read this thread about all the problems that
vector creates. I really think we shall get rid of it somehow, but it
should be in a transparent manner. I guess what we need is a vector of
pointers that emulates the vector<> behaviour.

JMarc

Re: beamer layout

[Uwe Stöhr]

Jean-Marc Lasgouttes wrote:


It would be reasonable. I guess you should ask the beamer author what
he prefers.


Some time ago I asked him if we could ship it directly with LyX and he 
allowed it (beamer is also under the GPL).


regards Uwe

Re: Bugs status

[Jean-Marc Lasgouttes]

> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:

>>  Note that you can compile it, but it does not run ;)

Bennett> Thbpbpthpt!

I did try to do something after all!

>> Did I ask you to try to compile with --disable-optimization
>> already?

Bennett> No, but it doesn't help:

So, just to make sure, you did a "make clean" and recompiled, didn't
you? 

JMarc

New Chktex.C patch.

[John C. McCabe-Dansted]

I have been playing with Chktex.C, and have made a patch against
lyx1.4.0pre3/Chktex.C which:
 - Drops the -v0 flag and uses the less cryptic default (-v1) ChkTeX format.
 - Uses error titles more informative than 'Chktex warning # n'.
 - Fixes the bug where filenames containing ':' do not parse correctly.
 - Removes the USE_BOOST_FORMAT #ifdef, and always uses the std C++ code which 
is simpler anyway.

I understand that due to the feature freeze this code is unlikely to included 
before 1.4.1.

-- 
John C. McCabe-Dansted
Masters Student


Chktex.C.patch.gz
Description: GNU Zip compressed data

Re: New Chktex.C patch.

[Jean-Marc Lasgouttes]

> "John" == John C McCabe-Dansted <[EMAIL PROTECTED]> writes:

John> I have been playing with Chktex.C, and have made a patch against
John> lyx1.4.0pre3/Chktex.C which: 

Could you provide a unified diff (diff -u)? It is easier to read.

John> - Drops the -v0 flag and uses the less cryptic default (-v1)
John> ChkTeX format. 

Would it be possible to use -v3 (lacheck), so that LyX can also use
lacheck for checking? I do not know which format is the best actually.

John> - Uses error titles more informative than 'Chktex warning # n'.
John> - Fixes the bug where filenames containing ':' do not parse
John> correctly. - Removes the USE_BOOST_FORMAT #ifdef, and always
John> uses the std C++ code which is simpler anyway.

I'll have to see the unified patch.

John> I understand that due to the feature freeze this code is
John> unlikely to included before 1.4.1.

Indeed. And for nontrivial features like that, expect 1.4.2 or later
(even 1.5 if there is a risk).

JMarc

Re: How to speed up LyXText::breakParagraph?

[Lars Gullik Bjønnes]

Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:

| > "Abdel" == Abdel  <[EMAIL PROTECTED]> writes:
| 
| Abdel> Oups I just notice a Cut problem. The prototype I am
| Abdel> proposing is as follow, sorry about that. Optionnally, insert
| Abdel> could return a reference or a pointer to the newly inserted
| Abdel> paragraph but I think that the get(size_t) function is cleaner.
| 
| I guess Lars won't like it because ParagraphList is not a good stl
| container anymore... I guess what we are looking after is some
| templatized container, and I am actually surprised that it does not
| exists already.

I don't "don't like it", it is close to a solution I already had
thought of.

BUT I am not ready even to begin thinking about it, I want 1.4.1
finished first.

-- 
Lgb

Re: How to speed up LyXText::breakParagraph?

[Jean-Marc Lasgouttes]

> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:

Lars> I don't "don't like it", it is close to a solution I already had
Lars> thought of.

Good.

Lars> BUT I am not ready even to begin thinking about it, I want 1.4.1
Lars> finished first.

I could not agree more :)

JMarc

Re: How to speed up LyXText::breakParagraph?

[Lars Gullik Bjønnes]

Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:

| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
| 
| Lars> I don't "don't like it", it is close to a solution I already had
| Lars> thought of.
| 
| Good.
| 
| Lars> BUT I am not ready even to begin thinking about it, I want 1.4.1
| Lars> finished first.
| 
| I could not agree more :)

except that I meant 1.4.0 of course...

-- 
Lgb

Re: How to speed up LyXText::breakParagraph?

[Jean-Marc Lasgouttes]

> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:

| I could not agree more :)

Lars> except that I meant 1.4.0 of course...

Damn!

JMarc

Re: Screen update improvements

[Abdel]

Jean-Marc Lasgouttes a écrit :

"Abdel" == Abdel  <[EMAIL PROTECTED]> writes:


Abdel> I guess so yes. Following patch will do so.

Do you see some improvement with the patch? I guess only qt3 could
benefit.


Right now, I cannot compile with qt3, sorry. With my Qt4 port, there is 
no flicker but I have tested this nonetheless with a different syntax:


viewport()->setAttribute(Qt::WA_OpaquePaintEvent);

The result is not good: all the "float buttons" (foot, figure, table, 
etc) are black on black. The weird thing is that this behavior affects 
also my previously compiled Qt3 version. I presume that floats are not 
"painted" by the lyx core but use the background color instead, aren't 
they? Apparently setting this attribute is propagated system wide by Qt4.


Abdel.




JMarc

Re: How to speed up LyXText::breakParagraph?

[Abdel]

Jean-Marc Lasgouttes a écrit :

"Abdel" == Abdel  <[EMAIL PROTECTED]> writes:


Abdel> Oups I just notice a Cut problem. The prototype I am
Abdel> proposing is as follow, sorry about that. Optionnally, insert
Abdel> could return a reference or a pointer to the newly inserted
Abdel> paragraph but I think that the get(size_t) function is cleaner.

I guess Lars won't like it because ParagraphList is not a good stl
container anymore... I guess what we are looking after is some
templatized container, and I am actually surprised that it does not
exists already.


Well, if the class provide "insert", "erase" and "find", isn't that enought?
I think it is even possible to derive ParagraphList from 
vector if we need the container interface. I 
can write a new proposal if you want.



BTW, don't you define ParagraphList::Iter twice?


Typo, sorry. I haven't tested this, I wrote the class within the email.



JMarc

[PATCH] Fix bibliography layout for CV textclass.

[Jean-Marc Lasgouttes]

The following change was probably forgotten by whoever introduced the
Bib_Environment tag.

Georg, is this something layout2layout c/should do?

I'll commit it, since it is trivial and fixes a regression (latex
output was "\item \bibitem{foo}").

JMarc

Index: lib/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/ChangeLog,v
retrieving revision 1.752
diff -u -p -r1.752 ChangeLog
--- lib/ChangeLog	2 Jan 2006 19:15:25 -	1.752
+++ lib/ChangeLog	5 Jan 2006 11:48:20 -
@@ -1,3 +1,8 @@
+2006-01-05  Jean-Marc Lasgouttes  <[EMAIL PROTECTED]>
+
+	* layouts/cv.layout (Bibliography): change latextype to
+	Bib_Environment.
+
 2006-01-02  Michael Gerz  <[EMAIL PROTECTED]>
 
 	* layouts/amsart-seq.layout: fix typo in counter
Index: lib/layouts/cv.layout
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/layouts/cv.layout,v
retrieving revision 1.14
diff -u -p -r1.14 cv.layout
--- lib/layouts/cv.layout	21 Oct 2005 16:11:33 -	1.14
+++ lib/layouts/cv.layout	5 Jan 2006 11:48:20 -
@@ -143,6 +143,7 @@ End
 Style Bibliography
 	CopyStyle Topic
 	LatexName thebibliography
+	LatexType Bib_Environment
 	LabelType Bibliography
 	LabelString   ""
 	LabelBottomSep0.7

Bug reading layout files (layout2layout?)

[Juergen Spitzmueller]

LyX 1.4 seems to have major problems reading layout files containing capital 
letters. The attached layout file is just a copy of article.layout, renamed  
articleX.layout. If you try to switch to that layout, LyX is entering a long 
busy stage before it eventually returns the message "Could not convert 
document class to articleX".

The console messages read: 

RunCommand:: could not start child process
Could not run layout conversion script layout2layout.py.
Error reading `~/.lyx-cvs/layouts/articleX.layout'
(Check `articleX')
Check your installation and try Options/Reconfigure...
RunCommand:: could not start child process
Could not run layout conversion script layout2layout.py.
Error reading `~/.lyx-cvs/layouts/articleX.layout'
(Check `articleX')
Check your installation and try Options/Reconfigure...
RunCommand:: could not start child process
Could not run layout conversion script layout2layout.py.
Error reading `~/.lyx-cvs/layouts/articleX.layout'
(Check `articleX')
Check your installation and try Options/Reconfigure...
RunCommand:: could not start child process
Could not run layout conversion script layout2layout.py.
Error reading `~/.lyx-cvs/layouts/articleX.layout'
(Check `articleX')
Check your installation and try Options/Reconfigure...

If you change the name to articlex.layout, everything is fine.

Jürgen
#% Do not delete the line below; configure depends on this
#  \DeclareLaTeXClass[article]{articleX}
# Article textclass definition file. Taken from initial LyX source code
# Author : Matthias Ettrich <[EMAIL PROTECTED]>
# Transposed by Pascal André <[EMAIL PROTECTED]>
# Heavily modifed and enhanced by serveral developers.

Format 2
Input stdclass.inc
Input numarticle.inc

SecNumDepth 3
TocDepth3

NoStyle Chapter
NoStyle Chapter*


Style Part
Align Left
AlignPossible Left
TopSep2
BottomSep 1.5
Font
  SizeLarger
EndFont
End


Style Part*
Align Left
AlignPossible Left
TopSep2
BottomSep 1.5
Font
  SizeLarger
EndFont
End

Re: Bug reading layout files (layout2layout?)

[Jose' Matos]

On Thursday 05 January 2006 11:53, Juergen Spitzmueller wrote:
> LyX 1.4 seems to have major problems reading layout files containing
> capital letters. The attached layout file is just a copy of article.layout,
> renamed articleX.layout. If you try to switch to that layout, LyX is
> entering a long busy stage before it eventually returns the message "Could
> not convert document class to articleX".

Although not completely related I am writing a set of python parsers for 
layout files. The purpose is to use those lessons to simply their grammar for 
1.5 while at same allow the creation of tools to ease their creation.

It is really amazing the complexity of layout files now, article has more than 
300 lines (without blanks and comments)!

> Jürgen

-- 
José Abílio

Re: Instant preview in LyX/Win 1.4.0pre3

[Angus Leeming]

Enrico Forestieri wrote:

> Angus Leeming <[EMAIL PROTECTED]> writes:
> 
>> Oh, that's horrid and the one that follows is worse.
>> What I think you should do is talk to David Kastrup and Jan-Åke Larsson
>> on the AucTeX mailing list (gmane.emacs.auc-tex) and see why they're
>> messing up the output that they devised for us.
> 
> I tried dvipng 1.7 on linux and its output is exactly equal to what that
> RE matches. So it is not a problem with dvipng itself but seemingly with
> the dvipng shipped with MikTeX.

;-) Then I guess you know who to complain to.

I wonder if the MikTeX version is piping its stderr stream to stdout? (For
reasons unknown.)

-- 
Angus

[PATCH 13x, 14x] squash bug 2193

[Angus Leeming]

The attached patches fix bug 2193, just reported, but raised originally by
Uwe on 7 December. See thread
http://thread.gmane.org/gmane.editors.lyx.devel/50473

(instant preview fails if the path to the ghostscript executable contains
spaces.)

I guess the fix fell below the radar screen...

Anyway, the patch is obvious and works for me, so I'll just commit it.

-- 
AngusIndex: status.13x
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/Attic/status.13x,v
retrieving revision 1.1.2.282
diff -u -p -r1.1.2.282 status.13x
--- status.13x	12 Dec 2005 10:08:37 -	1.1.2.282
+++ status.13x	5 Jan 2006 14:02:13 -
@@ -69,6 +69,9 @@ What's new
 - On exit, don't attempt to unlock a mutex in the Qt library --- it
   causes undefined behaviour and leads to a crash on NetBSD.
 
+- Enable Instant Preview to work if the path to the external GhostScript
+  executable contains spaces. (bug 2193).
+
 * Configuration/Installation:
 
 - Enable TeXFiles.sh to run when its path contains spaces.
Index: lib/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/ChangeLog,v
retrieving revision 1.363.2.134
diff -u -p -r1.363.2.134 ChangeLog
--- lib/ChangeLog	19 Dec 2005 11:08:08 -	1.363.2.134
+++ lib/ChangeLog	5 Jan 2006 14:02:16 -
@@ -1,3 +1,9 @@
+2006-01-05  Angus Leeming  <[EMAIL PROTECTED]>
+
+	* scripts/lyxpreview2ppm.py (find_exe): return only the basename of
+	the executable to avoid problems when the path to the exe contains
+	spaces. Fixes bug 2193.
+
 2005-12-16  Georg Baum  <[EMAIL PROTECTED]>
 
 	* symbols: avoid use of symbol font if cmsy is available.
Index: lib/scripts/lyxpreview2ppm.py
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/scripts/Attic/lyxpreview2ppm.py,v
retrieving revision 1.1.2.7
diff -u -p -r1.1.2.7 lyxpreview2ppm.py
--- lib/scripts/lyxpreview2ppm.py	16 Jun 2005 13:15:11 -	1.1.2.7
+++ lib/scripts/lyxpreview2ppm.py	5 Jan 2006 14:02:17 -
@@ -93,7 +93,11 @@ def find_exe(candidates, path):
 full_path = os.path.join(directory, prog)
 
 if os.access(full_path, os.X_OK):
-return full_path
+# The thing is in the PATH already (or we wouldn't
+# have found it). Return just the basename to avoid
+# problems when the path to the executable contains
+# spaces.
+return os.path.basename(full_path)
 
 return None
 
Index: lib/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/ChangeLog,v
retrieving revision 1.752
diff -u -p -r1.752 ChangeLog
--- lib/ChangeLog	2 Jan 2006 19:15:25 -	1.752
+++ lib/ChangeLog	5 Jan 2006 14:04:44 -
@@ -1,3 +1,9 @@
+2006-01-05  Angus Leeming  <[EMAIL PROTECTED]>
+
+	* scripts/lyxpreview_tools.py (find_exe): return only the basename of
+	the executable to avoid problems when the path to the exe contains
+	spaces. Fixes bug 2193.
+
 2006-01-02  Michael Gerz  <[EMAIL PROTECTED]>
 
 	* layouts/amsart-seq.layout: fix typo in counter
Index: lib/scripts/lyxpreview_tools.py
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/scripts/lyxpreview_tools.py,v
retrieving revision 1.1
diff -u -p -r1.1 lyxpreview_tools.py
--- lib/scripts/lyxpreview_tools.py	9 Aug 2004 11:31:18 -	1.1
+++ lib/scripts/lyxpreview_tools.py	5 Jan 2006 14:04:44 -
@@ -52,7 +52,11 @@ def find_exe(candidates, path):
 full_path = os.path.join(directory, prog)
 
 if os.access(full_path, os.X_OK):
-return full_path
+# The thing is in the PATH already (or we wouldn't
+# have found it). Return just the basename to avoid
+# problems when the path to the executable contains
+# spaces.
+return os.path.basename(full_path)
 
 return None
 

Re: [PATCH 13x, 14x] squash bug 2193

[Jean-Marc Lasgouttes]

> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:

Angus> The attached patches fix bug 2193, just reported, but raised
Angus> originally by Uwe on 7 December. See thread
Angus> http://thread.gmane.org/gmane.editors.lyx.devel/50473

Angus> (instant preview fails if the path to the ghostscript
Angus> executable contains spaces.)

Angus> I guess the fix fell below the radar screen...

Angus> Anyway, the patch is obvious and works for me, so I'll just
Angus> commit it.

Looks OK.

JMarc

Re: Crash running spellcheck

[Jean-Marc Lasgouttes]

> "Algernon" == Algernon  <[EMAIL PROTECTED]> writes:

Algernon> I'll report more later as I play with this if a pre4 doesn't
Algernon> come out first.

It would be nice if you could tell us what spellchecker is in used
(output of "lyx -version" would be fine) and give a precise recipe for
the crash.

JMarc

Re: Instant preview in LyX/Win 1.4.0pre3

[Enrico Forestieri]

Angus Leeming <[EMAIL PROTECTED]> writes:
> 
> Enrico Forestieri wrote:
> 
> > I tried dvipng 1.7 on linux and its output is exactly equal to what that
> > RE matches. So it is not a problem with dvipng itself but seemingly with
> > the dvipng shipped with MikTeX.
> 
>  Then I guess you know who to complain to.
> 
> I wonder if the MikTeX version is piping its stderr stream to stdout? (For
> reasons unknown.)

No, it is not like that. I can separately capture stderr and stdout.
I tried compiling dvipng 1.7 under cygwin, which should be more
reliable, and I am seeing a similar problem:

$ dvipng ...
This is dvipng 1.7 Copyright 2002-2005 Jan-Ake Larsson
dvipng warning: cannot find ps2pk.map, nor psfonts.map
[1 (preview-latex version 11.81) depth=6 height=16]

The warning should not matter. It is due to the fact that I used the
cygwin tetex-devel package (for libkpathsea) and simply did:

$ ln -s /c/texmf /usr/share/texmf

for using the MikTeX texmf tree, but unfortunately ps2pk.map and
psfonts.map are not in /c/texmf:

$ kpsewhich ps2pk.map
C:/localtexmf/dvips/config/ps2pk.map
$ kpsewhich psfonts.map
C:/localtexmf/dvips/config/psfonts.map

So, I am going to read the libkpathsea documentation for setting some
environment variable...

I'll see what it turns out to be. Having the sources, I can use ddd for
debugging dvipng.

--
Enrico

[Patch] speed patch revisited

[Martin Vermeer]

Please find attach the inside-inset speed patch, which now functions and
is as bug-free as I could get it.

There are still some rendering artefacts in corner cases, but none of
them look bad IMHO.

This is a somewhat complex and intrusive patch, and perhaps not for
1.4.0. But for 1.4.1 we should consider this -- together with the
inside-paragraph selection speed patch. I feel good about both.

Note that the patch was diffed from a dirty tree. It contains a
stowaway, the bool multiparsel_cache_ from the selection speed patch,
which should not cause trouble here.

- Martin

Index: BufferView.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/BufferView.C,v
retrieving revision 1.265
diff -u -p -r1.265 BufferView.C
--- BufferView.C	19 Dec 2005 11:47:13 -	1.265
+++ BufferView.C	5 Jan 2006 14:33:29 -
@@ -369,6 +369,18 @@ void BufferView::putSelectionAt(DocItera
 }
 
 
+bool const BufferView::repaintAll() const
+{ 
+	return pimpl_->repaintAll();
+}
+
+	
+void const BufferView::repaintAll(bool r) const
+{ 
+	pimpl_->repaintAll(r);
+}
+
+
 LCursor & BufferView::cursor()
 {
 	return pimpl_->cursor_;
Index: BufferView.h
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/BufferView.h,v
retrieving revision 1.189
diff -u -p -r1.189 BufferView.h
--- BufferView.h	1 Dec 2005 10:28:47 -	1.189
+++ BufferView.h	5 Jan 2006 14:33:29 -
@@ -198,7 +199,10 @@ public:
 	 */
 	void putSelectionAt(DocIterator const & cur,
 		int length, bool backwards);
-
+	///
+	bool const repaintAll() const;
+	///
+	void const repaintAll(bool r) const;
 
 private:
 	///
Index: BufferView_pimpl.h
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/BufferView_pimpl.h,v
retrieving revision 1.129
diff -u -p -r1.129 BufferView_pimpl.h
--- BufferView_pimpl.h	7 Nov 2005 15:06:42 -	1.129
+++ BufferView_pimpl.h	5 Jan 2006 14:33:29 -
@@ -103,6 +105,10 @@ public:
 	FuncStatus getStatus(FuncRequest const & cmd);
 	/// a function should be executed
 	bool dispatch(FuncRequest const & ev);
+	/// Flag: do a full redraw of inside text of inset
+	bool repaintAll() { return refresh_inside_; }
+	///
+	void repaintAll(bool r) {refresh_inside_ = r; }
 private:
 	/// An error list (replaces the error insets)
 	ErrorList errorlist_;
@@ -183,13 +189,17 @@ private:
 	///
 	LCursor cursor_;
 	///
+	bool multiparsel_cache_;
	///
 	lyx::pit_type anchor_ref_;
 	///
 	int offset_ref_;
 	///
 	ViewMetricsInfo metrics(bool singlepar = false);
-
-
+	/// Working variable indicating a full screen refresh
+	mutable bool refresh_;
+	/// Inside insets
+	mutable bool refresh_inside_;
+	
 };
 #endif // BUFFERVIEW_PIMPL_H
Index: rowpainter.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/rowpainter.C,v
retrieving revision 1.162
diff -u -p -r1.162 rowpainter.C
--- rowpainter.C	1 Jan 2006 23:06:23 -	1.162
+++ rowpainter.C	5 Jan 2006 14:33:30 -
@@ -164,7 +164,11 @@ void RowPainter::paintInset(pos_type con
 	pi.ltr_pos = (text_.bidi.level(pos) % 2 == 0);
 	pi.erased_ = erased_ || isDeletedText(par_, pos);
 	theCoords.insets().add(inset, int(x_), yo_);
-	inset->drawSelection(pi, int(x_), yo_);
+	InsetText const * in = static_cast(inset);
+	if (in && in->isTextInset() && !in->wide_inset_)
+		bv_.repaintAll(true);
+	if (bv_.repaintAll())
+		inset->drawSelection(pi, int(x_), yo_);
 	inset->draw(pi, int(x_), yo_);
 	x_ += inset->width();
 }
@@ -729,8 +733,9 @@ lyx::size_type calculateRowSignature(Row
 }
 
 
-bool isCursorOnRow(PainterInfo & pi, pit_type pit, RowList::const_iterator rit)
+bool CursorOnRow(PainterInfo & pi, pit_type pit, RowList::const_iterator rit)
 {
+	// Is there a cursor on this row (or inside inset on row)
 	LCursor & cur = pi.base.bv->cursor();
 	for (lyx::size_type d = 0; d < cur.depth(); d++)
 		if (cur[d].pit() == pit
@@ -741,6 +746,20 @@ bool isCursorOnRow(PainterInfo & pi, pit
 }
 
 
+bool innerCursorOnRow(PainterInfo & pi, pit_type pit, RowList::const_iterator rit)
+{
+	// Is there a cursor inside an inset on this row, and is this inset
+	// the only "character" on this row
+	LCursor & cur = pi.base.bv->cursor();
+	if (rit->pos() + 1 != rit->endpos())
+		return false;
+	for (lyx::size_type d = 0; d < cur.depth(); d++)
+		if (cur[d].pit() == pit && cur[d].pos() == rit->pos())
+			return d < cur.depth() - 1;
+	return false;
+}
+
+
 void paintPar
 	(PainterInfo & pi, LyXText const & text, pit_type pit, int x, int y,
 	 bool repaintAll)
@@ -763,14 +782,25 @@ void paintPar
 
 		// Row signature; has row changed since last paint?
 		lyx::size_type const row_sig = calculateRowSignature(*rit, par);
+		bool row_has_changed = par.rowSignature()[rowno] != row_sig;
+		
+		bool cursor_on_row = CursorOnRow(pi, pit, rit);
+		bool in_inset_alone_on_row = innerCursorOnRow(pi, pit, rit);
+
+		// If 

Re: [Patch] speed patch revisited

[Lars Gullik Bjønnes]

Martin Vermeer <[EMAIL PROTECTED]> writes:

| Please find attach the inside-inset speed patch, which now functions and
| is as bug-free as I could get it.
| 
| There are still some rendering artefacts in corner cases, but none of
| them look bad IMHO.
| 
| This is a somewhat complex and intrusive patch, and perhaps not for
| 1.4.0. But for 1.4.1 we should consider this -- together with the
| inside-paragraph selection speed patch. I feel good about both.

IMHO, not for 1.4.0 but can be considered for 1.4.1.
(just to make my position clear)

-- 
Lgb

bug 2194: Double clicking in qrefs dialog broken

[Juergen Spitzmueller]

Angus,

do you remember why you did the changes below? Disconnecting those signals 
broke double-clicking in 1.4 as well as in 1.3.7cvs.
Can I re-connect them, please?

Jürgen

[EMAIL PROTECTED] wrote:
> CVSROOT:/usr/local/lyx/cvsroot
> Module name:lyx-devel
> Repository: lyx-devel/src/frontends/qt2/ui/
> Changes by: [EMAIL PROTECTED]05/07/23 23:54:49
>
> Modified files:
> lyx-devel/src/frontends/qt2/: ChangeLog
> lyx-devel/src/frontends/qt2/ui/: QRefDialogBase.ui
>
> Log message:
> Disconnect two signals --- forward port from 1.3.x.
>
> Patches:
> http://www.lyx.org/cgi-bin/viewcvs.cgi/lyx-devel/src/frontends/qt2/ChangeLo
>g?r1=1.810=1.811
> http://www.lyx.org/cgi-bin/viewcvs.cgi/lyx-devel/src/frontends/qt2/ui/QRefD
>ialogBase.ui?r1=1.9=1.10
>
> Complete Diff:
> /usr/bin/cvs -f diff -kk -u -r 1.810 -r 1.811 src/frontends/qt2/ChangeLog
> /usr/bin/cvs -f diff -kk -u -r 1.9 -r 1.10
> src/frontends/qt2/ui/QRefDialogBase.ui

Re: Linking failure on Mac

[Bennett Helm]

On Jan 5, 2006, at 4:40 AM, Jean-Marc Lasgouttes wrote:


"Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:


Bennett> Most recent cvs fails to link on Mac with gcc-3.3. Any hints?

Did you run autogen.sh over your 1.4.0pre3 distribution? What happens
of you don't? Nowadays, autogen replaces the automake/libtool files in
config/ and it may be that you replaced working files with non-working
ones...


I'm not understanding here.

1.4.0pre3 works fine (and I did run autogen.sh); it's 1.4.0cvs that  
gives me the trouble. (And I did not manually run autogen.sh on it  
recently.)


Reverting ltmain.sh to the version before 30-Dec-2005 enables me to  
configure and make without problems. Reverting ltmain.sh back to the  
current version, reconfiguring, and making (without running  
autogen.sh) now works as well.


Bennett

Re: bug 2194: Double clicking in qrefs dialog broken

[Angus Leeming]

Juergen Spitzmueller wrote:
> do you remember why you did the changes below? Disconnecting those
> signals broke double-clicking in 1.4 as well as in 1.3.7cvs.
> Can I re-connect them, please?

Hi, Jürgen

No, I don't remember why, but the relevant entries in the ChangeLog are
below.

Angus


===
BRANCH_1_3_X
2005-07-22  Angus Leeming  <[EMAIL PROTECTED]>

* QRef.C (update_contents): disable the OK button when the dialog is
first shown. The user must first select a reference.

* QRefDialog.C (changed_adaptor): only enable the OK button when
the "Label:" field is not empty.
(refHighlighted): set the text in the "Label:" field only when
an item is currently selected in the "Available refs" browser. (When
th signal connected to this slot is triggered.)

===
Trunk:
2005-07-23  Angus Leeming  

* QRefDialogBase.ui: disconnect two refsLB signals to the
refSelected and changed_adaptor slots.

2005-07-22  Angus Leeming  

* QRef.C (update_contents): disable the OK button when the dialog is
first shown. The user must first select a reference.

* QRefDialog.C (changed_adaptor): only enable the OK button when
the "Label:" field is not empty.
(refHighlighted): set the text in the "Label:" field only when
an item is currently selected in the "Available refs" browser. (When
th signal connected to this slot is triggered.)

* QBibtexDialogBase.ui:
* QCharacterDialogBase.ui:
* QERTDialogBase.ui:
* QNoteDialogBase.ui: remove the Alt-C shortcut from the Close button.

* QAskForTextDialog.ui:
* QBibtexDialogBase.ui:
* QBranchDialogBase.ui:
* QERTDialogBase.ui:
* QGraphicsDialogBase.ui:
* QIndexDialogBase.ui:
* QNoteDialogBase.ui:
* QSendtoDialogBase.ui: connect the Alt-O shortcut to the OK button.

* QBibtexDialogBase.ui: change the shortcut to the "Content" field.
* QERTDialogBase.ui:  change the shortcut to the "Open" field.
* QGraphicsDialogBase.ui: change the shortcut to the "Origin" field.
* QNoteDialogBase.ui: change the shortcut to the "Comment" field.
* QParagraphDialogBase.ui:  change the shortcut to the "Longest label"
field.
* QPrefConvertersModule.ui: change the shortcut to the "From" field.
* QPrefLanguageModule.ui: change the shortcut to the "Use babel" field.
* QPrefUIModule.ui: change the shortcut to the "Cursor follows
scrollbar" field.
* QRefDialogBase.ui: change the shortcut to the "Labels in:" field.

-- 
Angus

Re: Bugs status

[Bennett Helm]

On Jan 5, 2006, at 4:51 AM, Jean-Marc Lasgouttes wrote:


Did I ask you to try to compile with --disable-optimization
already?


Bennett> No, but it doesn't help:

So, just to make sure, you did a "make clean" and recompiled, didn't
you?


Yes.

Bennett

Re: Linking failure on Mac

[Jean-Marc Lasgouttes]

> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:

Bennett> I'm not understanding here.

Bennett> 1.4.0pre3 works fine (and I did run autogen.sh); it's
Bennett> 1.4.0cvs that gives me the trouble. (And I did not manually
Bennett> run autogen.sh on it recently.)

Bennett> Reverting ltmain.sh to the version before 30-Dec-2005 enables
Bennett> me to configure and make without problems. Reverting
Bennett> ltmain.sh back to the current version, reconfiguring, and
Bennett> making (without running autogen.sh) now works as well.

So you mean that it works?

JMarc

Re: Linking failure on Mac

[Bennett Helm]

On Jan 5, 2006, at 11:57 AM, Jean-Marc Lasgouttes wrote:


"Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:


Bennett> I'm not understanding here.

Bennett> 1.4.0pre3 works fine (and I did run autogen.sh); it's
Bennett> 1.4.0cvs that gives me the trouble. (And I did not manually
Bennett> run autogen.sh on it recently.)

Bennett> Reverting ltmain.sh to the version before 30-Dec-2005 enables
Bennett> me to configure and make without problems. Reverting
Bennett> ltmain.sh back to the current version, reconfiguring, and
Bennett> making (without running autogen.sh) now works as well.

So you mean that it works?


Yes ... for now. It's all voodoo and magic incantations to me.

Bennett

Re: Linking failure on Mac

[Bennett Helm]

On Jan 5, 2006, at 12:09 PM, Bennett Helm wrote:


On Jan 5, 2006, at 11:57 AM, Jean-Marc Lasgouttes wrote:


"Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:


Bennett> I'm not understanding here.

Bennett> 1.4.0pre3 works fine (and I did run autogen.sh); it's
Bennett> 1.4.0cvs that gives me the trouble. (And I did not manually
Bennett> run autogen.sh on it recently.)

Bennett> Reverting ltmain.sh to the version before 30-Dec-2005  
enables

Bennett> me to configure and make without problems. Reverting
Bennett> ltmain.sh back to the current version, reconfiguring, and
Bennett> making (without running autogen.sh) now works as well.

So you mean that it works?


Yes ... for now. It's all voodoo and magic incantations to me.


... But no longer. (I'm not sure what explains why I was able to get  
it to seem to work once; maybe it was just apparent and not real.) To  
be more explicit, here's what I've now done:


cvs up -D 29-Dec-2005 config/ltmain.sh
./autogen.sh
./configure [... with my usual additions ...]
make

And that works fine. However:

touch src/lyx_main.C
cvs up -A config/ltmain.sh
./configure [...]
make

fails as before.

Bennett

Re: Mathfrak fonts broken in Windows version

[Uwe Stöhr]

Paul A. Rubin wrote:

I have LyX 1.3.6-1 installed on a few different windows machines.  The 
mathbb and mathcal fonts display properly, but mathfrak characters 
come out in the standard font.  I tried both bakoma and xft.  Any ideas?


On my systems, in the LyX window mathfrak characters display in a font 
that's different from the standard math font (looks like upright bold 
Arial, Arial being my choice for Sans Serif), but the characters appear 
as mathfrak in the DVI output.  I suspect that there is no screen 
version of mathfrak in either font package.


Mathfrak works for me (LyXWinInstaller version 0.6). I wasn't able to 
find out which font file is used by LyX to display mathfrak characters 
(LyX command line option -dbg fonts or -dbg mathed don't print the 
name.) Any idea where I can get this information?

If I know the fontname I can deliver it with the next installer version.

regards Uwe

Re: Instant preview in LyX/Win 1.4.0pre3

[Enrico Forestieri]

Enrico Forestieri <[EMAIL PROTECTED]> writes:
> 
> Angus Leeming  ...> writes:
> > 
> > Enrico Forestieri wrote:
> > 
> > > I tried dvipng 1.7 on linux and its output is exactly equal to what that
> > > RE matches. So it is not a problem with dvipng itself but seemingly with
> > > the dvipng shipped with MikTeX.
> > 
> >  Then I guess you know who to complain to.
> > 
> > I wonder if the MikTeX version is piping its stderr stream to stdout? (For
> > reasons unknown.)
> 
> No, it is not like that. I can separately capture stderr and stdout.
> I tried compiling dvipng 1.7 under cygwin, which should be more
> reliable, and I am seeing a similar problem:
> 
> $ dvipng ...
> This is dvipng 1.7 Copyright 2002-2005 Jan-Ake Larsson
> dvipng warning: cannot find ps2pk.map, nor psfonts.map
> [1 (preview-latex version 11.81) depth=6 height=16]
> 
> The warning should not matter. It is due to the fact that I used the
> cygwin tetex-devel package (for libkpathsea) and simply did:
> 
> $ ln -s /c/texmf /usr/share/texmf
> 
> for using the MikTeX texmf tree, but unfortunately ps2pk.map and
> psfonts.map are not in /c/texmf:
> 
> $ kpsewhich ps2pk.map
> C:/localtexmf/dvips/config/ps2pk.map
> $ kpsewhich psfonts.map
> C:/localtexmf/dvips/config/psfonts.map
> 
> So, I am going to read the libkpathsea documentation for setting some
> environment variable...
> 
> I'll see what it turns out to be. Having the sources, I can use ddd for
> debugging dvipng.

Ok, with the following four soft links I was able to use the cygwin
libkpathsea with MikTeX without messing with env vars:

$ ln -s /c/texmf /usr/share/texmf
$ ln -s /c/localtexmf /usr/share/texmf-local
$ ln -s /c/localtexmf/fonts /var/tmp/texfonts
$ ln -s /c/localtexmf/dvips/config /c/texmf/dvips/config-local

Now to the problem with dvipng. It is related to the version of the
preview-latex package used to produce the dvi file. Indeed, I can
reproduce it in linux when using a dvi file generated by MikTeX,
which uses a more recent version of preview-latex, and conversely,
the problem does not show up when using dvipng on Windows with a
debian testing tetex generated dvi file, which has a previous
version of preview-latex:

$ diff -u preview.sty.tetex preview.sty.miktex
...
@@ -83,6 +85,7 @@
 \DeclareOption{dvips}{%
   [EMAIL PROTECTED]@ne
   [EMAIL PROTECTED]
+  \special{!/[EMAIL PROTECTED]([EMAIL PROTECTED])def}
   \special{!userdict begin/preview-bop-level 0 def%
   /bop-hook{/preview-bop-level dup load dup 0 le{/isls false def%
   /vsize 792 def/hsize 612 def}if 1 add store}bind def%
...


The culprit is the following code from the dvipng special.c source file:

  if (strncmp(buffer,"!/[EMAIL PROTECTED](",18)==0) {
buffer+=18;
length-=18;
while (length>0 && buffer[length]!=')')
  length--;
if (page_imagep==NULL)
  Message(BE_NONQUIET," (preview-latex version %.*s)",length,buffer);
return;
  }

  /* preview-latex' tightpage option */
  if (strncmp(buffer,"!/[EMAIL PROTECTED]",19)==0) {
buffer+=19;
SKIPSPACES(buffer);
if (strncmp(buffer,"true",4)==0) {
  if (page_imagep==NULL)
Message(BE_NONQUIET," (preview-latex tightpage option detected, \
will use its bounding box)");
  flags |= PREVIEW_LATEX_TIGHTPAGE;
  return;
}
  }
  if (strncmp(buffer,"!userdict",9)==0
  && strstr(buffer+10,"7{currentfile token not{stop}if 65781.76 div")!=NULL)
 {
if (page_imagep==NULL && ~flags & PREVIEW_LATEX_TIGHTPAGE)
  Message(BE_NONQUIET," (preview-latex <= 0.9.1 tightpage option detected,\
 will use its bounding box)");
flags |= PREVIEW_LATEX_TIGHTPAGE;
return;
  }

and I solved it by replacing BE_NONQUIET with BE_VERBOSE in the
previous code. When the dvi file is generated by tetex the outer "if"
in the first block is never triggered due to the missing special in
preview.sty

This code is executed several times, but at a certain point page_imap
gets initialized and then nothing is sent to stdout anymore.

Angus, in a previous post you said that "they're messing up the output
that they devised for us" and indeed this seems to be the case.
However, I don't know what "our" agreement was, so I would be grateful
if you could report to them the story...

Then, still there is the problem that if a font is missing, the output
of the programs that are in charge to generate it is mixed to the
stdout of dvipng, thus confusing lyxpreview2bitmap.py. I think that
they should be launched redirecting their stdout to stderr.

--
Enrico

Re: Instant preview in LyX/Win 1.4.0pre3

[Angus Leeming]

Enrico Forestieri wrote:
[ snip the results of some impressive detective work ]

> Angus, in a previous post you said that "they're messing up the output
> that they devised for us" and indeed this seems to be the case.
> However, I don't know what "our" agreement was, so I would be grateful
> if you could report to them the story...

"Our" agreement was simply that David Kastrup and, to a lesser extent,
Jan-Åke Larsson created all the hooks needed by LyX in preview.sty and in
dvipng. They'll certainly remember, albeit hazily. I was a PITA (that's
"their arses") for a couple of months ;-)

I'm afraid I'm extremely busy tying up lose ends ATM before I start a new
job on Monday. Please contact them on the AucTeX mailing list; you'll tell
the story so much better than I could ;-)

> Then, still there is the problem that if a font is missing, the output
> of the programs that are in charge to generate it is mixed to the
> stdout of dvipng, thus confusing lyxpreview2bitmap.py. I think that
> they should be launched redirecting their stdout to stderr.

Sounds reasonable. Get them to do so and then add a test to
lyxpreview2bitmap.py for dvipng version >= 1.8 (as it perhaps will be) and
you're done.

Welcome to the LyX developer team ;-)
-- 
Angus

LyX web site proposal

[Martin Vermeer]

Looking at the LyX web site (thinking of upcoming release) I notice that
the LyX licence isn't mentioned other than "open source". Shouldn't
there be a front page link to the licence info?

Then, it says "a slightly modified GPL" which in my understanding no
longer applies.

Contributers -> Contributors

I used to like the text on the front page -- "LyX is what?!" -- but now
looking at it again, I am struck by the technical nature of the text.
LyX is described as the sum of its nuts and bolts as much as by its
capabilities. I think capabilities, the problems it was designed to
solve, should come here, and the nuts and bolts only later. 

Remember, this is the place where we "sell" -- or fail to sell -- LyX.
People "buy" solutions, not code or gadgets.

(I've been reading Karl Fogel's "Producing Open Source Software". :)

What about


"LyX is an advanced open source (GPL v.2, link) document processor
that encourages an approach to writing based on the structure of your
documents, not their appearance. 

"LyX was written for people that write and want their writing to look
great, out of the box. No more endless tinkering with formatting
details, 'finger painting' font attributes or futzing around with page
boundaries. You just write. In the background, LyX's legendary LaTeX
typesetting engine makes _you_ look good.

"LyX is stable and fully featured. It is a multi-platform, fully
internationalized application running natively on Unix/Linux and the
Macintosh and modern Windows platforms." 

And later on:

"On screen, LyX looks like any word processor; its printed output -- or
richly cross-referenced PDF, just as readily produced -- looks like
nothing else.  Gone are the days of industrially bland .docs, all
looking similarly not-quite-right, yet coming out unpredictably
different on different printer drivers. Gone are the crashes 'eating'
your dissertation the evening before going to press.

"LyX was written for scientists by scientists, and it shows, in
world-class support for math and structured document creation. Such
staples of scientific authoring as reference list and index creation
come standard. But _you_ don't have to be a scientist: with LyX you
create just as easily a letter or a novel or a theatre play or film
script. A broad array of ready, well designed document layouts and style
modification and feature support packages are built in."


Is this an idea?

- Martin
 


pgpPEt5GhL7iB.pgp
Description: PGP signature

Re: LyX web site proposal

[Angus Leeming]

Martin Vermeer wrote:
> What about

[ snip some hard sell :-P ]

> Is this an idea?

It's a great idea. Check out the www-user repository, get yourself karma
and go for it.

-- 
Angus

Re: Mathfrak fonts broken in Windows version

[Drop Box]

I managed to fix it myself after a little detective work...
I grepped the source code for cmsy10, which provides mathcal, and found 
qfont_loader.C.  In here, one sees that the missing font is called eufm10:

{ LyXFont::MSB_FAMILY,
"msbm10",
"-*-msbm10-*-*-*-*-*-*-*-*-*-*-*-*" },

{ LyXFont::EUFRAK_FAMILY,
"eufm10",
"-*-eufm10-medium-*-*-*-*-*-*-*-*-*-*-*" },

{ LyXFont::WASY_FAMILY,
"wasy10",
"-*-wasy10-medium-*-*-*-*-*-*-*-*-*-*-*" }

The common name for this font is "Euclid Fraktur".
I found it at
http://cardiome.ucsd.edu/mathtype/Mathtype4TTFonts/
under the filename eufrak.ttf.

In order to get LyX to recognize it, we must change the TrueType name, which 
is different from the filename.  I managed to do this using a script called 
ttfname from

http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi_id=FontUtils#801ab246
by using the following command:
ttfname -n eufm10 eufrak.ttf eufm10.ttf

Now just install eufm10.ttf, restart LyX, and you should be up and fraking.  
:)  Of course it would be delightful if Uwe managed to add this font with 
the next installer.


-Bob

Re: Mathfrak fonts broken in Windows version

[Uwe Stöhr]

dropbox wrote:

I have LyX 1.3.6-1 installed on a few different windows machines.  The 
mathbb and mathcal fonts display properly, but mathfrak characters 
come out in the standard font.  I tried both bakoma and xft.  Any ideas?


I found the problem: The file "eufm10.ttf" is missing in the current 
version of the BaKoMa4LyX-package.
I attached the file, so that you can install it manually (you need to 
reconfigure LyX after this).


The next installer version will fix this. I also uploade a new version 
of BaKoMa4LyX.


regards Uwe


eufm10.ttf
Description: Binary data

[patch] updated BaKoMa4LyX package

[Uwe Stöhr]

Hello JMarc,

I uploaded a new version of the BaKoMa4LyX Windows font package to

ftp://ftp.devel.lyx.org/pub/incoming/

Could you please move it to

ftp://ftp.lyx.org/pub/lyx/contrib/

I missed the file eufm10.ttf so that fraktur characters couldn't be 
displayed in mathed.


thanks and regards
Uwe

Re: Instant preview in LyX/Win 1.4.0pre3

[Enrico Forestieri]

Angus Leeming <[EMAIL PROTECTED]> writes:

> "Our" agreement was simply that David Kastrup and, to a lesser extent,
> Jan-Åke Larsson created all the hooks needed by LyX in preview.sty and in
> dvipng. They'll certainly remember, albeit hazily. I was a PITA (that's
> "their arses") for a couple of months 

I don't think so. You are listed in the credits section of the dvipng docs ;-)

> I'm afraid I'm extremely busy tying up lose ends ATM before I start a new
> job on Monday. Please contact them on the AucTeX mailing list; you'll tell
> the story so much better than I could 

Ok, then. Good luck to you with your new job!

> > Then, still there is the problem that if a font is missing, the output
> > of the programs that are in charge to generate it is mixed to the
> > stdout of dvipng, thus confusing lyxpreview2bitmap.py. I think that
> > they should be launched redirecting their stdout to stderr.
> 
> Sounds reasonable. Get them to do so and then add a test to
> lyxpreview2bitmap.py for dvipng version >= 1.8 (as it perhaps will be) and
> you're done.
> 
> Welcome to the LyX developer team 

Wow! I got promoted on the field! ;-)
Then I am sorry that my Christmas holidays are at the end... ;-)

--
Enrico

Re: Instant preview in LyX/Win 1.4.0pre3

[Enrico Forestieri]

Angus Leeming <[EMAIL PROTECTED]> writes:

> I'm afraid I'm extremely busy tying up lose ends ATM before I start a new
> job on Monday. Please contact them on the AucTeX mailing list; you'll tell
> the story so much better than I could 

Done:

http://article.gmane.org/gmane.emacs.auctex.devel/870

--
Enrico