Hi Abdel,
On Tue, Apr 14, 2009 at 10:13 AM, Abdelrazak Younes wrote:
> I've been thinking of a blog for many years but never managed to take the
> time to do it... maybe that's the right time :-)
> But in the mean time, here are a few pictures of Amir in the arms of his
> sister Lina.
Beautiful
Am 2009-04-15 schrieb Kornel Benko:
> Am 2009-04-14 schrieb Abdelrazak Younes:
> > Hello Kornel,
> >
> > I am a bit annoyed that po building is done at each compilation,
> > couldn't this be made optional or being done with "make install" or
> > "make po"? Right now, everytime I compile either o
Am 2009-04-14 schrieb Jean-Marc Lasgouttes:
> "Vincent van Ravesteijn - TNW" writes:
> > I'm annoyed that building the documentation is turned on by default. I
> > always have one project failing, because I don't have perl. Could this
> > be turned off by default in MSVC (if you don't have perl) ?
Am 2009-04-14 schrieb Vincent van Ravesteijn - TNW:
> >
>
> I'm annoyed that building the documentation is turned on by default. I
> always have one project failing, because I don't have perl. Could this
> be turned off by default in MSVC (if you don't have perl) ?
>
Uhm, yes of course.
Am 2009-04-14 schrieb Abdelrazak Younes:
> Hello Kornel,
>
> I am a bit annoyed that po building is done at each compilation,
> couldn't this be made optional or being done with "make install" or
> "make po"? Right now, everytime I compile either on Linux or Windows, I
> get these lengthy msgme
On Mon, 13 Apr 2009, Abdelrazak Younes wrote:
As I leaked the highly important news that my wife was pregnant
(whatever JMarc says), I'd thought I should announce formally that this
state of affair finally led to a small cute little guy named Amir :-)
The mother (Aya) is doing very well.
Con
Eran Kaplinsky wrote:
I find that many of my older documents cannot be opened from within
1.6.2; however, if opened from a windows folder by doubleclicking,
they come up just fine with the same 1.6.2
That is very odd. Could it be some kind of path problem?
rh
Abdelrazak Younes a écrit :
Lavaud Michel wrote:
Hello,
I usually work with ToC window detached from document. It seems it is
alway above the main Lyx window. Would it be possible to add an
option to have the toc window behind the main, when focus is on the
main window ? The present behavior
"Vincent van Ravesteijn - TNW" writes:
> I'm annoyed that building the documentation is turned on by default. I
> always have one project failing, because I don't have perl. Could this
> be turned off by default in MSVC (if you don't have perl) ?
The script used by cmake (only!) should be rewritt
>Hello Kornel,
>
>I am a bit annoyed that po building is done at each compilation,
>couldn't this be made optional or being done with "make install"
>or "make po"? Right now, everytime I compile either on Linux or
>Windows, I get these lengthy msgmerge and msgfmt calls...
>
>Please?
>
I'm annoye
Hello Kornel,
I am a bit annoyed that po building is done at each compilation,
couldn't this be made optional or being done with "make install" or
"make po"? Right now, everytime I compile either on Linux or Windows, I
get these lengthy msgmerge and msgfmt calls...
Please?
Abdel.
"Vincent van Ravesteijn - TNW" writes:
> Looking at the AtPoint code I realize that I might have forgotten to
> call cur.undispatched(). Without this call, the lfun is never relayed to
> the current inset after it has been dispatched to the next inset.
Yes, this point is important.
> If this is
"Vincent van Ravesteijn - TNW" writes:
> P.S I'm also annoyed by the difference between dispatch() and
> getStatus(). Namely one of them returns a bool to indicate whether a
> definitive decision has been made, whereas the other uses the
> cur.dispatched_ member.
What I'd like even is to have get
I find that many of my older documents cannot be opened from within
1.6.2; however, if opened from a windows folder by doubleclicking, they
come up just fine with the same 1.6.2
Lavaud Michel wrote:
Hello,
I usually work with ToC window detached from document. It seems it is
alway above the main Lyx window. Would it be possible to add an option
to have the toc window behind the main, when focus is on the main
window ? The present behavior is ok with large screen but
>"Vincent van Ravesteijn - TNW" writes:
>> 1. If we want to use the AtPoint mechanism for this, we should take
>> this argument into account when deciding to which Inset to relay.
This
>> would mean to put lfun-specific code into LyXAction::dispatch (IIRC),
>> which is ugly.
>
>The note inset
-Original Message-
From: Lavaud Michel [mailto:michel.lav...@cegetel.net]
Sent: dinsdag 14 april 2009 17:10
To: sa...@lyx.org; lyx-devel@lists.lyx.org
Subject: Re: position of ToC window
Pavel Sanda a écrit :
> Lavaud Michel wrote:
>
>> Hello,
>>
>> I usually work with ToC window de
Lavaud Michel wrote:
> I'm not sure I understand what you mean by "close Lyx", is it use 'File /
> Quit' option (ctrl-Q) ? If yes, with Windows version, this closes also the
> toc window? Or is it some other option ?
the point is that after file/quit and running lyx again, toc window is
opened a
Pavel Sanda a écrit :
Lavaud Michel wrote:
Hello,
I usually work with ToC window detached from document. It seems it is alway
above the main Lyx window. Would it be possible to add an option to have
the toc window behind the main, when focus is on the main window ? The
present behavior is
Hello,
I noticed in the Display menu ("Visualiser" in French) of Lyx 1.6.2 that
the option to undo the split of display screen ("Diviser la vue
gauche/droite" and "Diviser la vue haut/bas") is "Fermer le groupe de
tabulation". I think it should read something like "Fermer la division"?
Maybe t
Lavaud Michel wrote:
> Hello,
>
> I usually work with ToC window detached from document. It seems it is alway
> above the main Lyx window. Would it be possible to add an option to have
> the toc window behind the main, when focus is on the main window ? The
> present behavior is ok with large sc
Hello,
I usually work with ToC window detached from document. It seems it is
alway above the main Lyx window. Would it be possible to add an option
to have the toc window behind the main, when focus is on the main window
? The present behavior is ok with large screen but it is a pain on small
Jean-Marc Lasgouttes wrote:
Abdelrazak Younes writes:
Vincent van Ravesteijn - TNW wrote:
3. Yet another way is to introduce a new LyXAction flag that says that
this lfun should be dispatched both to the current inset as to the next
inset. In that case, we could process the argument i
Jean-Marc Lasgouttes wrote:
"Vincent van Ravesteijn - TNW" writes:
1. If we want to use the AtPoint mechanism for this, we should take this
argument into account when deciding to which Inset to relay. This would
mean to put lfun-specific code into LyXAction::dispatch (IIRC), which is
ugly.
Abdelrazak Younes writes:
> Vincent van Ravesteijn - TNW wrote:
>> 3. Yet another way is to introduce a new LyXAction flag that says that
>> this lfun should be dispatched both to the current inset as to the next
>> inset. In that case, we could process the argument in Inset::dispatch.
>> That wo
"Vincent van Ravesteijn - TNW" writes:
> 1. If we want to use the AtPoint mechanism for this, we should take this
> argument into account when deciding to which Inset to relay. This would
> mean to put lfun-specific code into LyXAction::dispatch (IIRC), which is
> ugly.
The note inset can look at
Vincent van Ravesteijn - TNW wrote:
3. Yet another way is to introduce a new LyXAction flag that says that
this lfun should be dispatched both to the current inset as to the next
inset. In that case, we could process the argument in Inset::dispatch.
That would mean AtPointAll (or something like t
Pavel Sanda writes:
> Jean-Marc Lasgouttes wrote:
>> Pavel Sanda writes:
>> > JMarc, can you look? pavel
>>
>> I tried to build from scratch a tex2lyx with monolithic build and had no
>> problem there. OTOH, I cannot build in frontend/qt4 (but I did not find
>> how to fix this).
>
> hmm lately
BH wrote:
On Tue, Apr 14, 2009 at 4:13 AM, Abdelrazak Younes wrote:
rgheck wrote:
Abdelrazak Younes wrote:
As I leaked the highly important news that my wife was pregnant (whatever
JMarc says), I'd thought I should announce formally that this state of
affair finally led to a sm
Martin Vermeer wrote:
On Mon, 13 Apr 2009 23:41:36 +0200
Abdelrazak Younes wrote:
As I leaked the highly important news that my wife was pregnant
(whatever JMarc says), I'd thought I should announce formally that this
state of affair finally led to a small cute little guy named Amir :-)
T
Waluyo Adi Siswanto wrote:
On Mon, 2009-04-13 at 23:41 +0200, Abdelrazak Younes wrote:
As I leaked the highly important news that my wife was pregnant
(whatever JMarc says), I'd thought I should announce formally that this
state of affair finally led to a small cute little guy named Amir :-)
>> I don't see a way to use this with the AtPoint LyXAction flag. I
>> either have to revert this, or discard the use of this argument.
>
>Sorry, I probably missed one of your messages, could you tell me
>again why they cannot be used together? Is that a technical problem
>or a UI problem?
This
On Monday 13 April 2009 22:41:36 Abdelrazak Younes wrote:
> As I leaked the highly important news that my wife was pregnant
> (whatever JMarc says), I'd thought I should announce formally that this
> state of affair finally led to a small cute little guy named Amir :-)
> The mother (Aya) is doing v
Abdelrazak Younes wrote:
> As I leaked the highly important news that my wife was pregnant (whatever
> JMarc says), I'd thought I should announce formally that this state of
> affair finally led to a small cute little guy named Amir :-)
> The mother (Aya) is doing very well.
>
> I guess this also
On Mon, 13 Apr 2009 23:41:36 +0200
Abdelrazak Younes wrote:
> As I leaked the highly important news that my wife was pregnant
> (whatever JMarc says), I'd thought I should announce formally that this
> state of affair finally led to a small cute little guy named Amir :-)
> The mother (Aya) is d
Jean-Marc Lasgouttes wrote:
> Pavel Sanda writes:
> > JMarc, can you look? pavel
>
> I tried to build from scratch a tex2lyx with monolithic build and had no
> problem there. OTOH, I cannot build in frontend/qt4 (but I did not find
> how to fix this).
hmm lately i haven't seen any problem. do yo
On Tue, Apr 14, 2009 at 4:13 AM, Abdelrazak Younes wrote:
> rgheck wrote:
>>
>> Abdelrazak Younes wrote:
>>>
>>> As I leaked the highly important news that my wife was pregnant (whatever
>>> JMarc says), I'd thought I should announce formally that this state of
>>> affair finally led to a small cu
On Mon, 2009-04-13 at 23:41 +0200, Abdelrazak Younes wrote:
> As I leaked the highly important news that my wife was pregnant
> (whatever JMarc says), I'd thought I should announce formally that this
> state of affair finally led to a small cute little guy named Amir :-)
> The mother (Aya) is doi
"Vincent van Ravesteijn - TNW" writes:
> So, do you have any ideas what to do with the argument of inset-settings
> ? The only place where this is used is the Edit menu, e.g.
> 'inset-settings note'
This version with argument is useful AFAIK to have a personalized menu
entry "Note Settings...". I
On 2009-04-13, Vincent van Ravesteijn wrote:
>> Another solution would be a kind of "implicit" label, that doesn't
>> actually surface in LyX at all. Every section-type entity, and maybe
>> other things, too---figures, tables, etc---could have an "implicit"
>> label which would get generated w
>> 2. the status of LFUN_INSET_SETTINGS is handled by
>> BufferView::getStatus() and the dispatch is handled by
>> Text::dispatch(). This looks at least a bit awkward. Shouldn't these
>> be handled by the same class ?
>
>Why not all of them in the relevant inset class?
>
>> 3. when Text::dispatch
Uwe Stöhr writes:
> Jean-Marc Lasgouttes schrieb:
>
>> I need more information.
>
> Try to import the attached one. This works with LyX 1.6.2 but not with
> 1.6.3svn and 2.0svn.
Uwe, did you make any progress on this bug?
JMarc
Pavel Sanda writes:
> JMarc, can you look? pavel
I tried to build from scratch a tex2lyx with monolithic build and had no
problem there. OTOH, I cannot build in frontend/qt4 (but I did not find
how to fix this).
JMarc
Abdelrazak Younes writes:
> How is your wife doing?
Tired!
JMarc
Jean-Marc Lasgouttes wrote:
Abdelrazak Younes writes:
As I leaked the highly important news that my wife was pregnant
(whatever JMarc says), I'd thought I should announce formally that
this state of affair finally led to a small cute little guy named Amir
:-)
I never said that your wi
Abdelrazak Younes wrote:
> As I leaked the highly important news that my wife was pregnant
> (whatever JMarc says), I'd thought I should announce formally that this
> state of affair finally led to a small cute little guy named Amir :-)
> The mother (Aya) is doing very well.
>
> I guess this also m
Abdelrazak Younes writes:
> As I leaked the highly important news that my wife was pregnant
> (whatever JMarc says), I'd thought I should announce formally that
> this state of affair finally led to a small cute little guy named Amir
> :-)
I never said that your wife was not pregnant!
That said
rgheck writes:
> The labels can be output only if they're referenced. That might need
> some kind of double pass, but I'll bet the reference cache could be
> used for this purpose already.
I guess validate() can take care of that.
JMarc
48 matches
Mail list logo
