Test file
Here's a test file created in lyx-1.1.5fix1-1
that makes the CVS LyX core dump. Apparently
related to the table format change.
Remove the ref from the table and the crash
goes away. This is the only thing keeping
me from upgrading.
Yst. Martin
--
Martin Vermeer [EMAIL PROTECTED]
Helsinki University of Technology
Department of Surveying
P.O. Box 1200, FIN-02015 HUT, Finland
:wq
#LyX 1.1 created this file. For more info see http://www.lyx.org/
\lyxformat 2.16
\textclass article
\language default
\inputencoding latin1
\fontscheme default
\graphics default
\paperfontsize default
\spacing single
\papersize Default
\paperpackage a4
\use_geometry 0
\use_amsmath 0
\paperorientation portrait
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
\papersides 1
\paperpagestyle default
\layout Standard
\added_space_top 0.3cm \added_space_bottom 0.3cm \align center \LyXTable
multicol5
1 1 0 0 -1 -1 -1 -1
1 1 0 0
8 1 1 "" ""
0 8 1 0 0 0 0 "" ""
Einstein (eq.
\begin_inset LatexCommand \ref{eq:Einstein}
\end_inset
) says:
\layout Standard
\begin_inset Formula \begin{equation}
\label{eq:Einstein}
E=mc^{2}
\end{equation}
\end_inset
\the_end
Re: Core dump when setting preferences with Lyx 1.1.6pre2
Errr Let's get this straight. Before you Reconfigured, you couldn't open Edit-Preferences. After you reconfigured you could. But isn't LyX reconfigured as part of thr installation process Don't understand. Angus On Sunday 03 December 2000 02:01, Ben Cazzolato wrote: Mon, 27 Nov 2000 Hi Guys I am starting to use the pre-release of Lyx 1.1.6pre2 (downloaded RPM from ftp://ftp.sylvan.com/pub/lyx/) and I can get Lyx to core dump every time. I tried Edit-Preferences immediately after upgrading from 1.5.2 (without opening up Lyx first and reconfiguring) and it would crash every time. lyx: SIGSEGV signal caught Sorry, you have found a bug in LyX. If possible, please read 'Known bugs' under the Help menu and then send us a full bug report. Thanks! Bye. Aborted (core dumped) I then did as Angus suggested, ie 1. Open up LyX and Edit-Reconfigure. 2. Close LyX. 3. Open up LyX again. Many of these warnings will dissapear. Your lyxrc is soon to become redundant. Open up Edit-Preferences, make some spurious change (to activate the Save button) and Save the change. You''ll now have a preferences file in your .lyx directory. lycrc will never be read again; instead preferences will be used instead. In future, use the Edit-Preferences popup to make any changes to LyX's behaviour. And all seems to be well. Maybe there needs to be some check for people like myself who will do things without reading the instructions. Ben
Re: Core dump when setting preferences with Lyx 1.1.6pre2
"Angus" == Angus Leeming [EMAIL PROTECTED] writes: Angus Errr Let's get this straight. Before you Reconfigured, you Angus couldn't open Edit- Preferences. After you reconfigured you could. Angus But isn't LyX reconfigured as part of thr installation Angus process When installing, the system lyxrc.default is changed. What Reconfigure does is to change the user lyxrc.default. JMarc
Re: Some messages won't get translated
Why not? They appear in my lyx.pot file. I guess you mean that they aren't in yours? Admittedly, "GUI background" etc don't appear. Will investigate. Angus On Friday 01 December 2000 18:07, Pauli Virtanen wrote: This applies on LyX CVS head branch of Wed Nov 29 For your information: The following parts of LyX won't get translated, even if the translations exist. - The "tooltips" in the bottom of the preferences popup. - The Close and Cancel buttons in the popups "Preferences", "Document properties", "Paragraph properties", "Citation", "Cross reference" and "Table of contents". The translated text doesn't appear, but the shortcut works. - The "GUI background/text/selection/pointer" items in the "LyX objects" list in the preferences popup in pane "Look Feel"/"Colors" - The "Sys UI" and "User UI" buttons in the UI file browse popup from the preferences. - The "Sys Bind" and "User Bind" buttons in the bind file browse popup from the preferences. Pauli Virtanen
Re: Core dump when setting preferences with Lyx 1.1.6pre2
Well how about adding a flag to the system lyxrc.defaults. \user_reconfigure yes/no ??? Angus On Monday 04 December 2000 11:11, Jean-Marc Lasgouttes wrote: "Angus" == Angus Leeming [EMAIL PROTECTED] writes: Angus Errr Let's get this straight. Before you Reconfigured, you Angus couldn't open Edit- Preferences. After you reconfigured you could. Angus But isn't LyX reconfigured as part of thr installation Angus process When installing, the system lyxrc.default is changed. What Reconfigure does is to change the user lyxrc.default. JMarc
Re: Core dump when setting preferences with Lyx 1.1.6pre2
I guess that what is needed is a permanent entry in the system lyxrc.defaults \user_reconfigure 1.1.6 yes that is overridden by the corresponding entry in the user lyxrc.defaults \user_reconfigure 1.1.6 no Angus On Monday 04 December 2000 11:26, Angus Leeming wrote: Well how about adding a flag to the system lyxrc.defaults. \user_reconfigure yes/no ??? Angus On Monday 04 December 2000 11:11, Jean-Marc Lasgouttes wrote: "Angus" == Angus Leeming [EMAIL PROTECTED] writes: Angus Errr Let's get this straight. Before you Reconfigured, you Angus couldn't open Edit- Preferences. After you reconfigured you could. Angus But isn't LyX reconfigured as part of thr installation Angus process When installing, the system lyxrc.default is changed. What Reconfigure does is to change the user lyxrc.default. JMarc
Re: Core dump when setting preferences with Lyx 1.1.6pre2
"Angus" == Angus Leeming [EMAIL PROTECTED] writes: Angus I guess that what is needed is a permanent entry in the system Angus lyxrc.defaults \user_reconfigure 1.1.6 yes Angus that is overridden by the corresponding entry in the user Angus lyxrc.defaults Angus \user_reconfigure 1.1.6 no Or rather a way to see when configure was run for the last time, so that it can be automatically re-run if necessary (\last_configure_version 1.1.6) Anyway, no crash should happen! JMarc
Re: Installing Problems
On Fri, 1 Dec 2000, Amir Karger wrote: On Fri, Dec 01, 2000 at 12:43:02PM +, John Levon wrote: I imagine you mean xforms. In fact I think this might be a problem that was reported ages ago, around when I started reading lyx-devel. I had the hypothesis at the time that this was Xpm routines causing xforms to crash, because it couldn't allocate the colours. This is because the lyx xpm files don't have "m" (mono) options for when the colour can't be allocated, and xforms doesn't seem to like the Xpm routines failing like this. I really should add these tags to the icon files, but it is a boring job (I can't find a tool that adds them automatically :() What exactly do you need to do? I only ask because Perl can do *anything* automatically. (Well, most things. Usually.) -Amir Change the things like : " c None", ". c #", "X c #7B7B", "o c gray70" to : " c None", ". c # m black", "X c #7B7B m black", "o c gray70 m black" or similar. It can't be 100% automatic because it needs to be seen how it looks in mono (though the bw versions, where applicable, can be a guide). My perl is far too shallow to have a go at this... thanks john
Re: Core dump when setting preferences with Lyx 1.1.6pre2
On Monday 04 December 2000 11:41, Jean-Marc Lasgouttes wrote: "Angus" == Angus Leeming [EMAIL PROTECTED] writes: Angus I guess that what is needed is a permanent entry in the system Angus lyxrc.defaults \user_reconfigure 1.1.6 yes Angus that is overridden by the corresponding entry in the user Angus lyxrc.defaults Angus\user_reconfigure 1.1.6 no Or rather a way to see when configure was run for the last time, so that it can be automatically re-run if necessary (\last_configure_version 1.1.6) Good. Anyway, no crash should happen! Well, I can''t reproduce this: lyx-1.1.4, Reconfigure, Close. mv ~/.lyx/preferences ~/.lyx/preferences_safe lyx-1.1.6cvs, Edit-Preferences No crash. Don't see how we can find the root cause of the problem, therefore. Your suggested work around seems like the best way forward. Angus
Re: Key-binding documentation dilemma
Angus Leeming [EMAIL PROTECTED] writes: | Gentlemen, | | I've written the inset proposed by Jean-Marc. Currently, it's a little | cumbersome to use: | | Eg, type in the minibuffer: | | shortcut-insert line-end But this is not what we really want... we want an inset that shows the output of a lyx variable. the command to get the would f.ex. be: describe-variable default-language - "norsk" describe-function-binding line-end - "C-e" describe-binding C-x C-s - "buffer-save" What we want is a inset that encapsulates this. Lgb
Re: Key-binding documentation dilemma
Allan Rae [EMAIL PROTECTED] writes: | On Fri, 1 Dec 2000, Angus Leeming wrote: | | Gentlemen, | | I've written the inset proposed by Jean-Marc. Currently, it's a little | cumbersome to use: | | Eg, type in the minibuffer: | | shortcut-insert line-end | | And a little button appears in the text containing the immortal [C-e]. | | It isn't quite there yet (no Read(), Write(), Latex() functions, so you can't | save it and can't export it to latex, but not bad for an hour's hacking I | feel. | | Bundle it with the Note inset and submit it after 1.1.6. | | Read, Write and LaTeX functions should be pretty easy BTW. I really do not want it done this way... Lgb
PATCH: xform_macros.h and FormPrefernces::Colors
Attached is a patch that removes xform_macros.h. It also finishes off the Colors tab. I hope. Angus patch.diff.bz2
Re: Bug tracker
On Sun, 3 Dec 2000, Allan Rae wrote: On Fri, 1 Dec 2000, John Levon wrote: Me Angus have started up a prototype bug tracker for lyx at : http://sourceforge.net/bugs/?group_id=15212 We've certainly discussed this often enough but nobody has had the time or inclination to do anything about it. Thanks. What's involved in adding developers to the list of people who can do admin stuff? It'd be nice if we could make this official and have all the core developers able to work with it. To be added as an admin : 1) create a sourceforge account for yourself. https://sourceforge.net/account/register.php 2) mail me or angus (or any other admin of the project), giving the username, and you will be added as admin. I'm none too sure about opening this particular database up "officially", simply because the sourceforge facilities are a little, um, basic. For example, there's no way to add a field indicating LyX version number. Really nice would be a proper bugzilla or similar installed somewhere. Can you change the CVS link to go to http://www.devel.lyx.org/cvs.php3 instead? nope :(. I've just turned it off for now. There are a few other bugs JMarc had entries for in his announcements for 1.1.5fix2 that you might like to add also if they haven't already been fixed. Thanks for the pointer, I'll look these up. thanks john -- "An AMM performance has no beginning or ending. Sounds outside the performance are distinguished from it only by individual sensibility." - Victor Schonfield
Re: Key-binding documentation dilemma - what I will try
Lior Silberman [EMAIL PROTECTED] writes: | With regards the UserGuide, however, we must bear in mind that having a | list of keybindings indexed by the key combinations is not useful. Why is this so? | I will admit here that all of the above reflects the personal opinions of | a cua.bind user. That shows. Lgb
Re: Bug tracker
John Levon [EMAIL PROTECTED] writes: | Me Angus have started up a prototype bug tracker for lyx at : | | http://sourceforge.net/bugs/?group_id=15212 | | We've both found it quite handy (I know what still needs working on !), so | if anyone else can make use of it, just ask angus or me for an account and | we'll add you as admin. Can bug reports be entered by sending mail to [EMAIL PROTECTED]? (after I setup the redirection of course) Lgb
Re: Installing Problems
John Levon [EMAIL PROTECTED] writes: | Change the things like : | | " c None", | ". c #", | "X c #7B7B", | "o c gray70" | | to : | | " c None", | ". c # m black", | "X c #7B7B m black", | "o c gray70 m black" | | or similar. It can't be 100% automatic because it needs to be seen how it | looks in mono (though the bw versions, where applicable, can be a | guide). My perl is far too shallow to have a go at this... Have you verified that XForms still can use the icons after that change? Lgb
Re: Core dump when setting preferences with Lyx 1.1.6pre2
Angus Leeming [EMAIL PROTECTED] writes: | Errr | | Let's get this straight. Before you Reconfigured, you couldn't open | Edit-Preferences. After you reconfigured you could. Why does this make a difference? It really shouldn't. Lgb
Re: Bug tracker
On 4 Dec 2000, Lars Gullik Bjønnes wrote: John Levon [EMAIL PROTECTED] writes: | Me Angus have started up a prototype bug tracker for lyx at : | | http://sourceforge.net/bugs/?group_id=15212 | | We've both found it quite handy (I know what still needs working on !), so | if anyone else can make use of it, just ask angus or me for an account and | we'll add you as admin. Can bug reports be entered by sending mail to [EMAIL PROTECTED]? (after I setup the redirection of course) Lgb Yep, I was hoping you might say that ;) Currently everything goes to me, it's trivial to change. thanks john -- "An AMM performance has no beginning or ending. Sounds outside the performance are distinguished from it only by individual sensibility." - Victor Schonfield
Re: Installing Problems
On 4 Dec 2000, Lars Gullik Bjønnes wrote: John Levon [EMAIL PROTECTED] writes: | Change the things like : | | " c None", | ". c #", | "X c #7B7B", | "o c gray70" | | to : | | " c None", | ". c # m black", | "X c #7B7B m black", | "o c gray70 m black" | | or similar. It can't be 100% automatic because it needs to be seen how it | looks in mono (though the bw versions, where applicable, can be a | guide). My perl is far too shallow to have a go at this... Have you verified that XForms still can use the icons after that change? Lgb AFAIK Xforms just uses Xpm library, so the answer is yes. Of course if I get round to this one, I'll test it :) thanks john -- "An AMM performance has no beginning or ending. Sounds outside the performance are distinguished from it only by individual sensibility." - Victor Schonfield
Re: Core dump when setting preferences with Lyx 1.1.6pre2
Angus Leeming [EMAIL PROTECTED] writes: | Anyway, no crash should happen! | | Well, I can''t reproduce this: | | lyx-1.1.4, Reconfigure, Close. | mv ~/.lyx/preferences ~/.lyx/preferences_safe | lyx-1.1.6cvs, Edit-Preferences | | No crash. Don't see how we can find the root cause of the problem, therefore. | Your suggested work around seems like the best way forward. I don't really like to use work arounds for problems we don't understand. The best way forward is to find out _why_ lyx craches and fix that reason or the wrong assumtions in the code. Everything else will just at bloat and complexity. Lgb
Re: menu-open problem in all bind files
Allan Rae [EMAIL PROTECTED] writes: | 4. As above but do a case insensitive search (IIRC STL provides such an | option) No it does not, but we provide it in lstrings.h Lgb
[PATCH] two 1.1.6 bug fixes
The attached patch fixes the two bugs :
1) figures wouldn't work if pspell was enabled. This bug is a direct
result of not having functions in their proper files ;)
2) Fix most of the cases of the gs hangs with a workaround. I have
verified this on 0.88 and 0.89. The remaining cases involve popup menus,
where it seems events are being discarded, and I think this will require
an xforms release to fix totally.
This workaround is actually not any uglier than what we had before ...
thanks
john
--
"An AMM performance has no beginning or ending. Sounds outside the performance
are distinguished from it only by individual sensibility."
- Victor Schonfield
? lib/examples/14538vFW0yy
? lib/examples/145408rEbRG
? lib/examples/14610igQICW
Index: ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/ChangeLog,v
retrieving revision 1.709
diff -u -p -r1.709 ChangeLog
--- ChangeLog 2000/12/04 09:15:50 1.709
+++ ChangeLog 2000/12/04 11:44:48
@@ -1,3 +1,9 @@
+2000-12-04 John Levon [EMAIL PROTECTED]
+
+ * src/spellchecker.C: fix figures with pspell enabled
+
+ * src/insets/figinset.C: workaround for gs hang xforms bug
+
2000-11-30 Dekel Tsur [EMAIL PROTECTED]
* Several files: Allow compilation when the compiler doesn't
Index: src/spellchecker.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/spellchecker.C,v
retrieving revision 1.41
diff -u -p -r1.41 spellchecker.C
--- src/spellchecker.C 2000/11/28 06:46:05 1.41
+++ src/spellchecker.C 2000/12/04 11:44:48
@@ -65,12 +65,8 @@
#include "encoding.h"
#include "support/lstrings.h"
-//#define USE_PSPELL 1
-
#ifdef USE_PSPELL
-
-#include pspell/pspell.h
-
+# include pspell/pspell.h
#endif
using std::reverse;
@@ -110,10 +106,8 @@ PspellManager * sc;
FD_form_spell_options *fd_form_spell_options = 0;
FD_form_spell_check *fd_form_spell_check = 0;
-//void sigchldhandler(int sig);
void sigchldhandler(pid_t pid, int *status);
-//extern void sigchldchecker(int sig);
extern void sigchldchecker(pid_t pid, int *status);
#ifndef USE_PSPELL
@@ -628,7 +622,7 @@ void sc_clean_up_after_error()
-// Send word to ispell and get reply
+// Send word to pspell and get reply
static
isp_result * sc_check_word(string const word)
{
@@ -965,10 +959,8 @@ bool RunSpellChecker(BufferView * bv)
return true;
}
}
-
-
-#ifndef USE_PSPELL
+#warning should go somewhere more sensible
void sigchldhandler(pid_t pid, int * status)
{
if (isp_pid 0)
@@ -980,12 +972,3 @@ void sigchldhandler(pid_t pid, int * sta
}
sigchldchecker(pid, status);
}
-
-#else
-
-void sigchldhandler(pid_t, int *)
-{
- // do nothing
-}
-
-#endif
Index: src/insets/figinset.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/insets/figinset.C,v
retrieving revision 1.93
diff -u -p -r1.93 figinset.C
--- src/insets/figinset.C 2000/11/28 06:46:06 1.93
+++ src/insets/figinset.C 2000/12/04 11:44:52
@@ -167,10 +167,14 @@ void kill_gs(int pid, int sig)
}
-extern "C" // static
-int GhostscriptMsg(FL_OBJECT *, Window, int, int,
- XEvent * ev, void *)
+extern "C" {
+static
+int GhostscriptMsg(XEvent * ev, void *)
{
+ // bin all events not of interest
+ if (ev-type != ClientMessage)
+ return FL_PREEMPT;
+
XClientMessageEvent * e = reinterpret_castXClientMessageEvent*(ev);
if (lyxerr.debugging()) {
@@ -297,7 +301,8 @@ int GhostscriptMsg(FL_OBJECT *, Window,
}
break;
}
- return 0;
+ return FL_PREEMPT;
+}
}
@@ -378,6 +383,9 @@ void AllocGrays(int num)
}
+// xforms doesn't define this
+extern "C" FL_APPEVENT_CB fl_set_preemptive_callback(Window, FL_APPEVENT_CB, void *);
+
static
void InitFigures()
{
@@ -389,9 +397,10 @@ void InitFigures()
// first get visual
gs_color = false;
if (lyxrc.use_gui) {
- fl_add_canvas_handler(figinset_canvas, ClientMessage,
- GhostscriptMsg,
- current_view-owner()-getForm());
+ /* we want to capture every event, in order to work around an
+* xforms bug.
+*/
+ fl_set_preemptive_callback(fl_get_canvas_id(figinset_canvas),
+GhostscriptMsg, 0);
local_gc_copy = createGC();
@@ -430,9 +439,6 @@ void DoneFigures()
figures.clear();
lyxerr.debug() "Unregistering figures..." endl;
-
- fl_remove_canvas_handler(figinset_canvas, ClientMessage,
-
Re: Key-binding documentation dilemma
Ummm... Aren't you wanting three different insets for your three different types of info. My quick (and fully working) hack does exactly what your describe-function-binding line-end - "C-e" would do. I guess that you could use the one inset, but don't see why. Angus On Monday 04 December 2000 12:33, Lars Gullik Bjønnes wrote: Angus Leeming [EMAIL PROTECTED] writes: | Gentlemen, | | I've written the inset proposed by Jean-Marc. Currently, it's a little | cumbersome to use: | | Eg, type in the minibuffer: | | shortcut-insert line-end But this is not what we really want... we want an inset that shows the output of a lyx variable. the command to get the would f.ex. be: describe-variable default-language - "norsk" describe-function-binding line-end - "C-e" describe-binding C-x C-s - "buffer-save" What we want is a inset that encapsulates this. Lgb
Re: try: M-f v followed by clicking in workarea
Allan Rae [EMAIL PROTECTED] writes: | LyXAction::funcHasFlag: No info about kb_action: 8 | A truly unknown func! Care to investigate? Why is anything passed to LyXAction/LyXFunc in this case? Lgb
Re: View-PDF (pdflatex) vs View-Update-PDF (pdflatex)
Allan Rae [EMAIL PROTECTED] writes: | On Sun, 3 Dec 2000, Dekel Tsur wrote: | | On Sun, Dec 03, 2000 at 05:23:18PM +1000, Allan Rae wrote: | | Viewing requires one run of pdflatex. Updating runs pdflatex 6 times | using the exact same file -- no changes in between runs. | | This doesn't make sense as preview = update + run viewer. | However, if you consistently getting this behavior, make your files | available for download so we can check this. | | I tried a few more times and got 6 runs of pdflatex with either | update or view. It would appear that I'd reported this "bug" a little too | early. | | I've yet to run pdflatex by hand to find out why LyX wants to run pdflatex | 6 times on my file. It does contain one reference so I do expect 2 or 3 | runs but 6 seems like something is wrong. Most likely some log messages that triggers reruns. Have you looked at the log file? do all your references have corresponding labels? Lgb
Re: Key-binding documentation dilemma
Angus Leeming [EMAIL PROTECTED] writes: | Ummm... | | Aren't you wanting three different insets for your three different types of | info. My quick (and fully working) hack does exactly what your | | describe-function-binding line-end - "C-e" | | would do. I guess that you could use the one inset, but don't see | why. Why have three identical insets? And insets have no business poking around in the bindings list, that is the task of lyxfuncs. We can easily also have lyxfunc like "today" instead of using ert... "show-variable author" Why go for the specific implementation when a generic implementation will be just as easy _and_ be a lot more powerful. Lgb
Re: Bug tracker
On 4 Dec 2000, Lars Gullik Bjønnes wrote: I'd be happy to have a bugzilla at baywatch.lyx.org. Just tell me what we need. Lgb I'm afraid installation looks non-trivial :( In terms of supporting packages, bugzilla (http://www.mozilla.org/projects/bugzilla/) needs an MySQL installation, plus the supporting Perl modules. I notice you only have postgre on baywatch currently. Or possibly GNATS (http://sources.redhat.com/gnats/) might be a better choice. It certainly looks simpler to install, and doesn't need anything other than emacs (!) as support. john -- "An AMM performance has no beginning or ending. Sounds outside the performance are distinguished from it only by individual sensibility." - Victor Schonfield
Re: try: M-f v followed by clicking in workarea
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: Lars Allan Rae [EMAIL PROTECTED] writes: | Lars LyXAction::funcHasFlag: No info about kb_action: 8 | A truly Lars unknown func! Lars Care to investigate? Lars Why is anything passed to LyXAction/LyXFunc in this case? I'd say the cursor is on a submenu, which number is the default number given by xforms (version control is the heighth entry). So when the menu times out, xforms returns 8 and we do not know what to do with it. I'd say it's mostly harmless, but I do not have a simple fix. How come there is no lyxfunc with number 8 (it is supposed to be LFUN_MENUSENDTO)? JMarc
Re: Key-binding documentation dilemma
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: | Yes, that's what I had in mind originally. And lyxfuncs allowed for | this inset should be marked explicitely in LyXAction. Hmmm... rather mark all functions that outputs something... | So, would you be ready to accept that in 1.1.6? I would hope to avoid that. | 1.1.6fix1? That would be your call. | Another question: do you think we should have a 1.1.5fix3? Your call. But I don't see any great demand. Lgb
Re: Key-binding documentation dilemma
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: Lars Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: | Lars Yes, that's what I had in mind originally. And lyxfuncs allowed Lars for | this inset should be marked explicitely in LyXAction. Lars Hmmm... rather mark all functions that outputs something... No, "output something and do not have any side effect". Lars | So, would you be ready to accept that in 1.1.6? Lars I would hope to avoid that. When do you expect 1.1.6 will be out? Lars | 1.1.6fix1? Lars That would be your call. OK. Lars | Another question: do you think we should have a 1.1.5fix3? Lars Your call. But I don't see any great demand. It would be nice to have a reasonably stable 1.1.5 version when 1.1.6 comes out. Of course, not having it would be a nice incentive for people to upgrade to 1.1.6 :) Anyway, we should probably be prepared to have a 1.1.6fix1 one week after 1.1.6 (I doubt there will not be serious problems). JMarc
Re: try: M-f v followed by clicking in workarea
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: Lars it is not a timeout. Indeed. I stand corrected. Lars | xforms returns 8 and we do not know what to do with | it. I'd Lars say it's mostly harmless, but I do not have a simple fix. How | Lars come there is no lyxfunc with number 8 (it is supposed to be | Lars LFUN_MENUSENDTO)? Lars I also belive this to be harmless. Lars Would be nice to know why it happens and if we can avoid it. I'll have a quick look. JMarc
Re: Key-binding documentation dilemma
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: | "Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: | | Lars Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: | | Lars Yes, that's what I had in mind originally. And lyxfuncs allowed | Lars for | this inset should be marked explicitely in LyXAction. | | Lars Hmmm... rather mark all functions that outputs something... | | No, "output something and do not have any side effect". Perhaps... | | Lars | So, would you be ready to accept that in 1.1.6? | | Lars I would hope to avoid that. | | When do you expect 1.1.6 will be out? I want one more prerelease out... I am not sure if we really have to wait for _all_ problems to be fixed, but we should at least investigate the reports that we alread have got. - some dead key issues - keymap issues - multicolumn tabular - preferences crash. I'like the new color stuff tested a bit more, and this is the main reason for pre3. I'll try to have a pre3 ready for the end of this week. Go bug hunting folks(and please provide fixes as well) Lgb
Re: Test file
This is dying in Buffer::isLatex()
bool Buffer::isLatex() const
{
return textclasslist.TextClass(params.textclass).outputType() == LATEX;
}
This hack works:
bool Buffer::isLatex() const
{
return true;
}
All displays correctly.
This fails on return:
bool Buffer::isLatex() const
{
LyXTextClassList::size_type tclass = params.textclass;
OutputType type = textclasslist.TextClass(tclass).outputType();
bool result = (type == LATEX);
lyxerr "type " type " " LATEX std::endl;
lyxerr "result " result std::endl;
return result;
}
From dbx:
(dbx) r
Warning: Setting language `default' to `english'.
type 1 1
result 1
signal Segmentation fault at
warning: "buffer.C":2097 has no code associated with it
[isLatex__C6BufferXv
warning: "buffer.C":2097 has no code associated with it
:2097 +0x201e1d7d,0x1201e1d7c]
line 2097 beyond end of file
(dbx) where
0 isLatex__C6BufferXv(this = (nil)) ["buffer.C":2097, 0x1201e1d7c]
1 __ct__8InsetRefXRC18InsetCommandParamsRC6Buffer(0x0, 0xe, 0x12030ba34,
0x14
Can some guru explain to me why (this) should be (nil)?
Angus
On Monday 04 December 2000 10:12, Martin Vermeer wrote:
Here's a test file created in lyx-1.1.5fix1-1
that makes the CVS LyX core dump. Apparently
related to the table format change.
Remove the ref from the table and the crash
goes away. This is the only thing keeping
me from upgrading.
Yst. Martin
Content-Type: text/plain; charset="us-ascii"; name="Attachment: 1"
Content-Transfer-Encoding: 7bit
Content-Description:
[PATCH] big KDE reorganisation
The attached re-organises the KDE frontend to be much nicer in terms
of number of files per directory. It also contains a full sync up to my
tree.
I have supplied a tarfile, as a diff would be completely unweildy in this
case. To apply :
patch -p0 kdebig.diff
cd src/frontends
tar zxvf kdebig.tar.gz
sh reorg.script
This should do the correct cvs add/removes for you, and apply the small
bits needed outside of kde/.
Please apply
thanks
john
--
"An AMM performance has no beginning or ending. Sounds outside the performance
are distinguished from it only by individual sensibility."
- Victor Schonfield
#!/bin/sh
removeme="copyrightdlgdata.C indexdlgdata.C paraextradlgdata.C parageneraldlgdata.C
printdlgdata.C copyrightdlgdata.h indexdlgdata.h paraextradlgdata.h
parageneraldlgdata.h printdlgdata.h lyxgui.kdevprj dlg/copyright.dlg dlg/index.dlg
dlg/paraextra.dlg dlg/parageneral.dlg dlg/print.dlg"
addme="moc/Makefile.am dlg/Makefile.am dlg/copyrightdlgdata.C dlg/indexdlgdata.C
dlg/parabelowdlgdata.h dlg/paraextradlgdata.h dlg/printdlgdata.C dlg/tabstack.h
dlg/copyrightdlgdata.h dlg/indexdlgdata.h dlg/paradlgdata.C dlg/printdlgdata.h
dlg/emptytable.Cdlg/paraabovedlgdata.C dlg/paradlgdata.h
dlg/parageneraldlgdata.C dlg/tabcreatedlgdata.C dlg/emptytable.h
dlg/paraabovedlgdata.h dlg/parageneraldlgdata.h dlg/tabcreatedlgdata.h
dlg/parabelowdlgdata.C dlg/paraextradlgdata.C dlg/tabstack.h dlg/tabstack.C
dlg/moc/Makefile.am dlg/dialogs/copyright.dlg dlg/dialogs/index.dlg
dlg/dialogs/paraextra.dlg dlg/dialogs/parageneral.dlg dlg/dialogs/print.dlg
dlg/dialogs/para.dlg dlg/dialogs/tabcreate.dlg dlg/dialogs/paraabove.dlg
dlg/dialogs/parabelow.dlg"
rm $removeme
cvs delete $removeme
cvs add $addme
Index: ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/ChangeLog,v
retrieving revision 1.709
diff -u -p -r1.709 ChangeLog
--- ChangeLog 2000/12/04 09:15:50 1.709
+++ ChangeLog 2000/12/04 13:58:23
@@ -1,3 +1,14 @@
+2000-12-04 John Levon [EMAIL PROTECTED]
+
+ * configure.in: add new KDE Makefiles
+ * src/vspace.h: return GlueLength not a normal one
+ * src/support/lstrings.h:
+ * src/support/lstrings.C: add isStrUnsignedInt(),
+ strToUnsignedInt()
+
+ * src/frontends/kde/*: big reorganisation, update
+ FormParagraph, add FormTabCreate
+
2000-11-30 Dekel Tsur [EMAIL PROTECTED]
* Several files: Allow compilation when the compiler doesn't
Index: configure.in
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/configure.in,v
retrieving revision 1.56
diff -u -p -r1.56 configure.in
--- configure.in2000/11/28 16:38:25 1.56
+++ configure.in2000/12/04 13:58:23
@@ -297,6 +297,9 @@ AC_OUTPUT([Makefile \
src/frontends/support/Makefile \
src/frontends/xforms/Makefile \
src/frontends/kde/Makefile \
+ src/frontends/kde/moc/Makefile \
+ src/frontends/kde/dlg/Makefile \
+ src/frontends/kde/dlg/moc/Makefile \
src/frontends/gnome/Makefile \
], [sed -e "/POTFILES =/r po/POTFILES" po/Makefile.in po/Makefile])
diff -u -p -r1.13 vspace.h
--- src/vspace.h2000/09/14 17:53:07 1.13
+++ src/vspace.h2000/12/04 13:58:24
@@ -222,7 +222,7 @@ public:
// access functions
vspace_kind kind() const { return kin; }
///
- LyXLength length() const { return len; }
+ LyXGlueLength length() const { return len; }
// a flag that switches between \vspace and \vspace*
bool keep() const { return kp; }
diff -u -p -r1.33 lstrings.C
--- src/support/lstrings.C 2000/11/15 03:22:08 1.33
+++ src/support/lstrings.C 2000/12/04 13:58:30
@@ -95,9 +95,39 @@ bool isStrInt(string const str)
}
+bool isStrUnsignedInt(string const str)
+{
+ if (str.empty()) return false;
+
+ // Remove leading and trailing white space chars.
+ string const tmpstr = frontStrip(strip(str, ' '), ' ');
+ if (tmpstr.empty()) return false;
+
+ string::const_iterator cit = tmpstr.begin();
+ string::const_iterator end = tmpstr.end();
+ for (; cit != end; ++cit) {
+ if (!isdigit((*cit))) return false;
+ }
+ return true;
+}
+
+
int strToInt(string const str)
{
if (isStrInt(str)) {
+ // Remove leading and trailing white space chars.
+ string const tmpstr = frontStrip(strip(str, ' '), ' ');
+ // Do the conversion proper.
+ return lyx::atoi(tmpstr);
+ } else {
+ return 0;
+ }
+}
+
+
+unsigned int strToUnsignedInt(string const str)
+{
+ if (isStrUnsignedInt(str)) {
// Remove leading and
Protected Space Incompatibility Lyx 1.1.4fix3 and 1.1.5fix2
Hello, I use LyX 1.1.4fix3 at home and LyX 1.1.5fix2 at work, that is i386 GNU/Linux Debian Potato and a current Debian Woody. Works like a charm, but: LyX 1.1.5 writes a construct that breaks 1.1.4: \layout Description a\SpecialChar ~ b c LyX 1.1.4 expects: \layout Description a\proctected_separator b c Unfortunately, reading the first may mess up the following line as well, so that your document is really shredded. Since LyX has been very compatible between version so far, I would appreciate it, if LyX 1.1.5fix3 would be compatible with older version again. If you want to reproduce the bug: Open a new document in lyx 1.1.5, set style to description, type a word, type C-space (protected space), type another word, space, and another word. Save that document and try to load it with lyx 1.1.4. Please note that I am not subscribed to the list, sorry, and there is no archive. So please send me an email-copy. Apologies if the bug is already known. Thomas [EMAIL PROTECTED]
Re: Test file
Angus Leeming [EMAIL PROTECTED] writes: | This is dying in Buffer::isLatex() Are you sure that inlining is not playing tricks on you? Seems almost liek isLatex is beeing called on a buffer that has just been deleted... Lgb
cvs question
Jean-Marc has just applied my FormPreferences/remove xform_macros.h patch. In the process of "cvs update", I get the line: R src/frontends/xforms/xform_macros.h Now when I create a patch, I have: Index: src/frontends/xforms/xform_macros.h === RCS file: xform_macros.h diff -N xform_macros.h --- /tmp/cvs645r8p Mon Dec 4 15:21:34 2000 +++ /dev/null Tue May 5 22:32:27 1998 @@ -1,30 +0,0 @@ -#ifndef XFORM_MACROS_H -#define XFORM_MACROS_H - -/** Collection of useful macros to assist in correctly wrapping and -mapping C callbacks to the C++ member functions. - */ - etc My question: Is "cvs remove src/frontends/xforms/xform_macros.h" the correct call and if so, what other call should/can I make to actually remove this file from the repository. Or should this be left to the "applier". Ie, how do we get the call: src/frontends/xforms/xform_macros.h is not needed anymore. Removed. Just interested... Angus
Re: cvs question
Angus Leeming [EMAIL PROTECTED] writes: | Jean-Marc has just applied my FormPreferences/remove xform_macros.h patch. | | In the process of "cvs update", I get the line: | R src/frontends/xforms/xform_macros.h This is because you have scheduled the file for "R"emoval | Is "cvs remove src/frontends/xforms/xform_macros.h" the correct call and if | so, what other call should/can I make to actually remove this file from the | repository. Or should this be left to the "applier". To be able to remove the file from the repository you have to have write access. The actual remove is done upon commit. | Ie, how do we get the call: | | src/frontends/xforms/xform_macros.h is not needed anymore. Removed. what do you mean? Lgb
Re: cvs question
"Angus" == Angus Leeming [EMAIL PROTECTED] writes: Angus Jean-Marc has just applied my FormPreferences/remove Angus xform_macros.h patch. In the process of "cvs update", I get the Angus line: R src/frontends/xforms/xform_macros.h I forgot to remove it from my side. The "cvs remove" you did had not effect on the server, just on your local copy. JMarc
Re: cvs question
On Monday 04 December 2000 15:15, Lars Gullik Bjønnes wrote: Angus Leeming [EMAIL PROTECTED] writes: | Jean-Marc has just applied my FormPreferences/remove xform_macros.h | patch. | | In the process of "cvs update", I get the line: | R src/frontends/xforms/xform_macros.h This is because you have scheduled the file for "R"emoval | Is "cvs remove src/frontends/xforms/xform_macros.h" the correct call and | if so, what other call should/can I make to actually remove this file | from the repository. Or should this be left to the "applier". To be able to remove the file from the repository you have to have write access. The actual remove is done upon commit. Sure. | Ie, how do we get the call: | | src/frontends/xforms/xform_macros.h is not needed anymore. Removed. Well, in the past when files have been removed from the repository to www.devel.lyx.org, anybody doing a subsequent "cvs update" of their local repository gets such a message rather than the R src/frontends/xforms/xform_macros.h type call. My point is that the file src/frontends/xforms/xform_macros.h does not now exist in my repository. Good. However, when I do a subsequent "cvs diff", I get a patch that references it in the www.devel.lyx.org directory. It's not beeing updated here (not added to my tree when I do a "cvs update"), but it's not been removed from www.devel. Merely interested... Angus
Re: [PATCH] big KDE reorganisation
The attached re-organises the KDE frontend to be much nicer in terms of number of files per directory. It also contains a full sync up to my tree. I don't know what the others think but I think it would be rather nice if you avoided sending 147 kByte patches to the list. Some people have limited space in there mailboxes and/or limited bandwidth and/or have to pay for volume. Can't you place them somewhere on a www/ftp server and simply send the URL? Andre' -- André Pönitz [EMAIL PROTECTED]
Re: [PATCH] big KDE reorganisation
On Mon, 4 Dec 2000, Andre Poenitz wrote: The attached re-organises the KDE frontend to be much nicer in terms of number of files per directory. It also contains a full sync up to my tree. I don't know what the others think but I think it would be rather nice if you avoided sending 147 kByte patches to the list. Some people have limited space in there mailboxes and/or limited bandwidth and/or have to pay for volume. Deepest apologies. Can't you place them somewhere on a www/ftp server and simply send the URL? Yes, sorry. john -- "An AMM performance has no beginning or ending. Sounds outside the performance are distinguished from it only by individual sensibility." - Victor Schonfield
Re: [PATCH] big KDE reorganisation
"John" == John Levon [EMAIL PROTECTED] writes: John It does. The things Lars questioned was the addition of John isStrUnsignedInt() (which I need to get signed-correctness John right, and is nice thing IMHO) and the changing in vspace.h I'll apply it then. Lars will be free after that to coerce you to change the code back. JMarc
Re: [PATCH] big KDE reorganisation
John Levon [EMAIL PROTECTED] writes: | On 4 Dec 2000, Jean-Marc Lasgouttes wrote: | | Does your patch include the former FormPara improvements? I had not | applied it earlier because it seem Lars had problems with it. | | I can apply the patch if there is no problem with it. | | JMArc | | It does. The things Lars questioned was the addition of isStrUnsignedInt() | (which I need to get signed-correctness right, and is nice thing IMHO) and | the changing in vspace.h I am not quite happy about the isStr... but I will change this later when we begin to use the cast library from Boost. | The vspace.h thing seems "obviously correct" IMHO (the actual thing stored | is a LyXGlueLength after all), but if people have a problem with it, can | you still apply, then I can send a fixup patch for KDE to re-insert the | hack I removed, until such a time the vspace.h patch is OK to apply. | | Lars didn't comment on my reply to his questions, I don't know whether | this is "silent assent" or not :) I think you can count it as that... Lgb
Re: [PATCH] big KDE reorganisation
"John" == John Levon [EMAIL PROTECTED] writes: John The attached re-organises the KDE frontend to be much nicer in John terms of number of files per directory. It also contains a full John sync up to my tree. John I have supplied a tarfile, as a diff would be completely John unweildy in this case. To apply : John patch -p0 kdebig.diff cd src/frontends tar zxvf kdebig.tar.gz John sh reorg.script John This should do the correct cvs add/removes for you, and apply John the small bits needed outside of kde/. Does your patch include the former FormPara improvements? I had not applied it earlier because it seem Lars had problems with it. I can apply the patch if there is no problem with it. JMArc
Re: [PATCH] big KDE reorganisation
On 4 Dec 2000, Jean-Marc Lasgouttes wrote: Does your patch include the former FormPara improvements? I had not applied it earlier because it seem Lars had problems with it. I can apply the patch if there is no problem with it. JMArc It does. The things Lars questioned was the addition of isStrUnsignedInt() (which I need to get signed-correctness right, and is nice thing IMHO) and the changing in vspace.h The vspace.h thing seems "obviously correct" IMHO (the actual thing stored is a LyXGlueLength after all), but if people have a problem with it, can you still apply, then I can send a fixup patch for KDE to re-insert the hack I removed, until such a time the vspace.h patch is OK to apply. Lars didn't comment on my reply to his questions, I don't know whether this is "silent assent" or not :) thanks john -- "An AMM performance has no beginning or ending. Sounds outside the performance are distinguished from it only by individual sensibility." - Victor Schonfield
Re: Protected Space Incompatibility Lyx 1.1.4fix3 and 1.1.5fix2
I'm not sure anybody promised backward compatability... Anyway, it's not
going to happen! Forward compatibility is Ok.
If you're not going to upgrade and use the same version of lyx on both
machines, then the following little file will do the trick:
conv_new2old.sed
# Replace all instances of
# xyz \SpecialChar ~
# abc
# with
# xyz
# \protected_separator
# abc
/[\]SpecialChar ~/{
s/[\]SpecialChar ~//
a\
\\protected_separator
}
Use as
sed -f conv_new2old.sed file_newformat.lyx file_oldformat.lyx
Angus
On Monday 04 December 2000 14:40, Thomas Steffen wrote:
Hello,
I use LyX 1.1.4fix3 at home and LyX 1.1.5fix2 at work, that is i386
GNU/Linux Debian Potato and a current Debian Woody. Works like a
charm, but: LyX 1.1.5 writes a construct that breaks 1.1.4:
\layout Description
a\SpecialChar ~
b c
LyX 1.1.4 expects:
\layout Description
a\proctected_separator
b c
Unfortunately, reading the first may mess up the following line as
well, so that your document is really shredded.
Since LyX has been very compatible between version so far, I would
appreciate it, if LyX 1.1.5fix3 would be compatible with older version
again.
If you want to reproduce the bug: Open a new document in lyx 1.1.5,
set style to description, type a word, type C-space (protected space),
type another word, space, and another word. Save that document and try
to load it with lyx 1.1.4.
Please note that I am not subscribed to the list, sorry, and there is
no archive. So please send me an email-copy. Apologies if the bug is
already known.
Thomas [EMAIL PROTECTED]
Re: export LANG=fr does not work on my suse6.2
"Yann" == Yann MORERE [EMAIL PROTECTED] writes: Yann hello, lyx users I've got a problem, when trying to get the Yann french language in the menus. Yann like said in the customization file, i export the LANG variable Yann : Yann export LANG=fr Yann i use a suse6.2. Is there another thing to do. I compiled lyx Yann with the nls support like noticed in the customization file. Yann Is anybogy got the problem? Yann I must say that there are other variable under suse LC_LANG Yann LANGUAGE which one should be set? Did you fix your problem? Which version of LyX is that? Does compiling with --with-included-gettext help? Did you try the other variables (LC_LANG?) JMarc
Re: Fwd: Re: Mandrake and KDe frontend
"Asger" == Asger K Alstrup Nielsen [EMAIL PROTECTED] writes: Asger Therefore, I must retract the argument that GUII will make the Asger model more basic, since obviously it isn't for the dialogs and Asger the menus. Thanks :) Asger If you by infrastructure mean the model abstraction, yes, this Asger will be easy. But once again, you basically just shove Asger complexity into the front-ends: Each front-end has to implement Asger the rest. No, because, except for xforms, the other toolkits have all that is needed to implement multiple toolbars, I guess. I won't comment on MVC, since it's been something I'm very fuzzy about. Asger Fair enough. Here's a section from the book "Design Patterns" Asger that explains the MVC concept: [snip] Thanks for refreshing my memories! Concerning the non-spearation of VC in menus/toolbar, I plead incompetence. I just rely on others to do it :) JMarc
Re: patch: Bug fixes
"Dekel" == Dekel Tsur [EMAIL PROTECTED] writes: Dekel This patch fixes few Dekel issues with RTL cursor, and also - Open all floats before Dekel spellchecking to enable spellchecking of their contents - Fix Dekel the bug where selecting with the mouse some text that ends with Dekel a closed float causes the float to open. Do we really want to open floats before spellchecking? This means that they will remain open afterwards, isn't it? I'm not sure about the answer, I just ask :) Dekel PS: Should I prepare a patch for 1.1.5fix ? Yes this would probably be welcome. In fact I would like to release 1.1.5fix3 if we can get the following fixed: - make sure it compiles with RH7 - introduce John's fix to figinset rendering if it turns out to be good (I think it is a major pain for people). - make sure the dead key situation with xforms 0.89 is solved. I believe these three fixes would warrant a new fix release. JMarc
Re: Some messages won't get translated
On Mon, Dec 04, 2000 at 11:23:31AM +, Angus Leeming wrote:
Why not? They appear in my lyx.pot file. I guess you mean that they aren't in
yours?
Admittedly, "GUI background" etc don't appear. Will investigate.
You should use 'xcol.name = _("GUI background")' instead of using N_().
There are several places in your code that need to fixed.
Note that in some places you need to keep the N_() but put a _() when the
string is used. For example, keep the N_() in LyXRC::getDescription but
in FormPreferences::feedback you need to put
str = formatted(_(str), ...)
Re: Test file
On Mon, Dec 04, 2000 at 03:56:53PM +0100, Lars Gullik Bjnnes wrote: Angus Leeming [EMAIL PROTECTED] writes: | This is dying in Buffer::isLatex() Are you sure that inlining is not playing tricks on you? Seems almost liek isLatex is beeing called on a buffer that has just been deleted... The real problem is the following line in LyXParagraph::CopyIntoMinibuffer(): minibuffer_inset = GetInset(pos)-Clone(*current_view-buffer()); As current_view hasn't been initialized yet, *current_view-buffer()) is junk. I've already mentioned this problem. Possible solution are 1) Change the first parameter of CopyIntoMinibuffer() from 'BufferParams const ' to 'Buffer const '. 2) Do not call to CopyIntoMinibuffer in LyXTabular::OldFormatRead().
Re: Protected Space Incompatibility Lyx 1.1.4fix3 and 1.1.5fix2
Angus Leeming [EMAIL PROTECTED] writes: I'm not sure anybody promised backward compatability... Anyway, it's not going to happen! Forward compatibility is Ok. Beg to differ. Forward compatibility is a must and therefore not worth mentioning. Backward compatibility is nice to have, and I would assume it between stable minor revisions. So far LyX *was* backward compatible, at least between the releases I have used (thats 1.0.1 to 1.1.5 IIRC). Remember the Word 97 thingy? If you're not going to upgrade and use the same version of lyx on both machines, then the following little file will do the trick: Obviously this is only the second best solution. It would certainly be nice to have this script in a complete form with some documentation in the distribution. Is this going to happen? If someone can point out the differences, I could at least collect them and try my best at a script (perl, that is :-)). sed -f conv_new2old.sed file_newformat.lyx file_oldformat.lyx Or a couple of keystrokes on XEmacs, yes, that is always possible. Once you know what the problem is. Remainder: please drop me a copy as well, I'm not on the list. Thomas [EMAIL PROTECTED]
Re: patch: Bug fixes
On Mon, Dec 04, 2000 at 06:43:50PM +0100, Jean-Marc Lasgouttes wrote: "Dekel" == Dekel Tsur [EMAIL PROTECTED] writes: Dekel This patch fixes few Dekel issues with RTL cursor, and also - Open all floats before Dekel spellchecking to enable spellchecking of their contents - Fix Dekel the bug where selecting with the mouse some text that ends with Dekel a closed float causes the float to open. Do we really want to open floats before spellchecking? This means that they will remain open afterwards, isn't it? I'm not sure about the answer, I just ask :) You do want to spellcheck the text in the footnotes.
Re: Some messages won't get translated
Dekel,
I'm no gettext guru. Can you explain what the two functions actually DO?
A
On Monday 04 December 2000 17:52, Dekel Tsur wrote:
On Mon, Dec 04, 2000 at 11:23:31AM +, Angus Leeming wrote:
Why not? They appear in my lyx.pot file. I guess you mean that they
aren't in yours?
Admittedly, "GUI background" etc don't appear. Will investigate.
You should use 'xcol.name = _("GUI background")' instead of using N_().
There are several places in your code that need to fixed.
Note that in some places you need to keep the N_() but put a _() when the
string is used. For example, keep the N_() in LyXRC::getDescription but
in FormPreferences::feedback you need to put
str = formatted(_(str), ...)
Re: patch: Bug fixes
Dekel Tsur [EMAIL PROTECTED] writes: | On Mon, Dec 04, 2000 at 06:43:50PM +0100, Jean-Marc Lasgouttes wrote: | "Dekel" == Dekel Tsur [EMAIL PROTECTED] writes: | | Dekel This patch fixes few | Dekel issues with RTL cursor, and also - Open all floats before | Dekel spellchecking to enable spellchecking of their contents - Fix | Dekel the bug where selecting with the mouse some text that ends with | Dekel a closed float causes the float to open. | | Do we really want to open floats before spellchecking? This means that | they will remain open afterwards, isn't it? I'm not sure about the | answer, I just ask :) | | You do want to spellcheck the text in the footnotes. by opening them. IMHO the float should only be opened if a wrongly spelt word is found inside. Lgb
Re: Test file
Dekel Tsur [EMAIL PROTECTED] writes: | On Mon, Dec 04, 2000 at 03:56:53PM +0100, Lars Gullik Bjønnes wrote: | Angus Leeming [EMAIL PROTECTED] writes: | | | This is dying in Buffer::isLatex() | | Are you sure that inlining is not playing tricks on you? | | Seems almost liek isLatex is beeing called on a buffer that has just | been deleted... | | The real problem is the following line in LyXParagraph::CopyIntoMinibuffer(): |minibuffer_inset = GetInset(pos)-Clone(*current_view-buffer()); | As current_view hasn't been initialized yet, *current_view-buffer()) is junk. | I've already mentioned this problem. | Possible solution are | 1) Change the first parameter of CopyIntoMinibuffer() from | 'BufferParams const ' to 'Buffer const '. | 2) Do not call to CopyIntoMinibuffer in LyXTabular::OldFormatRead(). I would actually prefere both... Lgb
KDE cleanup part deux
Some of the files in src/frontends/kde/dlg should be removed : cd src/frontends/kde/dlg rm copyrightdlg.C copyrightdlg.h indexdlg.C indexdlg.h paradlg.C paradlg.h paraextradlg.C paraextradlg.h printdlg.C printdlg.h parageneraldlg.C parageneraldlg.h tabcreatedlg.C tabcreatedlg.h cvs delete copyrightdlg.C copyrightdlg.h indexdlg.C indexdlg.h paradlg.C paradlg.h paraextradlg.C paraextradlg.h printdlg.C printdlg.h parageneraldlg.C parageneraldlg.h tabcreatedlg.C tabcreatedlg.h Also please apply the attached patch. It fixes various little things wrong that didn't show up until I could clean the tree properly. thanks john kdelittlefixes.diff.gz
Re: Protected Space Incompatibility Lyx 1.1.4fix3 and 1.1.5fix2
Angus Leeming [EMAIL PROTECTED] writes: Well, in general, it is impossible to be backward compatible always. By this I mean that changes to the file format cannot possibly be backward compatible. Yes, I understand that. And I am the last person to complain about a change to the better, even if it breaks backwards compatibility (Well ok, I *did* complain...). I was just puzzled by the fact that this is really the first file format problem ever that I came across, so I thought it might be a bug. There have not been many of these file format changes, however, so you've been lucky. Note, however, that lyx may move very soon to an xml file format. Yes, that makes sense (though having real latex as a file format would suit me even more, but I guess you have discussed that quite a lot). It will be possible to write a conversion script back to the old format, but that'll be the best we can do, I suspect. That's ok. If it is documented somewhere. Just the one thing about Word 97 (8): remember the file format was incompatible with Word 6 or 7? Some people really got mad about it, because it was really difficult to interoperate. Later Microsoft did provide export and import of the other format, but the PR damage was already done. Thomas [EMAIL PROTECTED]
Re: Protected Space Incompatibility Lyx 1.1.4fix3 and 1.1.5fix2
On Mon, Dec 04, 2000 at 07:49:19PM +0100, Lars Gullik Bjønnes wrote:
Thomas Steffen [EMAIL PROTECTED] writes:
| [snipped]
Only if you define what minor revisions are... I am not sure the
change from 1.1.4 to 1.1.5 is a minor revision (and please forget the
numbers). 1.1.4 to 1.1.4fix1 is a minor revision I guess.
Debian stable has 1.1.4fix3, so I guess quite some people will be bitten
by the file format changes (it happened recentely to a coworker of mine).
| So far LyX *was* backward
| compatible, at least between the releases I have used (thats 1.0.1 to
| 1.1.5 IIRC).
This is only by coincidence.
And probably not quite true either.
LyX 0.12.0 (at least) did use format 2.15.
I'd suggest an alert box if the file's lyxformat is greater than the
format recognized by LyX (currently a console ``ERROR'' message is output
if format - LYX_FORMAT 0.05).
Attached is a patch for 1.1.5fix2; would you accept one for 1.1.6?
Beware--my patch is not sufficient: in 1.1.5, if a decimal
separator other than the point is used, Buffer::readFile will believe
lyxformat==2.00; thus no warning.
| Remember the Word 97 thingy?
What about it?
Lgb
--
Yves
--- /home/stid/src/lyx-1.1.5fix2/src/buffer.C Fri Oct 13 14:25:42 2000
+++ /misc/rlin/home/zeb/src/lyx-1.1.5fix2/src/buffer.C Mon Dec 4 20:13:31 2000
@@ -1099,9 +1099,10 @@
printf(_("Warning: need lyxformat %.2f but
found %.2f\n"),
LYX_FORMAT, format);
}
- if (format - LYX_FORMAT 0.05) {
- printf(_("ERROR: need lyxformat %.2f but found
%.2f\n"),
- LYX_FORMAT, format);
+ if (format LYX_FORMAT) {
+ WriteAlert(_("Warning!"),
+ _("This document was created using
+a newer version of LyX."),
+ _("Please check for incorrect text
+or formating."));
}
bool the_end = readLyXformat2(lex, par);
// Formats = 2.13 support "\the_end" marker
Re: Test file
On Monday 04 December 2000 18:45, Lars Gullik Bjønnes wrote: Dekel Tsur [EMAIL PROTECTED] writes: | On Mon, Dec 04, 2000 at 03:56:53PM +0100, Lars Gullik Bjønnes wrote: | Angus Leeming [EMAIL PROTECTED] writes: | | This is dying in Buffer::isLatex() | | Are you sure that inlining is not playing tricks on you? | | Seems almost liek isLatex is beeing called on a buffer that has just | been deleted... | | The real problem is the following line in | LyXParagraph::CopyIntoMinibuffer(): minibuffer_inset = | GetInset(pos)-Clone(*current_view-buffer()); As current_view hasn't | been initialized yet, *current_view-buffer()) is junk. I've already | mentioned this problem. | Possible solution are | 1) Change the first parameter of CopyIntoMinibuffer() from | 'BufferParams const ' to 'Buffer const '. | 2) Do not call to CopyIntoMinibuffer in LyXTabular::OldFormatRead(). I would actually prefere both... Lgb Actually, I think that the "correct:" fix is to remove the (Buffer const ) from Inset::Clone() and not to store Buffer * in any Inset. That way, we can continue to pass a BufferParams to LyXParagraph::CopyIntoMinibuffer() and current_view dissapears from paragraph.C. Angus
Re: Protected Space Incompatibility Lyx 1.1.4fix3 and 1.1.5fix2
On Mon, Dec 04, 2000 at 06:19:08PM +, Angus Leeming wrote: [snip] Can anybody think of any other changes in format? \paragraph_spacing (special spacing for the paragraph) Angus -- Yves
Re: patch: Bug fixes
On Mon, Dec 04, 2000 at 07:32:16PM +0100, Lars Gullik Bjnnes wrote: Dekel Tsur [EMAIL PROTECTED] writes: | | You do want to spellcheck the text in the footnotes. by opening them. How many users knows that this is needed ? And how many of those will remember doing it ? IMHO the float should only be opened if a wrongly spelt word is found inside. This should be done in 1.2.0.
Re: patch: Bug fixes
Dekel Tsur [EMAIL PROTECTED] writes: | On Mon, Dec 04, 2000 at 07:32:16PM +0100, Lars Gullik Bjønnes wrote: | Dekel Tsur [EMAIL PROTECTED] writes: | | | | You do want to spellcheck the text in the footnotes. | | by opening them. | | How many users knows that this is needed ? And how many of those will | remember doing it ? I actually planned to put a question mark after that... | IMHO the float should only be opened if a wrongly spelt word is found | inside. | | This should be done in 1.2.0. Let's leave it until then. Lyx 1.1.6 will not be any worse that prev verisons in this respect. Lgb
Re: patch: Bug fixes
Dekel Tsur [EMAIL PROTECTED] writes: | Let's leave it until then. | Lyx 1.1.6 will not be any worse that prev verisons in this respect. | | But openning the floats is better than the current behavior. Is it really? Perhaps it is... but I don't want anything that can potentially delay 1.1.6. Let's get 1.1.6 out, begin 1.2.0cvs, "fixes" like this can be backported to 1.1.6fixX. Lgb
Re: patch: Bug fixes
On Mon, Dec 04, 2000 at 10:02:25PM +0100, Lars Gullik Bjnnes wrote: Dekel Tsur [EMAIL PROTECTED] writes: | Let's leave it until then. | Lyx 1.1.6 will not be any worse that prev verisons in this respect. | | But openning the floats is better than the current behavior. Is it really? Perhaps it is... but I don't want anything that can potentially delay 1.1.6. Let's get 1.1.6 out, begin 1.2.0cvs, "fixes" like this can be backported to 1.1.6fixX. How is this going to delay the code ? This fix is just two lines in spellchecker.C.
Re: patch: Bug fixes
Dekel Tsur [EMAIL PROTECTED] writes: | Let's get 1.1.6 out, begin 1.2.0cvs, "fixes" like this can be | backported to 1.1.6fixX. | | How is this going to delay the code ? All additional patches delay code... We have seen that patches thought to be trivial has created bugs, and created brown-paper-bag situations. | This fix is just two lines in spellchecker.C. I don't care. Especially since the first thing in 1.2.0cvs would be to remove those two lines again and fix the bug properly. Lgb
CVS compile failure
log attached Making all in intl make[1]: Entering directory `/usr/local/garst/lyx-devel/intl' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/local/garst/lyx-devel/intl' Making all in po make[1]: Entering directory `/usr/local/garst/lyx-devel/po' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/local/garst/lyx-devel/po' Making all in sigc++ make[1]: Entering directory `/usr/local/garst/lyx-devel/sigc++' make all-recursive make[2]: Entering directory `/usr/local/garst/lyx-devel/sigc++' Making all in macros make[3]: Entering directory `/usr/local/garst/lyx-devel/sigc++/macros' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/usr/local/garst/lyx-devel/sigc++/macros' make[3]: Entering directory `/usr/local/garst/lyx-devel/sigc++' make[3]: Leaving directory `/usr/local/garst/lyx-devel/sigc++' make[2]: Leaving directory `/usr/local/garst/lyx-devel/sigc++' make[1]: Leaving directory `/usr/local/garst/lyx-devel/sigc++' Making all in boost make[1]: Entering directory `/usr/local/garst/lyx-devel/boost' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/local/garst/lyx-devel/boost' Making all in src make[1]: Entering directory `/usr/local/garst/lyx-devel/src' make all-recursive make[2]: Entering directory `/usr/local/garst/lyx-devel/src' Making all in mathed make[3]: Entering directory `/usr/local/garst/lyx-devel/src/mathed' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/usr/local/garst/lyx-devel/src/mathed' Making all in insets make[3]: Entering directory `/usr/local/garst/lyx-devel/src/insets' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/usr/local/garst/lyx-devel/src/insets' Making all in graphics make[3]: Entering directory `/usr/local/garst/lyx-devel/src/graphics' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/usr/local/garst/lyx-devel/src/graphics' Making all in support make[3]: Entering directory `/usr/local/garst/lyx-devel/src/support' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/usr/local/garst/lyx-devel/src/support' Making all in frontends make[3]: Entering directory `/usr/local/garst/lyx-devel/src/frontends' Making all in support make[4]: Entering directory `/usr/local/garst/lyx-devel/src/frontends/support' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/usr/local/garst/lyx-devel/src/frontends/support' Making all in xforms make[4]: Entering directory `/usr/local/garst/lyx-devel/src/frontends/xforms' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/usr/local/garst/lyx-devel/src/frontends/xforms' make[4]: Entering directory `/usr/local/garst/lyx-devel/src/frontends' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/usr/local/garst/lyx-devel/src/frontends' make[3]: Leaving directory `/usr/local/garst/lyx-devel/src/frontends' make[3]: Entering directory `/usr/local/garst/lyx-devel/src' /bin/sh ../libtool --mode=link g++ -O -fno-rtti -fno-exceptions -W -Wall -o lyx BufferView.o BufferView2.o BufferView_pimpl.o Bullet.o Chktex.o ColorHandler.o CutAndPaste.o DepTable.o FloatList.o FontInfo.o FontLoader.o LColor.o LaTeX.o LaTeXFeatures.o LaTeXLog.o LyXAction.o LyXSendto.o LyXView.o MenuBackend.o Painter.o PainterBase.o Sectioning.o Spacing.o TextCache.o Timeout.o ToolbarDefaults.o UpdateInset.o Variables.o WorkArea.o bmtable.o buffer.o bufferlist.o bufferparams.o bufferview_funcs.o chset.o combox.o converter.o counters.o credits.o credits_form.o debug.o encoding.o exporter.o filedlg.o font.o form1.o gettext.o importer.o intl.o kbmap.o kbsequence.o language.o lastfiles.o layout.o layout_forms.o log_form.o lyx.o lyx_cb.o lyx_gui.o lyx_gui_misc.o lyx_main.o lyx_sty.o lyxcursor.o lyxfont.o lyxfr0.o lyxfr1.o lyxfunc.o lyxlex.o lyxlex_pimpl.o lyxlookup.o lyxrc.o lyxrow.o lyxserver.o lyxvc.o main.o minibuffer.o paragraph.o print_form.o screen.o sp_form.o spellchecker.o tabular.o tex-accent.o tex-strings.o texrow.o text.o text2.o tracer.o trans.o trans_mgr.o undo.o vc-backend.o vspace.o mathed/libmathed.la insets/libinsets.la graphics/libgraphics.la frontends/libfrontends.la ../src/frontends/xforms/libxforms.la frontends/libfrontends.la frontends/support/libfrontendsupport.la support/libsupport.la ../sigc++/libsigc.la -lforms `../sigc++/sigc-config --libs-names | sed -e 's/-lsigc//'` -lSM -lICE -liberty -lc -lm -L/usr/X11R6/lib -lX11 g++ -O -fno-rtti -fno-exceptions -W -Wall -o lyx BufferView.o BufferView2.o BufferView_pimpl.o Bullet.o Chktex.o ColorHandler.o CutAndPaste.o DepTable.o FloatList.o FontInfo.o FontLoader.o LColor.o LaTeX.o LaTeXFeatures.o LaTeXLog.o LyXAction.o LyXSendto.o LyXView.o MenuBackend.o Painter.o PainterBase.o Sectioning.o Spacing.o TextCache.o Timeout.o ToolbarDefaults.o UpdateInset.o Variables.o WorkArea.o bmtable.o buffer.o bufferlist.o bufferparams.o bufferview_funcs.o chset.o combox.o converter.o
Re: CVS compile failure
Why isn't -lXpm on your link line? Didn't you get a warning when running configure? Lgb
Re: ERT inset
Allan Rae [EMAIL PROTECTED] writes: | Isn't the ERT inset supposed to be strictly raw LaTeX so should always be | in TeX mode rather than allowing the user to set a standard paragraph | style or any other style for that matter? Yes. Should be fixed to TeX. Lgb
Test file
Here's a test file created in lyx-1.1.5fix1-1
that makes the CVS LyX core dump. Apparently
related to the table format change.
Remove the ref from the table and the crash
goes away. This is the only thing keeping
me from upgrading.
Yst. Martin
--
Martin Vermeer [EMAIL PROTECTED]
Helsinki University of Technology
Department of Surveying
P.O. Box 1200, FIN-02015 HUT, Finland
:wq
#LyX 1.1 created this file. For more info see http://www.lyx.org/
\lyxformat 2.16
\textclass article
\language default
\inputencoding latin1
\fontscheme default
\graphics default
\paperfontsize default
\spacing single
\papersize Default
\paperpackage a4
\use_geometry 0
\use_amsmath 0
\paperorientation portrait
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
\papersides 1
\paperpagestyle default
\layout Standard
\added_space_top 0.3cm \added_space_bottom 0.3cm \align center \LyXTable
multicol5
1 1 0 0 -1 -1 -1 -1
1 1 0 0
8 1 1 "" ""
0 8 1 0 0 0 0 "" ""
Einstein (eq.
\begin_inset LatexCommand \ref{eq:Einstein}
\end_inset
) says:
\layout Standard
\begin_inset Formula \begin{equation}
\label{eq:Einstein}
E=mc^{2}
\end{equation}
\end_inset
\the_end
Re: Core dump when setting preferences with Lyx 1.1.6pre2
Errr Let's get this straight. Before you Reconfigured, you couldn't open Edit->Preferences. After you reconfigured you could. But isn't LyX reconfigured as part of thr installation process Don't understand. Angus On Sunday 03 December 2000 02:01, Ben Cazzolato wrote: > Mon, 27 Nov 2000 > > Hi Guys > I am starting to use the pre-release of Lyx 1.1.6pre2 (downloaded RPM from > ftp://ftp.sylvan.com/pub/lyx/) and I can get Lyx to core dump every time. > > I tried Edit->Preferences immediately after upgrading from 1.5.2 (without > opening up Lyx first and reconfiguring) and it would crash every time. > > lyx: SIGSEGV signal caught > Sorry, you have found a bug in LyX. If possible, please read 'Known bugs' > under the Help menu and then send us a full bug report. Thanks! > Bye. > Aborted (core dumped) > > > I then did as Angus suggested, ie > > > 1. Open up LyX and Edit->Reconfigure. > > 2. Close LyX. > > 3. Open up LyX again. > > > > Many of these warnings will dissapear. > > > > Your lyxrc is soon to become redundant. Open up Edit->Preferences, make > > some spurious change (to activate the Save button) and Save the change. > > You''ll now have a preferences file in your .lyx directory. lycrc will > > never be read again; instead preferences will be used instead. In future, > > use the Edit->Preferences popup to make any changes to LyX's behaviour. > > And all seems to be well. > > Maybe there needs to be some check for people like myself who will do > things without reading the instructions. > > Ben
Re: Core dump when setting preferences with Lyx 1.1.6pre2
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: Angus> Errr Let's get this straight. Before you Reconfigured, you Angus> couldn't open Edit-> Preferences. After you reconfigured you could. Angus> But isn't LyX reconfigured as part of thr installation Angus> process When installing, the system lyxrc.default is changed. What Reconfigure does is to change the user lyxrc.default. JMarc
Re: Some messages won't get translated
Why not? They appear in my lyx.pot file. I guess you mean that they aren't in yours? Admittedly, "GUI background" etc don't appear. Will investigate. Angus On Friday 01 December 2000 18:07, Pauli Virtanen wrote: > This applies on LyX CVS head branch of Wed Nov 29 > > For your information: The following parts of LyX won't get > translated, even if the translations exist. > > - The "tooltips" in the bottom of the preferences popup. > > - The Close and Cancel buttons in the popups "Preferences", > "Document properties", "Paragraph properties", "Citation", > "Cross reference" and "Table of contents". > The translated text doesn't appear, but the shortcut works. > > - The "GUI background/text/selection/pointer" items in the > "LyX objects" list in the preferences popup in pane > "Look & Feel"/"Colors" > > - The "Sys UI" and "User UI" buttons in the UI file browse > popup from the preferences. > > - The "Sys Bind" and "User Bind" buttons in the bind file browse > popup from the preferences. > > > Pauli Virtanen
Re: Core dump when setting preferences with Lyx 1.1.6pre2
Well how about adding a flag to the system lyxrc.defaults. \user_reconfigure yes/no ??? Angus On Monday 04 December 2000 11:11, Jean-Marc Lasgouttes wrote: > > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: > > Angus> Errr Let's get this straight. Before you Reconfigured, you > Angus> couldn't open > Edit-> Preferences. After you reconfigured you could. > > Angus> But isn't LyX reconfigured as part of thr installation > Angus> process > > When installing, the system lyxrc.default is changed. What Reconfigure > does is to change the user lyxrc.default. > > JMarc
Re: Core dump when setting preferences with Lyx 1.1.6pre2
I guess that what is needed is a permanent entry in the system lyxrc.defaults \user_reconfigure 1.1.6 yes that is overridden by the corresponding entry in the user lyxrc.defaults \user_reconfigure 1.1.6 no Angus On Monday 04 December 2000 11:26, Angus Leeming wrote: > Well how about adding a flag to the system lyxrc.defaults. > > \user_reconfigure yes/no > > ??? > > Angus > > On Monday 04 December 2000 11:11, Jean-Marc Lasgouttes wrote: > > > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: > > > > Angus> Errr Let's get this straight. Before you Reconfigured, you > > Angus> couldn't open > > Edit-> Preferences. After you reconfigured you could. > > > > Angus> But isn't LyX reconfigured as part of thr installation > > Angus> process > > > > When installing, the system lyxrc.default is changed. What Reconfigure > > does is to change the user lyxrc.default. > > > > JMarc
Re: Core dump when setting preferences with Lyx 1.1.6pre2
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: Angus> I guess that what is needed is a permanent entry in the system Angus> lyxrc.defaults \user_reconfigure 1.1.6 yes Angus> that is overridden by the corresponding entry in the user Angus> lyxrc.defaults Angus> \user_reconfigure 1.1.6 no Or rather a way to see when configure was run for the last time, so that it can be automatically re-run if necessary (\last_configure_version 1.1.6) Anyway, no crash should happen! JMarc
Re: Installing Problems
On Fri, 1 Dec 2000, Amir Karger wrote: > On Fri, Dec 01, 2000 at 12:43:02PM +, John Levon wrote: > > > > I imagine you mean xforms. In fact I think this might be a problem that > > was reported ages ago, around when I started reading lyx-devel. I had the > > hypothesis at the time that this was Xpm routines causing xforms to crash, > > because it couldn't allocate the colours. This is because the lyx xpm > > files don't have "m" (mono) options for when the colour can't be > > allocated, and xforms doesn't seem to like the Xpm routines failing like > > this. > > > > I really should add these tags to the icon files, but it is a boring job > > (I can't find a tool that adds them automatically :() > > What exactly do you need to do? > > I only ask because Perl can do *anything* automatically. (Well, most things. > Usually.) > > -Amir > Change the things like : " c None", ". c #", "X c #7B7B", "o c gray70" to : " c None", ". c # m black", "X c #7B7B m black", "o c gray70 m black" or similar. It can't be 100% automatic because it needs to be seen how it looks in mono (though the bw versions, where applicable, can be a guide). My perl is far too shallow to have a go at this... thanks john
Re: Core dump when setting preferences with Lyx 1.1.6pre2
On Monday 04 December 2000 11:41, Jean-Marc Lasgouttes wrote: > > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: > > Angus> I guess that what is needed is a permanent entry in the system > Angus> lyxrc.defaults \user_reconfigure 1.1.6 yes > > Angus> that is overridden by the corresponding entry in the user > Angus> lyxrc.defaults > > Angus>\user_reconfigure 1.1.6 no > > Or rather a way to see when configure was run for the last time, so > that it can be automatically re-run if necessary > (\last_configure_version 1.1.6) Good. > Anyway, no crash should happen! Well, I can''t reproduce this: lyx-1.1.4, Reconfigure, Close. mv ~/.lyx/preferences ~/.lyx/preferences_safe lyx-1.1.6cvs, Edit->Preferences No crash. Don't see how we can find the root cause of the problem, therefore. Your suggested work around seems like the best way forward. Angus
Re: Key-binding documentation dilemma
Angus Leeming <[EMAIL PROTECTED]> writes: | Gentlemen, | | I've written the inset proposed by Jean-Marc. Currently, it's a little | cumbersome to use: | | Eg, type in the minibuffer: | | shortcut-insert line-end But this is not what we really want... we want an inset that shows the output of a lyx variable. the command to get the would f.ex. be: describe-variable default-language -> "norsk" describe-function-binding line-end -> "C-e" describe-binding C-x C-s -> "buffer-save" What we want is a inset that encapsulates this. Lgb
Re: Key-binding documentation dilemma
Allan Rae <[EMAIL PROTECTED]> writes: | On Fri, 1 Dec 2000, Angus Leeming wrote: | | > Gentlemen, | > | > I've written the inset proposed by Jean-Marc. Currently, it's a little | > cumbersome to use: | > | > Eg, type in the minibuffer: | > | > shortcut-insert line-end | > | > And a little button appears in the text containing the immortal [C-e]. | > | > It isn't quite there yet (no Read(), Write(), Latex() functions, so you can't | > save it and can't export it to latex, but not bad for an hour's hacking I | > feel. | | Bundle it with the Note inset and submit it after 1.1.6. | | Read, Write and LaTeX functions should be pretty easy BTW. I really do not want it done this way... Lgb
PATCH: xform_macros.h and FormPrefernces::Colors
Attached is a patch that removes xform_macros.h. It also finishes off the Colors tab. I hope. Angus patch.diff.bz2
Re: Bug tracker
On Sun, 3 Dec 2000, Allan Rae wrote: > On Fri, 1 Dec 2000, John Levon wrote: > > > Me & Angus have started up a prototype bug tracker for lyx at : > > > > http://sourceforge.net/bugs/?group_id=15212 > > We've certainly discussed this often enough but nobody has had the time or > inclination to do anything about it. Thanks. What's involved in adding > developers to the list of people who can do admin stuff? It'd be nice if > we could make this official and have all the core developers able to > work with it. > To be added as an admin : 1) create a sourceforge account for yourself. https://sourceforge.net/account/register.php 2) mail me or angus (or any other admin of the project), giving the username, and you will be added as admin. I'm none too sure about opening this particular database up "officially", simply because the sourceforge facilities are a little, um, basic. For example, there's no way to add a field indicating LyX version number. Really nice would be a proper bugzilla or similar installed somewhere. > Can you change the CVS link to go to > http://www.devel.lyx.org/cvs.php3 > > instead? > nope :(. I've just turned it off for now. > There are a few other bugs JMarc had entries for in his announcements for > 1.1.5fix2 that you might like to add also if they haven't already been > fixed. Thanks for the pointer, I'll look these up. thanks john -- "An AMM performance has no beginning or ending. Sounds outside the performance are distinguished from it only by individual sensibility." - Victor Schonfield
Re: Key-binding documentation dilemma - what I will try
Lior Silberman <[EMAIL PROTECTED]> writes: | With regards the UserGuide, however, we must bear in mind that having a | list of keybindings indexed by the key combinations is not useful. Why is this so? | I will admit here that all of the above reflects the personal opinions of | a cua.bind user. That shows. Lgb
Re: Bug tracker
John Levon <[EMAIL PROTECTED]> writes: | Me & Angus have started up a prototype bug tracker for lyx at : | | http://sourceforge.net/bugs/?group_id=15212 | | We've both found it quite handy (I know what still needs working on !), so | if anyone else can make use of it, just ask angus or me for an account and | we'll add you as admin. Can bug reports be entered by sending mail to [EMAIL PROTECTED]? (after I setup the redirection of course) Lgb
Re: Installing Problems
John Levon <[EMAIL PROTECTED]> writes: | Change the things like : | | " c None", | ". c #", | "X c #7B7B", | "o c gray70" | | to : | | " c None", | ". c # m black", | "X c #7B7B m black", | "o c gray70 m black" | | or similar. It can't be 100% automatic because it needs to be seen how it | looks in mono (though the bw versions, where applicable, can be a | guide). My perl is far too shallow to have a go at this... Have you verified that XForms still can use the icons after that change? Lgb
Re: Core dump when setting preferences with Lyx 1.1.6pre2
Angus Leeming <[EMAIL PROTECTED]> writes: | Errr | | Let's get this straight. Before you Reconfigured, you couldn't open | Edit->Preferences. After you reconfigured you could. Why does this make a difference? It really shouldn't. Lgb
Re: Bug tracker
On 4 Dec 2000, Lars Gullik Bjønnes wrote: > John Levon <[EMAIL PROTECTED]> writes: > > | Me & Angus have started up a prototype bug tracker for lyx at : > | > | http://sourceforge.net/bugs/?group_id=15212 > | > | We've both found it quite handy (I know what still needs working on !), so > | if anyone else can make use of it, just ask angus or me for an account and > | we'll add you as admin. > > Can bug reports be entered by sending mail to [EMAIL PROTECTED]? (after I > setup the redirection of course) > > Lgb > Yep, I was hoping you might say that ;) Currently everything goes to me, it's trivial to change. thanks john -- "An AMM performance has no beginning or ending. Sounds outside the performance are distinguished from it only by individual sensibility." - Victor Schonfield
Re: Installing Problems
On 4 Dec 2000, Lars Gullik Bjønnes wrote: > John Levon <[EMAIL PROTECTED]> writes: > > > | Change the things like : > | > | " c None", > | ". c #", > | "X c #7B7B", > | "o c gray70" > | > | to : > | > | " c None", > | ". c # m black", > | "X c #7B7B m black", > | "o c gray70 m black" > | > | or similar. It can't be 100% automatic because it needs to be seen how it > | looks in mono (though the bw versions, where applicable, can be a > | guide). My perl is far too shallow to have a go at this... > > Have you verified that XForms still can use the icons after that > change? > > Lgb AFAIK Xforms just uses Xpm library, so the answer is yes. Of course if I get round to this one, I'll test it :) thanks john -- "An AMM performance has no beginning or ending. Sounds outside the performance are distinguished from it only by individual sensibility." - Victor Schonfield
Re: Core dump when setting preferences with Lyx 1.1.6pre2
Angus Leeming <[EMAIL PROTECTED]> writes: | > Anyway, no crash should happen! | | Well, I can''t reproduce this: | | lyx-1.1.4, Reconfigure, Close. | mv ~/.lyx/preferences ~/.lyx/preferences_safe | lyx-1.1.6cvs, Edit->Preferences | | No crash. Don't see how we can find the root cause of the problem, therefore. | Your suggested work around seems like the best way forward. I don't really like to use work arounds for problems we don't understand. The best way forward is to find out _why_ lyx craches and fix that reason or the wrong assumtions in the code. Everything else will just at bloat and complexity. Lgb
Re: menu-open problem in all bind files
Allan Rae <[EMAIL PROTECTED]> writes: | 4. As above but do a case insensitive search (IIRC STL provides such an | option) No it does not, but we provide it in lstrings.h Lgb
[PATCH] two 1.1.6 bug fixes
The attached patch fixes the two bugs :
1) figures wouldn't work if pspell was enabled. This bug is a direct
result of not having functions in their proper files ;)
2) Fix most of the cases of the gs hangs with a workaround. I have
verified this on 0.88 and 0.89. The remaining cases involve popup menus,
where it seems events are being discarded, and I think this will require
an xforms release to fix totally.
This workaround is actually not any uglier than what we had before ...
thanks
john
--
"An AMM performance has no beginning or ending. Sounds outside the performance
are distinguished from it only by individual sensibility."
- Victor Schonfield
? lib/examples/14538vFW0yy
? lib/examples/145408rEbRG
? lib/examples/14610igQICW
Index: ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/ChangeLog,v
retrieving revision 1.709
diff -u -p -r1.709 ChangeLog
--- ChangeLog 2000/12/04 09:15:50 1.709
+++ ChangeLog 2000/12/04 11:44:48
@@ -1,3 +1,9 @@
+2000-12-04 John Levon <[EMAIL PROTECTED]>
+
+ * src/spellchecker.C: fix figures with pspell enabled
+
+ * src/insets/figinset.C: workaround for gs hang xforms bug
+
2000-11-30 Dekel Tsur <[EMAIL PROTECTED]>
* Several files: Allow compilation when the compiler doesn't
Index: src/spellchecker.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/spellchecker.C,v
retrieving revision 1.41
diff -u -p -r1.41 spellchecker.C
--- src/spellchecker.C 2000/11/28 06:46:05 1.41
+++ src/spellchecker.C 2000/12/04 11:44:48
@@ -65,12 +65,8 @@
#include "encoding.h"
#include "support/lstrings.h"
-//#define USE_PSPELL 1
-
#ifdef USE_PSPELL
-
-#include
-
+# include
#endif
using std::reverse;
@@ -110,10 +106,8 @@ PspellManager * sc;
FD_form_spell_options *fd_form_spell_options = 0;
FD_form_spell_check *fd_form_spell_check = 0;
-//void sigchldhandler(int sig);
void sigchldhandler(pid_t pid, int *status);
-//extern void sigchldchecker(int sig);
extern void sigchldchecker(pid_t pid, int *status);
#ifndef USE_PSPELL
@@ -628,7 +622,7 @@ void sc_clean_up_after_error()
-// Send word to ispell and get reply
+// Send word to pspell and get reply
static
isp_result * sc_check_word(string const & word)
{
@@ -965,10 +959,8 @@ bool RunSpellChecker(BufferView * bv)
return true;
}
}
-
-
-#ifndef USE_PSPELL
+#warning should go somewhere more sensible
void sigchldhandler(pid_t pid, int * status)
{
if (isp_pid > 0)
@@ -980,12 +972,3 @@ void sigchldhandler(pid_t pid, int * sta
}
sigchldchecker(pid, status);
}
-
-#else
-
-void sigchldhandler(pid_t, int *)
-{
- // do nothing
-}
-
-#endif
Index: src/insets/figinset.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/insets/figinset.C,v
retrieving revision 1.93
diff -u -p -r1.93 figinset.C
--- src/insets/figinset.C 2000/11/28 06:46:06 1.93
+++ src/insets/figinset.C 2000/12/04 11:44:52
@@ -167,10 +167,14 @@ void kill_gs(int pid, int sig)
}
-extern "C" // static
-int GhostscriptMsg(FL_OBJECT *, Window, int, int,
- XEvent * ev, void *)
+extern "C" {
+static
+int GhostscriptMsg(XEvent * ev, void *)
{
+ // bin all events not of interest
+ if (ev->type != ClientMessage)
+ return FL_PREEMPT;
+
XClientMessageEvent * e = reinterpret_cast(ev);
if (lyxerr.debugging()) {
@@ -297,7 +301,8 @@ int GhostscriptMsg(FL_OBJECT *, Window,
}
break;
}
- return 0;
+ return FL_PREEMPT;
+}
}
@@ -378,6 +383,9 @@ void AllocGrays(int num)
}
+// xforms doesn't define this
+extern "C" FL_APPEVENT_CB fl_set_preemptive_callback(Window, FL_APPEVENT_CB, void *);
+
static
void InitFigures()
{
@@ -389,9 +397,10 @@ void InitFigures()
// first get visual
gs_color = false;
if (lyxrc.use_gui) {
- fl_add_canvas_handler(figinset_canvas, ClientMessage,
- GhostscriptMsg,
- current_view->owner()->getForm());
+ /* we want to capture every event, in order to work around an
+* xforms bug.
+*/
+ fl_set_preemptive_callback(fl_get_canvas_id(figinset_canvas),
+GhostscriptMsg, 0);
local_gc_copy = createGC();
@@ -430,9 +439,6 @@ void DoneFigures()
figures.clear();
lyxerr.debug() << "Unregistering figures..." << endl;
-
- fl_remove_canvas_handler(figinset_canvas, ClientMessage,
-
Re: Key-binding documentation dilemma
Ummm... Aren't you wanting three different insets for your three different types of info. My quick (and fully working) hack does exactly what your describe-function-binding line-end -> "C-e" would do. I guess that you could use the one inset, but don't see why. Angus On Monday 04 December 2000 12:33, Lars Gullik Bjønnes wrote: > Angus Leeming <[EMAIL PROTECTED]> writes: > | Gentlemen, > | > | I've written the inset proposed by Jean-Marc. Currently, it's a little > | cumbersome to use: > | > | Eg, type in the minibuffer: > | > | shortcut-insert line-end > > But this is not what we really want... we want an inset that shows the > output of a lyx variable. > > the command to get the would f.ex. be: > > describe-variable default-language -> "norsk" > describe-function-binding line-end -> "C-e" > describe-binding C-x C-s -> "buffer-save" > > What we want is a inset that encapsulates this. > > Lgb
Re: try: M-f v followed by clicking in workarea
Allan Rae <[EMAIL PROTECTED]> writes: | LyXAction::funcHasFlag: No info about kb_action: 8 | A truly unknown func! Care to investigate? Why is anything passed to LyXAction/LyXFunc in this case? Lgb
Re: View->PDF (pdflatex) vs View->Update->PDF (pdflatex)
Allan Rae <[EMAIL PROTECTED]> writes: | On Sun, 3 Dec 2000, Dekel Tsur wrote: | | > On Sun, Dec 03, 2000 at 05:23:18PM +1000, Allan Rae wrote: | > > | > > Viewing requires one run of pdflatex. Updating runs pdflatex 6 times | > > using the exact same file -- no changes in between runs. | > | > This doesn't make sense as preview = update + run viewer. | > However, if you consistently getting this behavior, make your files | > available for download so we can check this. | | I tried a few more times and got 6 runs of pdflatex with either | update or view. It would appear that I'd reported this "bug" a little too | early. | | I've yet to run pdflatex by hand to find out why LyX wants to run pdflatex | 6 times on my file. It does contain one reference so I do expect 2 or 3 | runs but 6 seems like something is wrong. Most likely some log messages that triggers reruns. Have you looked at the log file? do all your references have corresponding labels? Lgb
Re: Key-binding documentation dilemma
Angus Leeming <[EMAIL PROTECTED]> writes: | Ummm... | | Aren't you wanting three different insets for your three different types of | info. My quick (and fully working) hack does exactly what your | | describe-function-binding line-end -> "C-e" | | would do. I guess that you could use the one inset, but don't see | why. Why have three identical insets? And insets have no business poking around in the bindings list, that is the task of lyxfuncs. We can easily also have lyxfunc like "today" instead of using ert... "show-variable author" Why go for the specific implementation when a generic implementation will be just as easy _and_ be a lot more powerful. Lgb
Re: Bug tracker
On 4 Dec 2000, Lars Gullik Bjønnes wrote: > I'd be happy to have a bugzilla at baywatch.lyx.org. > > Just tell me what we need. > > Lgb I'm afraid installation looks non-trivial :( In terms of supporting packages, bugzilla (http://www.mozilla.org/projects/bugzilla/) needs an MySQL installation, plus the supporting Perl modules. I notice you only have postgre on baywatch currently. Or possibly GNATS (http://sources.redhat.com/gnats/) might be a better choice. It certainly looks simpler to install, and doesn't need anything other than emacs (!) as support. john -- "An AMM performance has no beginning or ending. Sounds outside the performance are distinguished from it only by individual sensibility." - Victor Schonfield
Re: try: M-f v followed by clicking in workarea
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: Lars> Allan Rae <[EMAIL PROTECTED]> writes: | Lars> LyXAction::funcHasFlag: No info about kb_action: 8 | A truly Lars> unknown func! Lars> Care to investigate? Lars> Why is anything passed to LyXAction/LyXFunc in this case? I'd say the cursor is on a submenu, which number is the default number given by xforms (version control is the heighth entry). So when the menu times out, xforms returns 8 and we do not know what to do with it. I'd say it's mostly harmless, but I do not have a simple fix. How come there is no lyxfunc with number 8 (it is supposed to be LFUN_MENUSENDTO)? JMarc
Re: Key-binding documentation dilemma
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: | Yes, that's what I had in mind originally. And lyxfuncs allowed for | this inset should be marked explicitely in LyXAction. Hmmm... rather mark all functions that outputs something... | So, would you be ready to accept that in 1.1.6? I would hope to avoid that. | 1.1.6fix1? That would be your call. | Another question: do you think we should have a 1.1.5fix3? Your call. But I don't see any great demand. Lgb
Re: Key-binding documentation dilemma
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: Lars> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: | Lars> Yes, that's what I had in mind originally. And lyxfuncs allowed Lars> for | this inset should be marked explicitely in LyXAction. Lars> Hmmm... rather mark all functions that outputs something... No, "output something and do not have any side effect". Lars> | So, would you be ready to accept that in 1.1.6? Lars> I would hope to avoid that. When do you expect 1.1.6 will be out? Lars> | 1.1.6fix1? Lars> That would be your call. OK. Lars> | Another question: do you think we should have a 1.1.5fix3? Lars> Your call. But I don't see any great demand. It would be nice to have a reasonably stable 1.1.5 version when 1.1.6 comes out. Of course, not having it would be a nice incentive for people to upgrade to 1.1.6 :) Anyway, we should probably be prepared to have a 1.1.6fix1 one week after 1.1.6 (I doubt there will not be serious problems). JMarc
