On 04/25/2013 07:14 PM, Elmar Hinz wrote:
Exporting the markup syntax is a different issue. I can think of a
couple ways to do it. The first, and most involved, would be to
write export routines, in the LyX source itself, similar to the
LyXHTML export routines. Another would be t
> Exporting the markup syntax is a different issue. I can think of a couple
> ways to do it. The first, and most involved, would be to write export
> routines, in the LyX source itself, similar to the LyXHTML export routines.
> Another would be to write some kind of simple converter that would conv
On 2013-04-25, Richard Heck wrote:
> On 04/25/2013 12:05 PM, Elmar Hinz wrote:
>> What I am interested in is customization of LyX for special usecases.
>> That means
>> * reducing features to a defined minimum
>> * setting custom sets of markup
>> * creating exporters for the new markup to new la
On 04/25/2013 12:05 PM, Elmar Hinz wrote:
Hello all,
my name is Elmar and I am new to this list.
What I am interested in is customization of LyX for special usecases.
That means
* reducing features to a defined minimum
* setting custom sets of markup
* creating exporters for the new markup to
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> We are talking about two keystrokes per _session_ (which even
Andre> can be saved by the alias) and adding a dozen lines or so of
Andre> code to the lyx core.
It would be great to be able to reload all files, which cursors at the
On Wed, Feb 06, 2002 at 02:26:20PM +0100, Jean-Marc Lasgouttes wrote:
> Andre> Write a shell alias lyx1='lyx /path/to/your/file.lyx' and start
> Andre> lyx by typing 'lyx1'
>
> Or type M-f 1 when lyx is started. I agree that a pref to do that may
> be useful.
We are talking about two keystrokes
