Am 19.07.2011 um 01:05 schrieb Uwe Stöhr:
Am 19.07.2011 00:05, schrieb Jean-Marc Lasgouttes:
Le 15/07/11 22:30, Uwe Stöhr a écrit :
I don't agree that implementing it as part of the space inset is a good
idea. \textvisiblespace is not a space in the sense of the meaning but a
special
Uwe Stöhr wrote:
I still think it is wrong, but I am not going to fight forever on that
(what is there a space in foo bar and not foo_bar???).
The internal behaviour of a space and a character is different. LaTeX can
change the width of spaces to e.g. fit a line into the column margins.
Uwe Stöhr wrote:
There is the ideal, and there is what we have. The ideal way would be
to ensure that the extra paragraph types for running headers appear if
and only if page layout fancy is checked. Currently, that can't be
done with modules. But at least we have the running headers now,
Op dinsdag 19 juli 2011 00:06:55 schreef Jean-Marc Lasgouttes:
Le 18/07/11 23:58, Cor Blom a écrit :
Adding bc to BuildRequires solved the problem. Thanks for the help.
Interesting, but what does bc stand for?
bc: GNU Command Line Calculator
After your last remark I looked again through
Hi there,
I see that there's a lot of request to help for me in Trac; I would be
very happy to but I am very busy these days...
I am starting a new job in August in Switzerland and I am preparing my
moving to there with the family. So don't expect much from me in the
coming weeks.
Cheers,
Le 19/07/2011 03:21, Uwe Stöhr a écrit :
This doesn't help, because in some cases you need the feature that LyX
does not add nothing, no par break and also no newline but to continue
with the code right after the command.
Looks like a very badly coded macro, then. It might be easier to fix the
Le 19/07/2011 03:34, Uwe Stöhr a écrit :
Great news!
However, can we please for the future use usernames that are
self-explanatory? I mean when I read sanda I know that it is you,
reading cmd is quite meaningless.
It is the privilege of the new developer to pick a user name. cmd is not
Le 19/07/2011 05:54, BH a écrit :
Works well for me -- I use the title bar icon all the time (which can
also be used to reveal the complete path to the file and navigate to
any folder in the path).
Unfortunately, I cannot have only this part, since Qt does not do the
icon thing if I set the
Cor Blom wrote:
bc: GNU Command Line Calculator
After your last remark I looked again through the log and noticed that the
shell complained that bc could not be found. This complaint was not there
in
the buildlog for branch, so I added it as a requirement.
please can you paste the
Jean-Marc Lasgouttes wrote:
Le 19/07/2011 03:34, Uwe Stöhr a écrit :
Great news!
However, can we please for the future use usernames that are
self-explanatory? I mean when I read sanda I know that it is you,
reading cmd is quite meaningless.
It is the privilege of the new developer to pick
Am 19.07.2011 um 10:47 schrieb Pavel Sanda:
Cor Blom wrote:
bc: GNU Command Line Calculator
After your last remark I looked again through the log and noticed that the
shell complained that bc could not be found. This complaint was not there
in
the buildlog for branch, so I added it as
Jean-Marc Lasgouttes wrote:
Attached is a patch that does this.
The advantage is that we avoid confusions. If we would implement it as
InsetSpace, it is hard for the user to distinguish it within LyX from
the other spaces.
Just output it in black instead of blue.
this is already
Jürgen Spitzmüller wrote:
And this is exactly why it makes sense. It's a possibility to represent a
space. Why shouldn't InsetSpace allow for that possibility?
The discussion about glyph classification (technical symbol vs. space) is
completely irrelevant for most users. They might just
Pavel Sanda wrote:
the border of technical symbol vs. space is fuzzy to me and i don't
have hard opinion to dicuss it.
but to sum up as the time passed we have 3 patches:
1. special symbol - simple unicode char
2. part of insetspace
3. special symbol - specific drawing
if my counting is
Uwe Stöhr wrote:
Hi Pavel,
in the page http://wiki.lyx.org/LyX/NewInLyX20 there was the icon that the
initial module is documented. Where is it, I cannot find it?
i put the tickmark of documented feature when the module description inside
settings
dialog is enough to grab all information
Le 19/07/2011 08:41, Jürgen Spitzmüller a écrit :
That's not true for all spaces. Non-break spaces are of fixed width as well.
And so is \thinspace.
[...]
And this is exactly why it makes sense. It's a possibility to represent a
space. Why shouldn't InsetSpace allow for that possibility?
The
Le 19/07/2011 11:55, Pavel Sanda a écrit :
as sidecomment i dont think that adding specific features which pull extra
packages into our manuals is a healthy thing. they are not compilable on
various situations then and produce strange errors like when we added mchem
notion into math manual and
Le 19/07/2011 10:08, Abdelrazak Younes a écrit :
Hi there,
I see that there's a lot of request to help for me in Trac; I would be
very happy to but I am very busy these days...
I am starting a new job in August in Switzerland and I am preparing my
moving to there with the family. So don't
Le 19/07/2011 10:52, Pavel Sanda a écrit :
It is the privilege of the new developer to pick a user name. cmd is not
weirder than gmatht, after all :)
nobody asked me !?@$%!~ ;p
Hmm, maybe at the time the privilege did not exist, then.
On 07/19/2011 11:13 AM, Jean-Marc Lasgouttes wrote:
Have a nice trip.
JMarc
+1 :-)
--
José Matos
On 19/07/2011 12:13, Jean-Marc Lasgouttes wrote:
Le 19/07/2011 10:08, Abdelrazak Younes a écrit :
Hi there,
I see that there's a lot of request to help for me in Trac; I would be
very happy to but I am very busy these days...
I am starting a new job in August in Switzerland and I am preparing
On 19/07/2011 12:13, Jean-Marc Lasgouttes wrote:
Le 19/07/2011 10:08, Abdelrazak Younes a écrit :
Hi there,
I see that there's a lot of request to help for me in Trac; I would be
very happy to but I am very busy these days...
I am starting a new job in August in Switzerland and I am preparing
Op dinsdag 19 juli 2011 10:47:50 schreef Pavel Sanda:
please can you paste the relevant part of log? i have hard time to
understand why we need bc.
Here it is:
[...]
GENui_TocUi.h
GENui_ToggleWarningUi.h
GENui_VSpaceUi.h
GENui_ViewSourceUi.h
GENui_WrapUi.h
On 19/07/2011 13:22, Abdelrazak Younes wrote:
On 19/07/2011 12:13, Jean-Marc Lasgouttes wrote:
Le 19/07/2011 10:08, Abdelrazak Younes a écrit :
Hi there,
I see that there's a lot of request to help for me in Trac; I would be
very happy to but I am very busy these days...
I am starting a new
Am 19.07.2011 10:15, schrieb Jean-Marc Lasgouttes:
This doesn't help, because in some cases you need the feature that LyX
does not add nothing, no par break and also no newline but to continue
with the code right after the command.
Looks like a very badly coded macro, then.
No, these cases
Am 19.07.2011 11:55, schrieb Pavel Sanda:
in the page http://wiki.lyx.org/LyX/NewInLyX20 there was the icon that the
initial module is documented. Where is it, I cannot find it?
i put the tickmark of documented feature when the module description inside
settings
dialog is enough to grab all
Le 19/07/2011 13:22, Abdelrazak Younes a écrit :
Thinking about it, my family will be on holidays between the 5th and the
12th of August. So my new appartment will be empty (except for the still
unpacked stuff of course).
Is there interest in a LyX meeting during the week-end between the 5th
Le 19/07/2011 13:47, Uwe Stöhr a écrit :
No, these cases occur often. They are also not badly coded but
standard and valid LaTeX that commands affect the paragraph they are in.
What typical examples do you have in mind?
JMarc
Le 19/07/2011 13:47, Uwe Stöhr a écrit :
Yes, it should be done eventually, and it is not very difficult.
However, I think it would be better
to factor in the two cases, rather then duplicating code (with subtly
different bugs :)
Will you do this or is this something for Richard? Should I open
Am 19.07.2011 14:23, schrieb Jean-Marc Lasgouttes:
Le 19/07/2011 13:47, Uwe Stöhr a écrit :
No, these cases occur often. They are also not badly coded but
standard and valid LaTeX that commands affect the paragraph they are in.
What typical examples do you have in mind?
Pictures in
Le 19/07/2011 14:28, Uwe Stöhr a écrit :
Pictures in paragraphs (e.g. via picins, picinpar), wrapped floats,
initials, email commands, address formatting commands, various
scientific paper titling commands, ...
Most of these are indeed part of a paragraph an thus should be handled
by custom
Am 19.07.2011 14:38, schrieb Jean-Marc Lasgouttes:
Most of these are indeed part of a paragraph an thus should be handled by
custom insets. There is no
point to change normal layouts for them.
Yes, we already agree here. The only pint is that InsetLayout (a.k.a. flex inset) does not yet
Am 19.07.2011 um 11:05 schrieb Stephan Witt:
Am 19.07.2011 um 10:47 schrieb Pavel Sanda:
Cor Blom wrote:
bc: GNU Command Line Calculator
After your last remark I looked again through the log and noticed that the
shell complained that bc could not be found. This complaint was not there
On 07/19/2011 01:17 AM, Uwe Stöhr wrote:
Richard,
am I allowed to remove the file enumitem.lyx from branch too? Its
content is now in the UserGuide.
My goal was to merge all these infos into one place because before we
described customized lists in the Additional manual and the enumitem
On 07/19/2011 08:25 AM, Jean-Marc Lasgouttes wrote:
Le 19/07/2011 13:47, Uwe Stöhr a écrit :
Yes, it should be done eventually, and it is not very difficult.
However, I think it would be better
to factor in the two cases, rather then duplicating code (with subtly
different bugs :)
Will you
Le 17/07/2011 12:02, Pavel Sanda a écrit :
Uwe Stöhr wrote:
section 7.2.1: sentence
Before you begin to use the version control features in LyX, you should
be
familiar with RCS/CVS/SVN usage before start using it under LyX.
Indeed. I removed this now.
the wording maybe wrong in terms of
Am 19.07.2011 15:08, schrieb Richard Heck:
I'm still hoping to do some major reworking of how arguments are
handled, i.e., get rid of that inset.
What do you have in mind instead? I have now a lot of experience with it and find the current
implementation acceptable, except of these 2 things:
On 07/19/2011 09:58 AM, Uwe Stöhr wrote:
Am 19.07.2011 15:08, schrieb Richard Heck:
I'm still hoping to do some major reworking of how arguments are
handled, i.e., get rid of that inset.
What do you have in mind instead? I have now a lot of experience with
it and find the current
Richard Heck wrote:
- the menu entry must read optional Argument, not short title (this
is misleading and this appears often at the users list that people are
confused, a short title is only ONE occurrence of optional arguments
It's much less clear how you can label different insets
Abdelrazak Younes wrote:
Is there interest in a LyX meeting during the week-end between the 5th and
the 7th? I will leave in a very nice area close to Lausanne 5 minutes walk
very unprobable i will have spare time during this summer...
isn't Juergen the swiss layman now as well?
pavel
Pavel Sanda wrote:
Is there interest in a LyX meeting during the week-end between the 5th
and the 7th? I will leave in a very nice area close to Lausanne 5
minutes walk
very unprobable i will have spare time during this summer...
isn't Juergen the swiss layman now as well?
Yep (in
Am 19.07.2011 16:38, schrieb Richard Heck:
- the menu entry must read optional Argument, not short title (this
is misleading and this appears often at the users list that people are
confused, a short title is only ONE occurrence of optional arguments
It's much less clear how you can label
On 07/19/2011 12:54 PM, Uwe Stöhr wrote:
Am 19.07.2011 16:38, schrieb Richard Heck:
- the menu entry must read optional Argument, not short title (this
is misleading and this appears often at the users list that people are
confused, a short title is only ONE occurrence of optional arguments
Am 19.07.2011 19:33, schrieb Richard Heck:
I understand the idea, but it would make the Bibitem mess look neat.
What do you mean?
- the optional argument can sty as it is, only its menu entry in the
Insert menu must be changed.
There can be more than one optional argument. Think about
Am 19.07.2011 12:11, schrieb Jean-Marc Lasgouttes:
PS: BTW Uwe, did you see my messages about the \LyX macro? Since r37164 it is
robust under hyperref
and it is not necessary to redefine it in preamble.
Not yes. Thanks for the hint, I'll remove the corresponding preamble code now.
regards
Am 19.07.2011 08:14, schrieb Stephan Witt:
Sorry, I cannot resist... Notepad is not an editor. It's an excuse for not
having one.
Every time I have to view a file on stock windows I get an attack of windows
hate.
It's the same with the never ending newline story.
One should at least use
Am 19.07.2011 08:41, schrieb Jürgen Spitzmüller:
And this is exactly why it makes sense. It's a possibility to represent a
space. Why shouldn't InsetSpace allow for that possibility?
It is totally confusing that we have the menu Insert-Special character that already provides the
char. OK,
On 07/19/2011 01:49 PM, Uwe Stöhr wrote:
Am 19.07.2011 19:33, schrieb Richard Heck:
I understand the idea, but it would make the Bibitem mess look neat.
What do you mean?
The InsetBibitem code is a complete disaster. There are all kinds of
bugs associated with it, because we are trying to
Le 19/07/11 19:57, Uwe Stöhr a écrit :
PS: BTW Uwe, did you see my messages about the \LyX macro? Since
r37164 it is robust under hyperref
and it is not necessary to redefine it in preamble.
Not yes. Thanks for the hint, I'll remove the corresponding preamble
code now.
Of course don't forget
Am 20.07.2011 00:02, schrieb Jean-Marc Lasgouttes:
Of course don't forget to doublecheck that it works (it is in 2.0 too).
I always compile every file as PDF before committing. This should btw. the
default procedure.
(The only exception are the Japanese files because I don't have ptex.)
Jürgen Spitzmüller wrote:
Pavel Sanda wrote:
the border of technical symbol vs. space is fuzzy to me and i don't
have hard opinion to dicuss it.
but to sum up as the time passed we have 3 patches:
1. special symbol - simple unicode char
2. part of insetspace
3. special symbol -
Stephan Witt wrote:
In case of interest
QT_VERSION=4.10.3 sh -c 'v=0x0; for i in ${QT_VERSION//./ } ; do case $i
in 10) v=$v0a ;; 11) v=$v0b ;; 12) v=$v0c ;; 13) v=$v0d ;; 14)
v=$v0e ;; 15) v=$v0f ;; *) v=$v0$i ;; esac ; done; echo $v'
prints 0x0040a03
how do cmake people solve this in
Jean-Pierre Chrétien wrote:
Le 17/07/2011 12:02, Pavel Sanda a écrit :
Uwe Stöhr wrote:
section 7.2.1: sentence
Before you begin to use the version control features in LyX, you should
be
familiar with RCS/CVS/SVN usage before start using it under LyX.
Indeed. I removed this now.
the
Jean-Marc Lasgouttes wrote:
(and I'd prefer SVN/CVS/RCS to Version Control),
then perhaps Version Control(SVN/CVS/RCS) in order to know what you are running.
also readonly flag is needed to be displayed somewhere.
pavel
... so i returned to this ...
Uwe Stöhr wrote:
I now wrote its documentation from scratch and saw that your module did not
work.
it depends what you mean by works. if you just insert charstyle push character
there and start writing after charstyle inset it 'just works' (at least here).
you
Uwe Stöhr wrote:
Our manuals have to describe what you can do with LyX. There is no other
way. It might always be possible that our docs are uncompilable. We cannot
control what LaTeX-packages are installed on a system. Or where do you want
to set the line?
i dont have any fixed rule but
On Tue, Jul 19, 2011 at 6:13 PM, Jean-Marc Lasgouttes lasgout...@lyx.orgwrote:
Le 19/07/2011 10:52, Pavel Sanda a écrit :
It is the privilege of the new developer to pick a user name. cmd is not
weirder than gmatht, after all :)
nobody asked me !?@$%!~ ;p
Hmm, maybe at the time the
Am 20.07.2011 03:32, schrieb Pavel Sanda:
I now wrote its documentation from scratch and saw that your module did not
work.
it depends what you mean by works. if you just insert charstyle push character
there and start writing after charstyle inset it 'just works' (at least here).
By
Am 20.07.2011 03:45, schrieb Pavel Sanda:
Uwe Stöhr wrote:
Our manuals have to describe what you can do with LyX. There is no other
way. It might always be possible that our docs are uncompilable. We cannot
control what LaTeX-packages are installed on a system. Or where do you want
to set the
Am 20.07.2011 06:06, schrieb Uwe Stöhr:
Attached is an example where you get a LaTeX error.
Here it is.
regards Uwe
newfile1.lyx
Description: application/lyx
Am 19.07.2011 um 01:05 schrieb Uwe Stöhr:
> Am 19.07.2011 00:05, schrieb Jean-Marc Lasgouttes:
>
>> Le 15/07/11 22:30, Uwe Stöhr a écrit :
>>> I don't agree that implementing it as part of the space inset is a good
>>> idea. \textvisiblespace is not a space in the sense of the meaning but a
>>>
Uwe Stöhr wrote:
> > I still think it is wrong, but I am not going to fight forever on that
> > (what is there a space in "foo bar" and not "foo_bar"???).
>
> The internal behaviour of a space and a character is different. LaTeX can
> change the width of spaces to e.g. fit a line into the column
Uwe Stöhr wrote:
> > There is the ideal, and there is what we have. The "ideal" way would be
> > to ensure that the extra paragraph types for running headers appear if
> > and only if page layout "fancy" is checked. Currently, that can't be
> > done with modules. But at least we have the running
Op dinsdag 19 juli 2011 00:06:55 schreef Jean-Marc Lasgouttes:
> Le 18/07/11 23:58, Cor Blom a écrit :
> > Adding bc to BuildRequires solved the problem. Thanks for the help.
>
> Interesting, but what does bc stand for?
>
bc: GNU Command Line Calculator
After your last remark I looked again
Hi there,
I see that there's a lot of request to help for me in Trac; I would be
very happy to but I am very busy these days...
I am starting a new job in August in Switzerland and I am preparing my
moving to there with the family. So don't expect much from me in the
coming weeks.
Cheers,
Le 19/07/2011 03:21, Uwe Stöhr a écrit :
This doesn't help, because in some cases you need the feature that LyX
does not add nothing, no par break and also no newline but to continue
with the code right after the command.
Looks like a very badly coded macro, then. It might be easier to fix the
Le 19/07/2011 03:34, Uwe Stöhr a écrit :
Great news!
However, can we please for the future use usernames that are
self-explanatory? I mean when I read "sanda" I know that it is you,
reading "cmd" is quite meaningless.
It is the privilege of the new developer to pick a user name. cmd is not
Le 19/07/2011 05:54, BH a écrit :
Works well for me -- I use the title bar icon all the time (which can
also be used to reveal the complete path to the file and navigate to
any folder in the path).
Unfortunately, I cannot have only this part, since Qt does not do the
icon thing if I set the
Cor Blom wrote:
> bc: GNU Command Line Calculator
>
> After your last remark I looked again through the log and noticed that the
> shell complained that "bc" could not be found. This complaint was not there
> in
> the buildlog for branch, so I added it as a requirement.
please can you paste
Jean-Marc Lasgouttes wrote:
> Le 19/07/2011 03:34, Uwe Stöhr a écrit :
>> Great news!
>> However, can we please for the future use usernames that are
>> self-explanatory? I mean when I read "sanda" I know that it is you,
>> reading "cmd" is quite meaningless.
>
> It is the privilege of the new
Am 19.07.2011 um 10:47 schrieb Pavel Sanda:
> Cor Blom wrote:
>> bc: GNU Command Line Calculator
>>
>> After your last remark I looked again through the log and noticed that the
>> shell complained that "bc" could not be found. This complaint was not there
>> in
>> the buildlog for branch, so
Jean-Marc Lasgouttes wrote:
>> Attached is a patch that does this.
>>
>> The advantage is that we avoid confusions. If we would implement it as
>> InsetSpace, it is hard for the user to distinguish it within LyX from
>> the other spaces.
>
> Just output it in black instead of blue.
this is
Jürgen Spitzmüller wrote:
> And this is exactly why it makes sense. It's a possibility to represent a
> space. Why shouldn't InsetSpace allow for that possibility?
>
> The discussion about glyph classification ("technical symbol" vs. "space") is
> completely irrelevant for most users. They
Pavel Sanda wrote:
> the border of "technical symbol" vs. "space" is fuzzy to me and i don't
> have hard opinion to dicuss it.
>
> but to sum up as the time passed we have 3 patches:
> 1. special symbol - simple unicode char
> 2. part of insetspace
> 3. special symbol - specific drawing
>
> if
Uwe Stöhr wrote:
> Hi Pavel,
>
> in the page http://wiki.lyx.org/LyX/NewInLyX20 there was the icon that the
> initial module is documented. Where is it, I cannot find it?
i put the tickmark of documented feature when the module description inside
settings
dialog is enough to grab all
Le 19/07/2011 08:41, Jürgen Spitzmüller a écrit :
That's not true for all spaces. Non-break spaces are of fixed width as well.
And so is \thinspace.
[...]
And this is exactly why it makes sense. It's a possibility to represent a
space. Why shouldn't InsetSpace allow for that possibility?
The
Le 19/07/2011 11:55, Pavel Sanda a écrit :
as sidecomment i dont think that adding specific features which pull extra
packages into our manuals is a healthy thing. they are not compilable on
various situations then and produce strange errors like when we added mchem
notion into math manual and
Le 19/07/2011 10:08, Abdelrazak Younes a écrit :
Hi there,
I see that there's a lot of request to help for me in Trac; I would be
very happy to but I am very busy these days...
I am starting a new job in August in Switzerland and I am preparing my
moving to there with the family. So don't
Le 19/07/2011 10:52, Pavel Sanda a écrit :
It is the privilege of the new developer to pick a user name. cmd is not
weirder than gmatht, after all :)
nobody asked me !?@$%!~ ;p
Hmm, maybe at the time the privilege did not exist, then.
On 07/19/2011 11:13 AM, Jean-Marc Lasgouttes wrote:
Have a nice trip.
JMarc
+1 :-)
--
José Matos
On 19/07/2011 12:13, Jean-Marc Lasgouttes wrote:
Le 19/07/2011 10:08, Abdelrazak Younes a écrit :
Hi there,
I see that there's a lot of request to help for me in Trac; I would be
very happy to but I am very busy these days...
I am starting a new job in August in Switzerland and I am preparing
On 19/07/2011 12:13, Jean-Marc Lasgouttes wrote:
Le 19/07/2011 10:08, Abdelrazak Younes a écrit :
Hi there,
I see that there's a lot of request to help for me in Trac; I would be
very happy to but I am very busy these days...
I am starting a new job in August in Switzerland and I am preparing
Op dinsdag 19 juli 2011 10:47:50 schreef Pavel Sanda:
> please can you paste the relevant part of log? i have hard time to
> understand why we need bc.
Here it is:
[...]
GENui_TocUi.h
GENui_ToggleWarningUi.h
GENui_VSpaceUi.h
GENui_ViewSourceUi.h
GENui_WrapUi.h
On 19/07/2011 13:22, Abdelrazak Younes wrote:
On 19/07/2011 12:13, Jean-Marc Lasgouttes wrote:
Le 19/07/2011 10:08, Abdelrazak Younes a écrit :
Hi there,
I see that there's a lot of request to help for me in Trac; I would be
very happy to but I am very busy these days...
I am starting a new
Am 19.07.2011 10:15, schrieb Jean-Marc Lasgouttes:
This doesn't help, because in some cases you need the feature that LyX
does not add nothing, no par break and also no newline but to continue
with the code right after the command.
Looks like a very badly coded macro, then.
No, these cases
Am 19.07.2011 11:55, schrieb Pavel Sanda:
in the page http://wiki.lyx.org/LyX/NewInLyX20 there was the icon that the
initial module is documented. Where is it, I cannot find it?
i put the tickmark of documented feature when the module description inside
settings
dialog is enough to grab all
Le 19/07/2011 13:22, Abdelrazak Younes a écrit :
Thinking about it, my family will be on holidays between the 5th and the
12th of August. So my new appartment will be empty (except for the still
unpacked stuff of course).
Is there interest in a LyX meeting during the week-end between the 5th
Le 19/07/2011 13:47, Uwe Stöhr a écrit :
No, these cases occur often. They are also not "badly coded" but
standard and valid LaTeX that commands affect the paragraph they are in.
What typical examples do you have in mind?
JMarc
Le 19/07/2011 13:47, Uwe Stöhr a écrit :
Yes, it should be done eventually, and it is not very difficult.
However, I think it would be better
to factor in the two cases, rather then duplicating code (with subtly
different bugs :)
Will you do this or is this something for Richard? Should I open
Am 19.07.2011 14:23, schrieb Jean-Marc Lasgouttes:
Le 19/07/2011 13:47, Uwe Stöhr a écrit :
No, these cases occur often. They are also not "badly coded" but
standard and valid LaTeX that commands affect the paragraph they are in.
What typical examples do you have in mind?
Pictures in
Le 19/07/2011 14:28, Uwe Stöhr a écrit :
Pictures in paragraphs (e.g. via picins, picinpar), wrapped floats,
initials, email commands, address formatting commands, various
scientific paper titling commands, ...
Most of these are indeed part of a paragraph an thus should be handled
by custom
Am 19.07.2011 14:38, schrieb Jean-Marc Lasgouttes:
Most of these are indeed part of a paragraph an thus should be handled by
custom insets. There is no
point to change normal layouts for them.
Yes, we already agree here. The only pint is that InsetLayout (a.k.a. flex inset) does not yet
Am 19.07.2011 um 11:05 schrieb Stephan Witt:
> Am 19.07.2011 um 10:47 schrieb Pavel Sanda:
>
>> Cor Blom wrote:
>>> bc: GNU Command Line Calculator
>>>
>>> After your last remark I looked again through the log and noticed that the
>>> shell complained that "bc" could not be found. This
On 07/19/2011 01:17 AM, Uwe Stöhr wrote:
> Richard,
>
> am I allowed to remove the file enumitem.lyx from branch too? Its
> content is now in the UserGuide.
> My goal was to merge all these infos into one place because before we
> described customized lists in the Additional manual and the
On 07/19/2011 08:25 AM, Jean-Marc Lasgouttes wrote:
> Le 19/07/2011 13:47, Uwe Stöhr a écrit :
>>> Yes, it should be done eventually, and it is not very difficult.
>>> However, I think it would be better
>>> to factor in the two cases, rather then duplicating code (with subtly
>>> different bugs
Le 17/07/2011 12:02, Pavel Sanda a écrit :
Uwe Stöhr wrote:
section 7.2.1: sentence
"Before you begin to use the version control features in LyX, you should
be
familiar with RCS/CVS/SVN usage before start using it under LyX."
Indeed. I removed this now.
the wording maybe wrong in terms of
Am 19.07.2011 15:08, schrieb Richard Heck:
I'm still hoping to do some major reworking of how arguments are
handled, i.e., get rid of that inset.
What do you have in mind instead? I have now a lot of experience with it and find the current
implementation acceptable, except of these 2 things:
On 07/19/2011 09:58 AM, Uwe Stöhr wrote:
> Am 19.07.2011 15:08, schrieb Richard Heck:
>
>> I'm still hoping to do some major reworking of how arguments are
>> handled, i.e., get rid of that inset.
>
> What do you have in mind instead? I have now a lot of experience with
> it and find the current
Richard Heck wrote:
> > - the menu entry must read "optional Argument, not "short title" (this
> > is misleading and this appears often at the users list that people are
> > confused, a short title is only ONE occurrence of optional arguments
>
> It's much less clear how you can label different
Abdelrazak Younes wrote:
> Is there interest in a LyX meeting during the week-end between the 5th and
> the 7th? I will leave in a very nice area close to Lausanne 5 minutes walk
very unprobable i will have spare time during this summer...
isn't Juergen the swiss layman now as well?
pavel
1 - 100 of 120 matches
Mail list logo
