Angus Leeming <[EMAIL PROTECTED]> writes:
| path_prefix is essentially a Windows thing. Windows has a PATH environment
| variable but most native Windows apps don't use it; they use the registry
| instead. LyX, however, knows nothing about the registry, so we give our users
a
| localized way of t
"Bo Peng" <[EMAIL PROTECTED]> writes:
| > If we are going for this it will be a major new feature (IMHO) and
| > should then wait for 1.7.
|
| And it needs cleanup of classes like buffer. Anyway, the real
| implementation is *easy* so this feature is not that far away from us.
This feature has a
Angus Leeming wrote:
> It's not very expensive and it'll make your life easy.
OK, I really just had a quick look. Perhaps it's just the right thing.
> The general thrust of your idea is good. Go for it!
No chance ATM, really. Sorry about that.
Jürgen
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
> PS: I also looked at FileMonitor, but I guess monitoring bib files is a bit
> overkill.
It's not very expensive and it'll make your life easy.
The general thrust of your idea is good. Go for it!
Angus
Juergen Spitzmueller wrote:
> - make InsetBibtex::getFiles a map (or a vector/pair, dunno) instead of a
> vector which stores not only the file name, but also information about the
> state of the bibfiles. In this case, I think even the timestamp of the file
> would suffice. If not, I seem to remem
Juergen Spitzmueller wrote:
> This optimization is no more.
I don't have time to work on it in the foreseeable timeframe, but how about
the following idea, that strikes me much better than the 1.3 optimization
hack?
- make fillWithBibKeys a bool.
- make InsetBibtex::getFiles a map (or a vector/
> I think it should work if you packaged all your
> LyX associated files into a tar.gz which would
> unpack into a path without spaces,
The bst/space patch has been submitted. If this patch is working, you
can open and work with a .lyx file directly, along with .cls, .bst,
.bib, .eps, .cls, .layou
> If you want to wrap c++ to interface with python, I suggest boost::python.
> It's easy once you get over the learning curve, and we're already using
> boost.
That is true, but I only know SWIG. :-) While SWIG can wrap all the
classes automatically, boost::python need to write things manually
(an
Bo Peng wrote:
>> If we are going for this it will be a major new feature (IMHO) and
>> should then wait for 1.7.
>
> And it needs cleanup of classes like buffer. Anyway, the real
> implementation is *easy* so this feature is not that far away from us.
>
> Bo
If you want to wrap c++ to interfac
When I read the following email from lyx-user, I feel the urge to
complete my local .cls/.layout patch. :-) Lars, I am waiting for your
comment about my pre-Patch.
Bo
"I know perfectly that, if I am getting a zip file with .lyx, .cls,
and .layout, I am supposed to
1. create localtexmf, modi
> [ignore 1000-word instruction]
> It is hard to understand why you don't do this the
> easy way, it makes me wonder about
I know perfectly that, if I am getting a zip file with .lyx, .cls, and
.layout, I am supposed to
1. create localtexmf, modify TEXINPUTS environment variable.
2. or put
On Thu, Mar 30, 2006 at 08:59:37PM +, Angus Leeming wrote:
> Enrico Forestieri <[EMAIL PROTECTED]> writes:
> > It is used by LyX to set the PATH prefix. In *nix it should be omitted,
> > as everything needed should already be in the PATH. In the native win32
> > LyX it will be set by the instal
On Thu, Mar 30, 2006 at 10:21:53PM +0200, Georg Baum wrote:
> Am Mittwoch, 29. März 2006 20:49 schrieb Enrico Forestieri:
>
> > I have reorganized things in this way:
> > 1) The kind of path style to be written into .tex files is only
> > decided by the configure script which checks what the co
Thank you for the suggestion. Unfortunately, that doesn't seem to be
the problem. I removed the LyX and LyX-1.4 directories and restarted
LyX, but it still crashed when I tried to open Preferences.
On Mar 30, 2006, at 12:32 PM, Bennett Helm wrote:
On Mar 30, 2006, at 12:07 PM, Darren Oh wro
When I read the following email from lyx-user, I feel the urge to
complete my local .cls/.layout patch. :-) Lars, I am waiting for your
comment about my pre-Patch.
Bo
To install a new class, place the .cls file in an appropriate directory
(for instance, in a subdirectory $localtexmf$/tex/latex/s
On Thu, Mar 30, 2006 at 05:44:17PM +0200, Abdelrazak Younes wrote:
> I am using TortoiseSVN which has a very good GUI that can show visual
> comparison between revisions or even 3-way comparisons. With this GUI
> you can reject a change, revert to an older version, etc. I definitely
> prefer th
On Thu, Mar 30, 2006 at 05:01:52PM +0200, Jean-Marc Lasgouttes wrote:
> > "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>
> Abdelrazak> Message to the main lyx developers:
>
> Abdelrazak> IMHO, if you want to encourage new contributions, you
> Abdelrazak> should relax a bit th
On Thu, Mar 30, 2006 at 06:39:39PM +0200, Jean-Marc Lasgouttes wrote:
> I think this cygwin-without-cygwin stuff is becoming stranger and
> stranger.
cygwin-without-cygwin? what's that? ;-)
--
Enrico
> > I will do that, as well as the \Format+spacing later. Please apply the
> > current patch first.
>
> I'll do that if you submit a log entry.
2006-03-30 Bo Peng <[EMAIL PROTECTED]>
* configure.py: Major clean up.
> Note also that the pdflatex format changes are missing.
Which one?
On Thu, Mar 30, 2006 at 05:33:31PM +0200, Georg Baum wrote:
> I did not yet have time to comment on Enricos patch, I just had a quick look
> and the cygwin ifdefs he introduced in frontends/qt2/FileDialog.C don't
> seem right. If they are really needed (which I doubt currently, but that
> may chan
> Setting it in the installer is a kludge. The correct place to set this thing
> is
> in the configure script so that it can be updated as you install software. We
> couldn't do that before now because shell scripts have "limited" support for
> interogation of the registry ;-)
This is part of the
Enrico Forestieri <[EMAIL PROTECTED]> writes:
> It is used by LyX to set the PATH prefix. In *nix it should be omitted,
> as everything needed should already be in the PATH. In the native win32
> LyX it will be set by the installer, so also in this case it is probably
> not needed. This leaves cygw
Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
>
> Georg Baum <[EMAIL PROTECTED]> writes:
>
> | Am Donnerstag, 30. März 2006 18:09 schrieb Bo Peng:
> |
> | > > I think that the configure script should also provide for a default
> | > > \path_prefix in lyxrc.default, probably based on platform.
Am Donnerstag, 30. März 2006 18:39 schrieb Jean-Marc Lasgouttes:
> I think this cygwin-without-cygwin stuff is becoming stranger and
> stranger.
Indeed. We should keep this as simple as possible. IMO a cygwin ignorant
person (such as me) should be able to understand the code without even
touchin
Am Donnerstag, 30. März 2006 21:33 schrieb Lars Gullik Bjønnes:
> Why cannot programs we defined with absolute paths when the prog is
> not in the default path? Why should lyx have its own path lookup
> logic?
There have been long discussions about that around jan 2005. I forgot the
reasons, but
Am Donnerstag, 30. März 2006 21:31 schrieb Bo Peng:
> I will do that, as well as the \Format+spacing later. Please apply the
> current patch first.
I'll do that if you submit a log entry. Note also that the pdflatex format
changes are missing.
Georg
Am Donnerstag, 30. März 2006 21:29 schrieb Bo Peng:
> Then, this is not my fault. :-)
I did not say that it was yours.
> I definitely agree, but a speedier review would be welcome.
No problem if you can extend each day by some extra hours ;-)
> The patch works, but I do not like the one line f
On Thursday 30 March 2006 20:14, Georg Baum wrote:
> If the goal is really to go to C++ I would skip the python part. Why
> create additional work?
Probably because it is easier to create and develop, it is cross platform
and a better approach than what we have now.
> Georg
--
José Abílio
On Thu, Mar 30, 2006 at 03:56:02PM +0200, Abdelrazak Younes wrote:
> Just for confirmation, is /cygdrive is present on any cygwin installation?
> But in the special case where a user has a c:\cygdrive and lyx is
> installed on the same drive, this test doesn't work (I just made the
> test). Is t
Am Mittwoch, 29. März 2006 20:49 schrieb Enrico Forestieri:
> I have reorganized things in this way:
> 1) The kind of path style to be written into .tex files is only
> decided by the configure script which checks what the correct
> style is (miktex vs cygwin tetex).
> 2) The "Use Cygwin-sty
> If we are going for this it will be a major new feature (IMHO) and
> should then wait for 1.7.
And it needs cleanup of classes like buffer. Anyway, the real
implementation is *easy* so this feature is not that far away from us.
Bo
On Thu, Mar 30, 2006 at 09:46:57PM +0200, Enrico Forestieri wrote:
> Please, attached find a patch correcting this problems.
I forgot to attach the patch.
--
Enrico
--- configure.py.orig Thu Mar 30 12:58:18 2006
+++ configure.pyThu Mar 30 21:27:14 2006
@@ -33,7 +33,7 @@
def removeF
> Please, attached find a patch correcting this problems. I have
> substituted "cmdOutput('cygpath -w ' + ...).replace('\\', '/')"
> with "cmdOutput('cygpath -m ' + ...)", as the -m flag to cygpath
> already does what you do with the replace().
> I also have corrected the logic: path correction is
"Bo Peng" <[EMAIL PROTECTED]> writes:
| Dear list,
|
| I just read a bit about 'LyX Wanted Features list' and saw
|
| Scripting language: Support a scripting language to control various
| parts of LyX, this requires deciding on an official scripting
| language. The idea is for non-core parts of
Lars Gullik Bjønnes wrote:
What happens if you do as it say?
oops missed the "there" ...
(and it did the trick of course)
thanks, edwin
On Thu, Mar 30, 2006 at 10:09:07AM -0600, Bo Peng wrote:
> >
> > I tested it on cygwin. Here are the results.
> >
> > 1) After launching, the script was hanging in checkCygwinPath().
> >I had to kill the latex.exe process to let it continue (I use
> >MikTeX, so latex.exe is a native win32 p
Georg Baum <[EMAIL PROTECTED]> writes:
| Am Donnerstag, 30. März 2006 18:09 schrieb Bo Peng:
|
| > > I think that the configure script should also provide for a default
| > > \path_prefix in lyxrc.default, probably based on platform. When
| > > sys.platform == 'cygwin', it would be:
| > >
| > > \
Edwin Leuven <[EMAIL PROTECTED]> writes:
| configure: error: source directory already configured; run "make
| distclean" there first
| [EMAIL PROTECTED]:~/svn/build$
|
| anyone else seeing this?
What happens if you do as it say?
cd .. (out of build)
mak
"Bo Peng" <[EMAIL PROTECTED]> writes:
| > But also the windows size storing stuff put me a bit off and I am a
| > lot more unsure if that is the right approach at all. (I think it is
| > in combination with the (reworked) other lyxrc patch).
|
| I think this is a quite common approach. If you are
> > > \path_prefix "/usr/local/bin:/usr/bin:/usr/X11R6/bin"
> >
> > Where will it be used?
>
> For running utility programs such as converters, viewers etc. This was
> introduced for native windows and is not needed for unix, because
> normally all programs are in the path. I don't know how it is o
> That place is wrong, too. mangledFilename() treats the extension
> specially.
Then, this is not my fault. :-) My current knowledge of lyx source
code only allows me to mimic existing code.
> This is a good example why reviewing is needed: Even if you are sure that
> your patch has no problem ot
Am Donnerstag, 30. März 2006 21:09 schrieb Bo Peng:
> >
> > Which version of tetex do you have? tetex 3 should be able to handle
that.
>
>
> % latex
> This is TeX, Version 3.14159 (Web2C 7.4.5)
>
> % rpm -qa | grep tetex
> tetex-fonts-2.0.2-22.EL4.7
> tetex-2.0.2-22.EL4.7
> tetex-afm-2.0.2-22.E
Am Donnerstag, 30. März 2006 18:09 schrieb Bo Peng:
> > I think that the configure script should also provide for a default
> > \path_prefix in lyxrc.default, probably based on platform. When
> > sys.platform == 'cygwin', it would be:
> >
> > \path_prefix "/usr/local/bin:/usr/bin:/usr/X11R6/bin"
>
Am Donnerstag, 30. März 2006 17:58 schrieb Bo Peng:
> Then, we would also need rc_copier_entry, rc_spell_command_entry ... .
> The real issue is actually people have been adjusting spaces to let
> the rc file look better and I don't want to mess it up again.
You could compute the needed amount of
Am Donnerstag, 30. März 2006 13:33 schrieb Enrico Forestieri:
> I think that the configure script should also provide for a default
> \path_prefix in lyxrc.default, probably based on platform. When
> sys.platform == 'cygwin', it would be:
>
> \path_prefix "/usr/local/bin:/usr/bin:/usr/X11R6/bin"
Am Donnerstag, 30. März 2006 10:50 schrieb Abdelrazak Younes:
> Your work load is impressive! I would like to advice you to ask for svn
> RW access to Lars.
I would support that.
> I wouldn't like you to be frustrated by people not
> having enough time to review your (big and frequent) patche
>
> Which version of tetex do you have? tetex 3 should be able to handle that.
% latex
This is TeX, Version 3.14159 (Web2C 7.4.5)
% rpm -qa | grep tetex
tetex-fonts-2.0.2-22.EL4.7
tetex-2.0.2-22.EL4.7
tetex-afm-2.0.2-22.EL4.7
tetex-dvips-2.0.2-22.EL4.7
tetex-xdvi-2.0.2-22.EL4.7
tetex-latex-2.0.2
> If at anything it is my workload during the week, usually during
> weekends I have some more time to spare.
I understand that. I am under the same situation.
> But also the windows size storing stuff put me a bit off and I am a
> lot more unsure if that is the right approach at all. (I think it
Am Mittwoch, 29. März 2006 22:45 schrieb Bo Peng:
> > OK, that means that the test is still necessary. But I don't
understand
> > why it works on windows.
Now I do: tex_allows_spaces is probably set in your windows installation
of LyX, and it is not in your Linux installation.
> On windows, I g
Am Mittwoch, 29. März 2006 21:51 schrieb Bo Peng:
> > mangledFilename() should be called on complete filenames (with
extension).
> > Please use something like
>
> This is not what the code shows me (insetbibtex.C, line 166).
That place is wrong, too. mangledFilename() treats the extension
speci
[EMAIL PROTECTED]:~/svn/lyx-devel$ ./autogen.sh
Using automake (GNU automake) 1.9.6
Using autoconf (GNU Autoconf) 2.59
Locating GNU m4... /usr/bin/m4
Generate acinclude.m4... done.
Building macros...
.
/usr/share/aclocal/glib.m4:8: warning: underquoted definition of
AM_PATH_GLIB
run in
Dear list,
I just read a bit about 'LyX Wanted Features list' and saw
Scripting language: Support a scripting language to control various
parts of LyX, this requires deciding on an official scripting
language. The idea is for non-core parts of LyX to be moved to the
scripting language and thus s
"Bo Peng" <[EMAIL PROTECTED]> writes:
| > I would like to advice you to ask for svn RW access to
| > Lars. I wouldn't like you to be frustrated by people not
| > having enough time to review your (big and frequent)
| > patches.
|
| I admit that I have been a little frustrated. I think, to be fair
Am Mittwoch, 29. März 2006 21:59 schrieb Michael Gerz:
> Could you please check whether they are relevant? (I am just a stupig
> guy running a diff tool).
You could pretend to be a clever guy by running diff with the -u
option ;-)
Seriously: unified diffs are far better readable IMO.
Georg
On Thu, Mar 30, 2006 at 01:43:34PM +0200, Georg Baum wrote:
> Enrico Forestieri wrote:
>
> > 2) lyxrc.defaults had CRLF terminators.
>
> This should not matter at all. Does LyX have problems reading it?
I don't think so. I simply noticed it because I made a diff with the
old lyxrc.default.
--
On Mar 30, 2006, at 12:07 PM, Darren Oh wrote:
I just installed LyX/Mac 1.4.0 and tried to open Preferences. LyX
crashed. I restarted it and opened a recent document, then tried to
open Preferences again. Instead of Preferences, the About window
opened. Clicking on the About menu item cause
I just installed LyX/Mac 1.4.0 and tried to open Preferences. LyX
crashed. I restarted it and opened a recent document, then tried to
open Preferences again. Instead of Preferences, the About window
opened. Clicking on the About menu item caused the status bar to
display "(buffer-export fax
Jean-Marc Lasgouttes a écrit :
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
I don't understand what is wrong with an #ifdef? I personally
prefer always compiletime checks rather than runtime checks if it
is possible. Why do a hackish runtime test if the same thing can be
achie
> I understand the frustration (gone through this) but this job, if you
> accept it :-), is equally applicable to linux.
You know how I was working on windows? I set up a cygwin/ssh server
and ssh to it from linux. I edit files locally (under linux) and
transfer files through scp, rsync or svn...
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>> I don't understand what is wrong with an #ifdef? I personally
>> prefer always compiletime checks rather than runtime checks if it
>> is possible. Why do a hackish runtime test if the same thing can be
>> achieved at compile ti
Bo Peng a écrit :
[...]
I would love to have svn RW access and I will take my greatest caution
not to abuse this privilege.
hint, hint...
[...]
and there is a big TODO with regards to Windows user. The problem
is related to graphics conversion for on-screen display
I hope I caught your inter
> I would like to advice you to ask for svn RW access to
> Lars. I wouldn't like you to be frustrated by people not
> having enough time to review your (big and frequent)
> patches.
I admit that I have been a little frustrated. I think, to be fairer to
the time I spent, Lars would better apply my
>
> I tested it on cygwin. Here are the results.
>
> 1) After launching, the script was hanging in checkCygwinPath().
>I had to kill the latex.exe process to let it continue (I use
>MikTeX, so latex.exe is a native win32 program, whereas python
>is a cygwin application). Doing so, the c
> Just a thought, but rather than hard code the formating of the "Format" and
> "Converter" entries, so:
> rc_entry = [ r'\Format agragr Grace "" "%%"
> "%%"']
> why not define rc_format_entry and rc_converter_entry functions, to be used
> so:
> rc_format_ent
Georg Baum a écrit :
Abdelrazak Younes wrote:
Abdelrazak Younes a écrit :
#include
bool isCygwin()
{
return access("/cygdrive", F_OK) == 0;
}
Just for confirmation, is /cygdrive is present on any cygwin
installation? But in the special case where a user has a c:\cygdrive and
lyx is inst
Jean-Marc Lasgouttes a écrit :
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Message to the main lyx developers:
Abdelrazak> IMHO, if you want to encourage new contributions, you
Abdelrazak> should relax a bit the implicit process of reviewing for
Abdelrazak> trunk.
Abdelrazak Younes wrote:
> Abdelrazak Younes a écrit :
>> #include
>>
>> bool isCygwin()
>> {
>> return access("/cygdrive", F_OK) == 0;
>> }
>>
>> Just for confirmation, is /cygdrive is present on any cygwin
>> installation? But in the special case where a user has a c:\cygdrive and
>> lyx
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Message to the main lyx developers:
Abdelrazak> IMHO, if you want to encourage new contributions, you
Abdelrazak> should relax a bit the implicit process of reviewing for
Abdelrazak> trunk. I think that external devel
Abdelrazak Younes a écrit :
#include
bool isCygwin()
{
return access("/cygdrive", F_OK) == 0;
}
Just for confirmation, is /cygdrive is present on any cygwin installation?
But in the special case where a user has a c:\cygdrive and lyx is
installed on the same drive, this test doesn't work
On Thu, 2006-03-30 at 16:23 +0200, Juergen Spitzmueller wrote:
> I think a good starting point, especially if your new on this area, is to use
> an existing dialog/controller, copy and adapt that. I think vspace could be a
> prototype in this case.
A couple of issues which it would be nice to re
John Spray wrote:
> > I have figured out and tested the latex to generate for all
> > combinations of input. Now I am
> > looking at qt4 designer. :-)
>
> Could you please write the controller first, before any UI? Once
> frontend code is written, it's a terrible effort to change anything in
> t
> Georg> I am interested in this, but your patches are coming in too
> Georg> fast. I am not able to deal with them in that pace :-(
>
> Ditto...
Well, I have overused my limited amount of hobby programming time and
really need to go back to work. Less patch will be submitted in the
next two weeks
Enrico Forestieri a écrit :
[...]
So, I agree with you that a part of the fix can also be applied
to the plain win32 target, but I do not think that we can avoid
all the "#ifdef __CYGWIN__" switches.
Maybe not all but any which can be deleted is good. Is there a simple
way to check at runtime if
Committed to trunk.
A more general way of setting paragraphs in an inset to standard
layout upon paste.
* insettext.[Ch]: add forceParagraphsToDefault method
* insettabular.C
(InsetTabular::doDispatch): use it for cell
* insetbox.C
(InsetB
On Thu, 2006-03-30 at 12:02 +0300, Martin Vermeer wrote:
...
> Attached a patch that I intend to put into trunk soon. In addition to
> smoother scrolling, I changed the button text Dn -> Down, and added
> keyboard shortcuts.
Committed:
* QToc.C
(QToc::updateToc): Better scroll b
On Thu, 2006-03-30 at 14:23 +0200, Helge Hafting wrote:
> I have figured out and tested the latex to generate for all
> combinations of input. Now I am
> looking at qt4 designer. :-)
Could you please write the controller first, before any UI? Once
frontend code is written, it's a terrible effor
Helge Hafting wrote:
> Pulldown list for selecting distance:
> small, med, big, fill, user defined
I'd add the insetspace spaces here as well (thinspace, quad, qquad and
friends; have a look at insetspace.C)
Other than that, the plan looks good.
Jürgen
Here is what I plan on making:
A dialog named "Horizontal spacing & formatting", as it does both
spacing and other things.
Pulldown list for selecting type:
space, dots, rule, leftarrow, rightarrow, upbrace, downbrace
Pulldown list for selecting distance:
small, med, big, fill, user defined
Ed
On Thu, Mar 30, 2006 at 01:16:56PM +0200, Abdelrazak Younes wrote:
> Enrico Forestieri a écrit :
> >That indeed would be great, but I think that the cygwin target has
> >some peculiarities not easily mimicked by a native build.
>
> IMHO, no need to mimic anything, he who want a cygwin functionali
Ekkehart Schlicht wrote:
Angus Leeming wrote:
Could you try out the executable found at
http://www.lyx.org/~leeming/ekkehart.exe
Hi Angus,
I tried the following:
ekkehart2.exe exits as follows:
4. with no drive associated with J: nothing
5. with an empty drive associated with J:
Angus Leeming wrote:
Could you try out the executable found at
http://www.lyx.org/~leeming/ekkehart.exe
Hi Angus,
I tried the following:
ekkehart.exe it exits here as follows:
1. with no drive associated with J:
Exception caught:
boost::filesystem::is_directory: "J:\foo": The
Enrico Forestieri wrote:
> 2) lyxrc.defaults had CRLF terminators.
This should not matter at all. Does LyX have problems reading it?
Georg
On Wed, Mar 29, 2006 at 10:55:19PM -0600, Bo Peng wrote:
> Dear list,
>
> configure.py was first written as a direct translation of the
> configure.m4 file. It is not structured, and use all global variables.
> Attached is a more pythonic version. It is the first step towards my
> goal of automati
Enrico Forestieri a écrit :
On Thu, Mar 30, 2006 at 11:01:29AM +0200, Abdelrazak Younes wrote:
Enrico Forestieri a écrit :
I have reviewed all (I think) possible problems related to paths in
cygwin. The attached is the patch I come up with. I hope that it can
be applied for 1.4.1 as it doesn't
On Thu, Mar 30, 2006 at 11:01:29AM +0200, Abdelrazak Younes wrote:
> Enrico Forestieri a écrit :
> >I have reviewed all (I think) possible problems related to paths in
> >cygwin. The attached is the patch I come up with. I hope that it can
> >be applied for 1.4.1 as it doesn't harm the other target
Ekkehart Schlicht wrote:
I hope that these observations help to solve the problem. I opt for
solution 1. at the moment and can now look forward to trying the new Lyx
1.4.1 (as time permits).
I hope that this bug is not too difficult to resolve.
Hi, Ekkehart.
Could you try out the executable
On Thu, 2006-03-30 at 10:55 +0200, Jean-Marc Lasgouttes wrote:
> > "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> Martin> I don't think it is relevant. If you look at updateToc() in
> Martin> QToc.C, what happens every time the method is called is, that
>
> Martin> - the document
On Thu, 2006-03-30 at 08:43 +0300, Martin Vermeer wrote:
> On Wed, 2006-03-29 at 23:40 +0200, Jean-Marc Lasgouttes wrote:
> > > "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
> >
> > >> Would it be possible to remember the scrollbar position and reset
> > >> it afterwards (if entry is
Enrico Forestieri a écrit :
I have reviewed all (I think) possible problems related to paths in
cygwin. The attached is the patch I come up with. I hope that it can
be applied for 1.4.1 as it doesn't harm the other targets and is
really needed for cygwin.
Hello Enrico,
Having had a (quick) loo
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Bo Peng wrote:
>> Dear list,
>>
>> I am surprised to see that nobody seems to be interested in such a
>> feature, which is, at least to me, a big step forward for the
>> userfriendliness of lyx. Considering that you can directly open
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
Martin> I don't think it is relevant. If you look at updateToc() in
Martin> QToc.C, what happens every time the method is called is, that
Martin> - the document (!) is traversed looking for TOC-able headers -
Martin> the QListView is bu
Bo Peng a écrit :
Dear list,
configure.py was first written as a direct translation of the
configure.m4 file. It is not structured, and use all global variables.
Attached is a more pythonic version. It is the first step towards my
goal of automatic partial re-configuration.
Hi Bo,
Your work l
Bo Peng <[EMAIL PROTECTED]> writes:
>
> Dear list,
>
> configure.py was first written as a direct translation of the
> configure.m4 file. It is not structured, and use all global variables.
> Attached is a more pythonic version. It is the first step towards my
> goal of automatic partial re-conf
93 matches
Mail list logo
