I am trying to support a command with argument for run-in headings: It
produces a small vertical skip without indent and then writes the text
in the argument in a bold font. Is it possible to mimic this behavior
in LyX? I experimented with the LabelType Manual directive but could
not get it
Marcus Kriele wrote:
I also ran into various problems with tex2lyx when I tried to import
tex-documents with LaTeX-commands that use required or optional
arguments and that are supported in the layout. Are such problems well
known or should I file a bug report?
Such problems are not known
I am trying to support a command with argument for run-in headings: It
produces a small vertical skip without indent and then writes the text
in the argument in a bold font. Is it possible to mimic this behavior
in LyX? I experimented with the LabelType Manual directive but could
not get it to
Thanks!
I have filed a bug (#7468) for those cases where there should be
support from the layout file. I believe that the layout was known to
tex2lyx since the created LyX document used formatting that I had
defined in the same layout file.
Marcus
I am trying to support a command with argument for run-in headings: It
produces a small vertical skip without indent and then writes the text
in the argument in a bold font. Is it possible to mimic this behavior
in LyX? I experimented with the "LabelType Manual" directive but could
not get
Marcus Kriele wrote:
> I also ran into various problems with tex2lyx when I tried to import
> tex-documents with LaTeX-commands that use required or optional
> arguments and that are supported in the layout. Are such problems well
> known or should I file a bug report?
Such problems are not
I am trying to support a command with argument for run-in headings: It
produces a small vertical skip without indent and then writes the text
in the argument in a bold font. Is it possible to mimic this behavior
in LyX? I experimented with the "LabelType Manual" directive but could
not get it
Thanks!
I have filed a bug (#7468) for those cases where there should be
support from the layout file. I believe that the layout was known to
tex2lyx since the created LyX document used formatting that I had
defined in the same layout file.
Marcus
jean-marc wrote:
Currently, listings reuses ERT (?) to handle spaces. We could of course
decide to have a new parameter to alloz multiple normal space. Even
better, we could use \obeyspaces in LyX-Code to make normal spaces
work like ~. This would solve many problems IMO (but create
jean-marc wrote:
> Currently, listings reuses ERT (?) to handle spaces. We could of course
> decide to have a new parameter to alloz multiple normal space. Even
> better, we could use \obeyspaces in LyX-Code to make normal spaces
> work like ~. This would solve many problems IMO (but create
i am fiddling with a layout i'm trying to put together
i want to define an environment that contains plain text.
i have the following
Style Stata-Log
LatexType Environment
LatexName stlog
FreeSpacing true
KeepEmpty
leuven edwin wrote:
i am fiddling with a layout i'm trying to put together
i want to define an environment that contains plain text.
i have the following
Style Stata-Log
LatexType Environment
LatexName stlog
FreeSpacing true
richard wrote:
~ is the only way to preserve multiple spaces in LaTeX.
i don't think so, it depends on the environment. listings for example preserves
multiple spaces.
what i am after is listings type behavior, but using Style instead of
InsetLayout and for that i don't want the ~ nor the
leuven edwin wrote:
richard wrote:
~ is the only way to preserve multiple spaces in LaTeX.
i don't think so, it depends on the environment. listings for example preserves
multiple spaces.
I see.
what i am after is listings type behavior, but using Style instead of
rgheck rgh...@bobjweil.com writes:
At the moment, I'm not sure we can do that in a normal environment
(i.e., not in an inset). But there's no reason we couldn't.
Currently, listings reuses ERT (?) to handle spaces. We could of course
decide to have a new parameter to alloz multiple normal
Jean-Marc Lasgouttes wrote:
rgheck rgh...@bobjweil.com writes:
At the moment, I'm not sure we can do that in a normal environment
(i.e., not in an inset). But there's no reason we couldn't.
Currently, listings reuses ERT (?) to handle spaces. We could of course
decide to have a new
rgheck rgh...@bobjweil.com writes:
Some alternative to the current ~ would be nice. Using ~ means, of
course, that LaTeX has all kinds of problems with linebreaks if you
try to use FreeSpacing in lines of any width.
OTOH, some people are used to LyX-Code breaking lines and would not
unhappy to
i am fiddling with a layout i'm trying to put together
i want to define an environment that contains plain text.
i have the following
Style Stata-Log
LatexType Environment
LatexName stlog
FreeSpacing true
KeepEmpty
leuven edwin wrote:
i am fiddling with a layout i'm trying to put together
i want to define an environment that contains plain text.
i have the following
Style Stata-Log
LatexType Environment
LatexName stlog
FreeSpacing true
richard wrote:
> ~ is the only way to preserve multiple spaces in LaTeX.
i don't think so, it depends on the environment. listings for example preserves
multiple spaces.
what i am after is listings type behavior, but using Style instead of
InsetLayout and for that i don't want the ~ nor the
leuven edwin wrote:
richard wrote:
~ is the only way to preserve multiple spaces in LaTeX.
i don't think so, it depends on the environment. listings for example preserves
multiple spaces.
I see.
what i am after is listings type behavior, but using Style instead of
rgheck writes:
> At the moment, I'm not sure we can do that in a normal environment
> (i.e., not in an inset). But there's no reason we couldn't.
Currently, listings reuses ERT (?) to handle spaces. We could of course
decide to have a new parameter to alloz multiple normal
Jean-Marc Lasgouttes wrote:
rgheck writes:
At the moment, I'm not sure we can do that in a normal environment
(i.e., not in an inset). But there's no reason we couldn't.
Currently, listings reuses ERT (?) to handle spaces. We could of course
decide to have a new
rgheck writes:
> Some alternative to the current ~ would be nice. Using ~ means, of
> course, that LaTeX has all kinds of problems with linebreaks if you
> try to use FreeSpacing in lines of any width.
OTOH, some people are used to LyX-Code breaking lines and would not
On Tue, 31 Jul 2007, Paul A. Rubin wrote:
That makes sense, unless you can create an upload area readable by all
but writable only by the developers. As far as my tweaked layouts go,
they won't be official until Juergen folds them into a subsequent
release, at which point the wiki copies
On Tue, 31 Jul 2007, Paul A. Rubin wrote:
That makes sense, unless you can create an upload area readable by all
but writable only by the developers. As far as my tweaked layouts go,
they won't be official until Juergen folds them into a subsequent
release, at which point the wiki copies
On Mon, 30 Jul 2007, Paul A. Rubin wrote:
[EMAIL PROTECTED] wrote:
As a side note, it's perfectly possible to add an enhancement request to
bugzilla, post a tweaked layout to bugzilla, and then refer to the tweaked
layout in bugzilla from within a wiki page. Not sure if it helps, but it
[EMAIL PROTECTED] wrote:
Your approach is valid, but somewhat unsafe as others may alter your
layout with no reasonable trace. Yes, this is a drawback with the
current system, but difficult to do something about.
Well, if you're worrying about there being untrustworthy LyXers out
there,
On Mon, 30 Jul 2007, Paul A. Rubin wrote:
[EMAIL PROTECTED] wrote:
As a side note, it's perfectly possible to add an enhancement request to
bugzilla, post a tweaked layout to bugzilla, and then refer to the tweaked
layout in bugzilla from within a wiki page. Not sure if it helps, but it
[EMAIL PROTECTED] wrote:
Your approach is valid, but somewhat unsafe as others may alter your
layout with no reasonable trace. Yes, this is a drawback with the
current system, but difficult to do something about.
Well, if you're worrying about there being untrustworthy LyXers out
there,
[EMAIL PROTECTED] wrote:
As a side note, it's perfectly possible to add an enhancement request to
bugzilla, post a tweaked layout to bugzilla, and then refer to the
tweaked layout in bugzilla from within a wiki page. Not sure if it
helps, but it will keep the tweaked layout together with the
[EMAIL PROTECTED] wrote:
As a side note, it's perfectly possible to add an enhancement request to
bugzilla, post a tweaked layout to bugzilla, and then refer to the
tweaked layout in bugzilla from within a wiki page. Not sure if it
helps, but it will keep the tweaked layout together with the
José Matos wrote:
On Sunday 15 July 2007 22:06:10 Paul A. Rubin wrote:
If some kind developer would test these and then commit them if
appropriate, I would be obliged. If you'd prefer diff files, that could
probably be arranged. Sorry for the web links, but I tried posting this
through GMANE
On Sun, 29 Jul 2007, Paul A. Rubin wrote:
José Matos wrote:
On Sunday 15 July 2007 22:06:10 Paul A. Rubin wrote:
If some kind developer would test these and then commit them if
appropriate, I would be obliged. If you'd prefer diff files, that could
probably be arranged. Sorry for the
José Matos wrote:
On Sunday 15 July 2007 22:06:10 Paul A. Rubin wrote:
If some kind developer would test these and then commit them if
appropriate, I would be obliged. If you'd prefer diff files, that could
probably be arranged. Sorry for the web links, but I tried posting this
through GMANE
On Sun, 29 Jul 2007, Paul A. Rubin wrote:
José Matos wrote:
On Sunday 15 July 2007 22:06:10 Paul A. Rubin wrote:
> If some kind developer would test these and then commit them if
> appropriate, I would be obliged. If you'd prefer diff files, that could
> probably be arranged. Sorry for
On Sunday 15 July 2007 22:06:10 Paul A. Rubin wrote:
If some kind developer would test these and then commit them if
appropriate, I would be obliged. If you'd prefer diff files, that could
probably be arranged. Sorry for the web links, but I tried posting this
through GMANE with zip
On Sunday 15 July 2007 22:06:10 Paul A. Rubin wrote:
>
> If some kind developer would test these and then commit them if
> appropriate, I would be obliged. If you'd prefer diff files, that could
> probably be arranged. Sorry for the web links, but I tried posting this
> through GMANE with zip
Hi,
Before I put this is in as an enhancement request, I wanted to make sure
it doesn't already exist. I know you can define counters in a layout
function. Is there a mechanism to specify, say when defining a section
style, that certain counters get reset at the start of the section? If
Paul A. Rubin wrote:
Hi,
Before I put this is in as an enhancement request, I wanted to make
sure it doesn't already exist. I know you can define counters in a
layout function. Is there a mechanism to specify, say when defining a
section style, that certain counters get reset at the start
On Sun, Jul 15, 2007 at 09:59:32AM -0400, Paul A. Rubin wrote:
Hi,
Before I put this is in as an enhancement request, I wanted to make sure it
doesn't already exist. I know you can define counters in a layout function.
Is there a mechanism to specify, say when defining a section
Martin Vermeer wrote:
On Sun, Jul 15, 2007 at 09:59:32AM -0400, Paul A. Rubin wrote:
Hi,
Before I put this is in as an enhancement request, I wanted to make sure it
doesn't already exist. I know you can define counters in a layout function.
Is there a mechanism to specify, say when
Hi,
Before I put this is in as an enhancement request, I wanted to make sure
it doesn't already exist. I know you can define counters in a layout
function. Is there a mechanism to specify, say when defining a section
style, that certain counters get reset at the start of the section? If
Paul A. Rubin wrote:
Hi,
Before I put this is in as an enhancement request, I wanted to make
sure it doesn't already exist. I know you can define counters in a
layout function. Is there a mechanism to specify, say when defining a
section style, that certain counters get reset at the start
On Sun, Jul 15, 2007 at 09:59:32AM -0400, Paul A. Rubin wrote:
> Hi,
>
> Before I put this is in as an enhancement request, I wanted to make sure it
> doesn't already exist. I know you can define counters in a layout function.
> Is there a mechanism to specify, say when defining a section
Martin Vermeer wrote:
On Sun, Jul 15, 2007 at 09:59:32AM -0400, Paul A. Rubin wrote:
Hi,
Before I put this is in as an enhancement request, I wanted to make sure it
doesn't already exist. I know you can define counters in a layout function.
Is there a mechanism to specify, say when
46 matches
Mail list logo