On Thu, 2006-11-02 at 07:59 +0100, Asger Ottar Alstrup wrote:
> Martin Vermeer wrote:
> > On Wed, Nov 01, 2006 at 11:36:08PM +0100, Asger Ottar Alstrup wrote:
> >> [Partial refresh requires partial coord cache refresh]
>
> > Hmmm, I don't think this is done in 1.4, and still single par update
> >
On Thursday 02 November 2006 6:11 am, Enrico Forestieri wrote:
> Georg, I think you forgot to update src/ChangeLog.
Another reason why having 1.5 as the stable series is an beneficial. ;-)
> --
> Enrico
--
José Abílio
Martin Vermeer wrote:
On Wed, Nov 01, 2006 at 11:36:08PM +0100, Asger Ottar Alstrup wrote:
[Partial refresh requires partial coord cache refresh]
Hmmm, I don't think this is done in 1.4, and still single par update
works just fine there...
I guess that in the common case, things work out c
On Wed, Nov 01, 2006 at 11:36:08PM +0100, Asger Ottar Alstrup wrote:
> Hi,
>
> To implement partial update (single paragraph update), it is not enough
> just to redraw only those parts of the screen.
>
> You also have to implement partial update of the coord cache. Right now,
> the only possibl
[EMAIL PROTECTED] wrote:
> Author: baum
> Date: Wed Nov 1 10:46:14 2006
> New Revision: 15655
>
> URL: http://www.lyx.org/trac/changeset/15655
> Log:
> Fix generation of invalid LyX files
> * src/lyxfont.C
> (LyXFont::lyxWriteChanges): Don't change color "inherit" to
> "default
Dear all,
http://www.lyx.org/trac/changeset/15688
As far as I can tell, I have solved the three state toolbar chaos
completely by introducing this view->toolbar menu and
LFUN_TOOLBAR_TOGGLE_STATE lfunc. If there is no objection, I will
apply both patches tomorrow to attract more testing. Interes
hi michael,
> If appropriate, we took your translations from the 1.4.X stable branch
> such that your prior work didn't get lost.
this was not good note ;) i was close to forget all the bug-fixes
i've made in 1.4.x from the initial 1.4 stage... (next time maybe better
to say directly, which versi
On Wed, Nov 01, 2006 at 09:15:08PM +0100, Joost Verburg wrote:
> Jean-Marc Lasgouttes wrote:
> > Joost> Agreed. As I said earlier, the developers can use a setting so
> > Joost> it will be possible for them to run multiple LyX processes.
> > Joost> That will be useful for debugging, testing etc.
>
On Wed, Nov 01, 2006 at 09:39:02PM +0100, Joost Verburg wrote:
> Lars Gullik Bjønnes wrote:
> > We have a filesystem...
> > Filesystems are shared between computers...
> > Computer have users...
> > Users run LyX...
> > LyX loads the same file...
>
> LyX can set a write lock on open files.
>
> >
On Wed, Nov 01, 2006 at 09:02:24PM +0100, Jean-Marc Lasgouttes wrote:
> > "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes:
>
> Enrico> However, I don't think it is wise using different mechanisms
> Enrico> on different platforms. Maybe the socket code could be
> Enrico> switched from
Yeah, it was not that hard (see below). It's just that I don't have much
time.
This does solves my bookmark problem, but are you sure it is a good
idea to open all buffers that was opened in the parent window?
My proposal was that we do not open any buffer but allow users to
switch to them from
Peter Kümmel wrote:
Abdelrazak Younes wrote:
This does not help. But after a CTRL-N all is fine,
so it couldn't be that hard for someone who knows
all the details. ;)
Yeah, it was not that hard (see below). It's just that I don't have much
time.
Abdel.
This commit initialise correctly the t
Hi,
To implement partial update (single paragraph update), it is not enough
just to redraw only those parts of the screen.
You also have to implement partial update of the coord cache. Right now,
the only possible operation for the coord cache is to clear all of it.
To implement partial upd
[EMAIL PROTECTED] wrote:
Author: schmitt
Date: Wed Nov 1 22:17:56 2006
New Revision: 15680
URL: http://www.lyx.org/trac/changeset/15680
Log:
* text.C: fix another change tracking FIXME
We are making progress... slowly but constantly.
I may not be able to do much LyX work in the n
Lars Gullik Bjønnes wrote:
We have a filesystem...
Filesystems are shared between computers...
Computer have users...
Users run LyX...
LyX loads the same file...
LyX can set a write lock on open files.
It is not a requirement, and why are you talking about synchronizing
documents? We only wan
Hi, Lars (and others),
Attached is the patch you can beat. It will be committed tomorrow. It
works well here, except for the on/off/auto state change, which needs
frontend support.
This patch:
1. toolbar has on/off/auto states, (see session.h)
2. I have added an AUTO flag to Toolbar. MATH etc wi
> I think we are not going to do anything useful without intercepting
> the Qt toolbars popup and using ours instead. Then the session code
> will have real data to look at, not some randomly relevant values from
> Qt.
This is Bo's latest suggestion if I understand it correctly.
So the menu is
Joost Verburg <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > | There is a reason why all word processors that support multiple
| > | windows have a single running process. It should not be possible to
| > | open the same document multiple times when the data is not shared
| > | betw
Bo Peng wrote:
I am sorry but where this menu is implemented? I can not find it
anywhere. I need to either change it to
review -> on/off/auto (submenu)
A submenu is the best option in my opinion. The menu is created by Qt
and should be replaced with a custom menu.
Joost
Abdelrazak Younes wrote:
I can explain you how it works on Windows,
Yes please.
You can use a mutex to detect the running process and a window message
to have the existing process start a new document.
Joost
Jean-Marc Lasgouttes wrote:
I think we are not going to do anything useful without intercepting
the Qt toolbars popup and using ours instead. Then the session code
will have real data to look at, not some randomly relevant values from
Qt.
This is Bo's latest suggestion if I understand it correc
Jean-Marc Lasgouttes wrote:
Joost> Agreed. As I said earlier, the developers can use a setting so
Joost> it will be possible for them to run multiple LyX processes.
Joost> That will be useful for debugging, testing etc.
Or useful in real life, for people who know what they are doing.
Yes. But
On Wednesday 01 November 2006 8:00 pm, Jean-Marc Lasgouttes wrote:
> Well, the initial settings are useful.
I agree.
> JMarc
--
José Abílio
Jean-Marc Lasgouttes wrote:
Well, the initial settings are useful.
Indeed, it should be possible to set the state when a user starts LyX
for the first time.
Joost
> "Joost" == Joost Verburg <[EMAIL PROTECTED]> writes:
Joost> Agreed. As I said earlier, the developers can use a setting so
Joost> it will be possible for them to run multiple LyX processes.
Joost> That will be useful for debugging, testing etc.
Or useful in real life, for people who know wh
Lars Gullik Bjønnes wrote:
| There is a reason why all word processors that support multiple
| windows have a single running process. It should not be possible to
| open the same document multiple times when the data is not shared
| between the windows.
It does not follow that a single running
Jean-Marc Lasgouttes wrote:
Let's say we should use the same instance by default (to avoid
surprises), but there should be a way to launch a new instance.
Agreed. As I said earlier, the developers can use a setting so it will
be possible for them to run multiple LyX processes. That will be use
> "Bo" == Bo Peng <[EMAIL PROTECTED]> writes:
>> Depending on these two states the mode can be set to 'on', 'off' or
>> 'auto'.
Bo> The problem is how you switch them through right-click-menu, and
Bo> how to differentiate the states when lyx exits?
I think we are not going to do anything usef
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
| In LyX 1.4 there is one window per process. However now one process
| can have multiple windows, there should only be one running process.
Lars> I don't get this logic.
Let's say we should use the same instance by default (to avo
Joost Verburg <[EMAIL PROTECTED]> writes:
| > I would have liked us to have some better control over files that
| > might have changed on disk though. (And this is a problem we have
| > regardless of only one lyx instance or not.)
|
| There is a reason why all word processors that support multipl
what dead horse? did it die in the 5 minutes from the patch was posted
till I posted my reply?
You should look for [Updated PATCH] or [Updated Updated PATCH] 1 hours
after this. :-)
Bo
> "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes:
Enrico> However, I don't think it is wise using different mechanisms
Enrico> on different platforms. Maybe the socket code could be
Enrico> switched from AF_UNIX to AF_INET such that lyxclient would
Enrico> also work on Windows.
We a
> "Michael" == Michael Gerz <[EMAIL PROTECTED]> writes:
Michael> In other words: Once the settings are saved, the default.ui
Michael> settings are pointless. Which suggests getting rid of them.
Well, the initial settings are useful.
JMarc
Lars Gullik Bjønnes wrote:
| 2) and 3) share the same data, but 1) does not. Do you really expect
| the users to know which windows belong to which instance?
as a matter of fact, yes I do.
The windows look identical. There is no way to tell the difference.
I would have liked us to have some
"Bo Peng" <[EMAIL PROTECTED]> writes:
| > This should not be static. (anon namespace is enough)
| > Also indentation is wrong.
|
| Lars, you are shooting a dead horse. An updated patch is available.
| (And a further updated patch will be available soon.)
what dead horse? did it die in the 5 minu
At the same time this menu should also be accessible using View >
Toolsbars. Otherwise there is a problem when all toolbars are hidden.
I am sorry but where this menu is implemented? I can not find it
anywhere. I need to either change it to
review -> on/off/auto (submenu)
or
X review
X auto rev
> "Michael" == Michael Gerz <[EMAIL PROTECTED]> writes:
Michael> With the proposed solution above, "auto" is silently
Michael> introduced, even if the user doesn't like it. I am willing to
Michael> accept this for math and table but not for review.
That is the problem: everybody has his own
Joost Verburg <[EMAIL PROTECTED]> writes:
| José Matos wrote:
| > What is the difference to what we have now?
| > Why don't we see people complaining about that?
|
| In LyX 1.4 there is one window per process. However now one process
| can have multiple windows, there should only be one runni
This should not be static. (anon namespace is enough)
Also indentation is wrong.
Lars, you are shooting a dead horse. An updated patch is available.
(And a further updated patch will be available soon.)
Bo
Joost Verburg <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > sure it does. I do this all the time with emacs and firefox.
|
| Firefox has only a single process for all windows.
|
| In LyX you can have right now:
|
| 1) Multiple LyX instances (different processes)
| 2) Multiple win
Peter Kümmel <[EMAIL PROTECTED]> writes:
| Index: frontends/LyXView.h
| ===
| --- frontends/LyXView.h (revision 15652)
| +++ frontends/LyXView.h (working copy)
| @@ -136,6 +136,7 @@
|
| /// update the toolbar
|
Bo Peng wrote:
1. we modify the right-click-menu to (use review, math, table are the same)
X review (on/off)
X auto review (on/off)
autoreview will override on/off. That is to say, we default to review
(always) on, or (always) off. It a user select auto review, then auto
is enabled. The mode s
José Matos wrote:
What is the difference to what we have now?
Why don't we see people complaining about that?
In LyX 1.4 there is one window per process. However now one process can
have multiple windows, there should only be one running process.
Joost
Lars Gullik Bjønnes wrote:
sure it does. I do this all the time with emacs and firefox.
Firefox has only a single process for all windows.
In LyX you can have right now:
1) Multiple LyX instances (different processes)
2) Multiple windows per instance
3) Multiple documents per window
2) and 3
On Wednesday 01 November 2006 6:11 pm, Joost Verburg wrote:
>
> It does not make sense to allow multiple instances when each instance
> can also have multiple windows. There is no way to tell which window
> belongs to which instance and therefore you can easily loose data by
> saving the wrong vers
Joost Verburg <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > | Sometimes you want to edit to same document in two places. However now
| > | we have this multiple window feature, it should not be possible
| > | anymore to start multiple LyX instances. Can someone take a look at
| > |
There is no problem. You can save a different state depending on whether
the user is working in text mode or math mode.
This is difficult.
Maybe:
1. we modify the right-click-menu to (use review, math, table are the same)
X review (on/off)
X auto review (on/off)
autoreview will override on/
On Wed, Nov 01, 2006 at 06:55:52PM +0100, Joost Verburg wrote:
> Enrico Forestieri wrote:
> >> Sometimes you want to edit to same document in two places. However now
> >> we have this multiple window feature, it should not be possible anymore
> >> to start multiple LyX instances.
> >
> > Unless
Peter Kümmel wrote:
Now is the time to discuss. ;)
We have two possibilities:
1. default is context-sensitive but the manual change to show
when the CT toolbar is hidden will be rememberd forever
2. default is visible and hiding moves the toolbar to the context-sensitive
state
There are
Bo Peng wrote:
The problem is how you switch them through right-click-menu, and how
to differentiate the states when lyx exits?
There is no problem. You can save a different state depending on whether
the user is working in text mode or math mode. If you remember these two
states it is also p
Depending on these two states the mode can be set to 'on', 'off' or 'auto'.
The problem is how you switch them through right-click-menu, and how
to differentiate the states when lyx exits?
Bo
Bo Peng wrote:
>> > The major problem is with
>> > math/review/table toolbars. The logic is now:
>> >
>> > 1. if math is on when lyx exists, I assume it is always on
>> > 2. if math is off when lyx exists, I assume it is auto.
>>
>> But now it does not remember the position of the moved auto toolba
On Wed, Nov 01, 2006 at 05:44:52PM +0100, Abdelrazak Younes wrote:
> Martin Vermeer wrote:
> >
> >I'm not sure your description is quite right... the problem is the
> >statement
> >
> > buffer_view_->updateMetrics(false);
> >
> >which you added in revision 14456. It repaints the whole screen e
> 1. if math is on when lyx exists, I assume it is always on
> 2. if math is off when lyx exists, I assume it is auto.
Will it be the same with "review"? Yesterday, I noticed that
context-sensitive toolbars can be a real pain. Just imagine two loaded
documents, one with CT on, the other one with
Peter Kümmel wrote:
We have two possibilities:
1. default is context-sensitive but the manual change to show
when the CT toolbar is hidden will be rememberd forever
2. default is visible and hiding moves the toolbar to the context-sensitive
state
No, it is also possible to save multiple st
Bo Peng wrote:
The logic is now:
1. if math is on when lyx exists, I assume it is always on
2. if math is off when lyx exists, I assume it is auto.
I don't think this is a good idea. Either multiple states should be
saved (on/off in text mode and on/off in math mode) or the auto toolbars
sho
> The major problem is with
> math/review/table toolbars. The logic is now:
>
> 1. if math is on when lyx exists, I assume it is always on
> 2. if math is off when lyx exists, I assume it is auto.
But now it does not remember the position of the moved auto toolbars.
Because auto toolbars are no
Michael Gerz wrote:
> Bo Peng wrote:
>
>> 1. if math is on when lyx exists, I assume it is always on
>> 2. if math is off when lyx exists, I assume it is auto.
>
> Will it be the same with "review"? Yesterday, I noticed that
> context-sensitive toolbars can be a real pain. Just imagine two loaded
On Wed, Nov 01, 2006 at 07:28:09PM +0100, Michael Gerz wrote:
> >1. if math is on when lyx exists, I assume it is always on
> >2. if math is off when lyx exists, I assume it is auto.
>
> Will it be the same with "review"? Yesterday, I noticed that
> context-sensitive toolbars can be a real pain.
Michael Gerz wrote:
How do the session settings and the default settings in default.ui
interact? Which overrules which?
And do we still need default settings in default.ui at all?
I assume they are obsolete after the first startup, because then the
session info overrule the default.ui settin
Abdel,
A new patch has been posted. To answer your questions:
Well, I don't want to minimize your work Bo but for the toolbar
positioning, maybe we could use Qt own session management and call that
from your own session class?
No, we still have the GUII policy so session does not know what q
Bo Peng wrote:
> Hi, Peter,
>
> I revised your patch and now it works fine (save restore on/off and
Nice improvements! I feared the casts.
> location). It works like this. The major problem is with
> math/review/table toolbars. The logic is now:
>
> 1. if math is on when lyx exists, I assume it
Bo Peng wrote:
1. if math is on when lyx exists, I assume it is always on
2. if math is off when lyx exists, I assume it is auto.
Will it be the same with "review"? Yesterday, I noticed that
context-sensitive toolbars can be a real pain. Just imagine two loaded
documents, one with CT on, the
It works like this. The major problem is The logic is now:
I surely wrote something more readable, but gmail messed things up
when it stopped responding and I clicked "send" the second time. I
have also checked my system time, and it is accurate to milliseconds.
I guess the gmail SMTP serv
Lars Gullik Bjønnes wrote:
| Sometimes you want to edit to same document in two places. However now
| we have this multiple window feature, it should not be possible
| anymore to start multiple LyX instances. Can someone take a look at
| this?
Why?
It does not make sense to allow multiple inst
Joost Verburg wrote:
Abdelrazak Younes wrote:
Sometimes you want to edit to same document in two places. However
now we have this multiple window feature, it should not be possible
anymore to start multiple LyX instances. Can someone take a look at
this?
Could you post again the code to do s
Hi, Peter,
I revised your patch and now it works fine (save restore on/off and
location). It works like this. The major problem is with
math/review/table toolbars. The logic is now:
1. if math is on when lyx exists, I assume it is always on
2. if math is off when lyx exists, I assume it is auto.
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| If you want to revert the code to your old solution, please explain
| your rationale on the list (with more pragmatic reasons than "string"
| is not appropriate for containing utf8).
You are not listening. I am saying th
Joost Verburg <[EMAIL PROTECTED]> writes:
| Peter Kümmel wrote:
| > I don't understand why we need this new Window feature.
| > If someone wants two top level LyX programs then he could
| > start LyX twice.
|
| Sometimes you want to edit to same document in two places. However now
| we have this
Abdelrazak Younes wrote:
Sometimes you want to edit to same document in two places. However now
we have this multiple window feature, it should not be possible
anymore to start multiple LyX instances. Can someone take a look at this?
Could you post again the code to do so?
I can explain you
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| If you want to revert the code to your old solution, please explain
| your rationale on the list (with more pragmatic reasons than "string"
| is not appropriate for containing utf8).
You are not listening. I am saying that "string" is not appropriat
Enrico Forestieri wrote:
Sometimes you want to edit to same document in two places. However now
we have this multiple window feature, it should not be possible anymore
to start multiple LyX instances.
Unless specifically requested. I have your word that I can have
that option ;-)
Sure, a com
Joost Verburg wrote:
Peter Kümmel wrote:
I don't understand why we need this new Window feature.
If someone wants two top level LyX programs then he could
start LyX twice.
Sometimes you want to edit to same document in two places. However now
we have this multiple window feature, it should no
Peter Kümmel wrote:
Bo Peng wrote:
I don't understand why we need this new Window feature.
If someone wants two top level LyX programs then he could
start LyX twice.
When I edit a large lyx file, I often need to refer to another part of
the file. Two windows (or two panels) would help me a lot.
On Wed, Nov 01, 2006 at 06:25:05PM +0100, Joost Verburg wrote:
> Peter Kümmel wrote:
> > I don't understand why we need this new Window feature.
> > If someone wants two top level LyX programs then he could
> > start LyX twice.
>
> Sometimes you want to edit to same document in two places. Howeve
Bo Peng wrote:
>> I don't understand why we need this new Window feature.
>> If someone wants two top level LyX programs then he could
>> start LyX twice.
>
> When I edit a large lyx file, I often need to refer to another part of
> the file. Two windows (or two panels) would help me a lot. Of cour
Now it's possible to compile without precompiled headers,
from README.cmake:
- for the Debug and Release build all precompiled headers are enabled
to compile without pch (to check if all necessary headers are included)
* use MinSizeRel which only precompiles the STL and Boo
Bo Peng wrote:
It is very wrong to have the tabbar show _all_ buffers. Can't we
change it right now to show only buffers in current LyXView?
I do not like that behavior either. I propose that
1. view->Documents show all documents that is opened in all windows
2. tabs only show opened documents
I don't understand why we need this new Window feature.
If someone wants two top level LyX programs then he could
start LyX twice.
When I edit a large lyx file, I often need to refer to another part of
the file. Two windows (or two panels) would help me a lot. Of course I
can start two lyx insta
Peter Kümmel wrote:
I don't understand why we need this new Window feature.
If someone wants two top level LyX programs then he could
start LyX twice.
Sometimes you want to edit to same document in two places. However now
we have this multiple window feature, it should not be possible anymore
On Wed, Nov 01, 2006 at 02:23:46PM +0100, Herbert Voss wrote:
> Enrico Forestieri schrieb:
[...]
> > Essentially, we should replace the converter from postscript to pdf
> > as follows:
> >
> > pspdf13 -dAutoRotatePages#/None $$i $$o
>
> why ps2pdf13??
> This is a regression. It should be ps2pdf,
Bo Peng wrote:
>> It is very wrong to have the tabbar show _all_ buffers. Can't we
>> change it right now to show only buffers in current LyXView?
>
> I do not like that behavior either. I propose that
> 1. view->Documents show all documents that is opened in all windows
> 2. tabs only show opened
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>> Abdelrazak Younes wrote:
>>> Peter,
>>>
>>> You've done a good job there thanks!
>>>
>>> On request though: Could you please load the TabBar (if there's more
>>> than document that is) by default when a new Window is opened?
>>>
>>> Thanks in advanc
Am Mittwoch, 1. November 2006 17:50 schrieb Peter Kümmel:
> Maybe here:
>
> Index: buffer.C
> ===
> --- buffer.C(revision 15674)
> +++ buffer.C(working copy)
> @@ -373,7 +373,7 @@
>
> void Buffer::setFileName(string const &
It is very wrong to have the tabbar show _all_ buffers. Can't we
change it right now to show only buffers in current LyXView?
I do not like that behavior either. I propose that
1. view->Documents show all documents that is opened in all windows
2. tabs only show opened documents in *this* window
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>> And what I say is the buffer_switch should show the buffer in the
>> current view, not change view. We have OS support for switching
>> between windows.
>>
>> If this is not good enough, it is probably that our model is not
>
Bennett Helm wrote:
On Nov 1, 2006, at 2:42 AM, Abdelrazak Younes wrote:
Is there no official binary qt release from trolltec for OS X?
The official page does not cite any:
http://www.trolltech.com/developer/downloads/qt/mac
But their ftp site seems to have one:
ftp://ftp.trolltech.com/qt/s
On Wed, Nov 01, 2006 at 03:21:18PM +0100, Leuven, E. wrote:
> From: Enrico Forestieri [mailto:[EMAIL PROTECTED]
> > I agree with John here. I also like having 1-pixel cursor...
>
> aah, a poll! i love polls!! i vote for the 2-pixel cursor
>
> ;-)
>
Yeah, these unessential discussions are alway
Georg Baum wrote:
> Am Mittwoch, 1. November 2006 17:27 schrieb Leuven, E.:
>>> I use the 'onlyFilename' function to set the tab name so
>> yeah, i saw that...
>>
>>> I wonder why you see the full path?
>>> Is this function is broken?
>> it looks for a forward slash
>>
>> string::size_type j =
Martin Vermeer wrote:
I'm not sure your description is quite right... the problem is the statement
buffer_view_->updateMetrics(false);
which you added in revision 14456. It repaints the whole screen every time
redraw is
called -- which happens even when only a row or para repaint ough
On Wed, Nov 01, 2006 at 03:55:56PM +0100, Abdelrazak Younes wrote:
> Enrico Forestieri wrote:
> > On Wed, Nov 01, 2006 at 03:21:13PM +0100, Abdelrazak Younes wrote:
>
> >> But quite frankly, I don't understand what's so bad about letting the
> >> user change the cursor width. I put that at the s
Am Mittwoch, 1. November 2006 17:27 schrieb Leuven, E.:
> > I use the 'onlyFilename' function to set the tab name so
>
> yeah, i saw that...
>
> > I wonder why you see the full path?
> > Is this function is broken?
>
> it looks for a forward slash
>
> string::size_type j = fname.rfind('/'
On Wed, Nov 01, 2006 at 04:49:49PM +0200, Martin Vermeer wrote:
> On Wed, Nov 01, 2006 at 11:03:18AM +0100, Abdelrazak Younes wrote:
> > Martin Vermeer wrote:
> > >On Wed, 2006-11-01 at 08:26 +0100, Asger Ottar Alstrup wrote:
...
> > >>As I said before, I believe the best is to draw less. There i
> I use the 'onlyFilename' function to set the tab name so
yeah, i saw that...
> I wonder why you see the full path?
> Is this function is broken?
it looks for a forward slash
string::size_type j = fname.rfind('/');
whereas dirs are separated here with backward slashes...
Dear translators,
the LyX team is working hard on LyX 1.5.0. We intend to publish a first
alpha release by mid-November.
Today, we cleaned up the *.po files in the trunk of the SVN repository.
If appropriate, we took your translations from the 1.4.X stable branch
such that your prior work di
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>> Abdelrazak Younes wrote:
>>> Bo Peng wrote:
>> Abdelrazak> So explain me how you are going to switch to file-A on
>> Abdelrazak> view-1, file-C on view-2 and file-B on view-3?
>>
>> For sessions or in normal use?
> for restoring
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
> Uwe Stöhr wrote:
> > Can we get get rid of horizontal box content alignment in box dialog?
> > This is in any case greyed out
>
> No. Chose "Type: Rectangular Box" and "Inner Box: None", for instance.
Thanks, this pointed me to my new LyX manua
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Bo Peng wrote:
Abdelrazak> So explain me how you are going to switch to file-A on
Abdelrazak> view-1, file-C on view-2 and file-B on view-3?
For sessions or in normal use?
for restoring session.
No, this is not for session, it is for bookmarks and
Jean-Marc Lasgouttes wrote:
"Bo" == Bo Peng <[EMAIL PROTECTED]> writes:
Bo> 1. open documents in one window, save bookmarks 2. open a new
Bo> window. View->Documents and Bookmarks are grayed out. If I enable
Bo> them and click, lyx will crash since there is no valid view to
Bo> display the buff
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> As I said multiple times, this problem will be solved
Abdelrazak> implicitely when Peter enable the tabbar on _all_ windows.
I do not understand whatthe tabbar has to be with buffer_switch.
JMarc
1 - 100 of 194 matches
Mail list logo
