chr == chr [EMAIL PROTECTED] writes:
chr Anyway, although I also feel that the documentation should
chr (eventually) be stored in the source, I can see why now is not a
chr good time for that.
I think basically that you should not wait for us :)
chr I assume Gunter and I can pepper the
On 10.06.05, Lars Gullik Bjønnes wrote:
G. Milde [EMAIL PROTECTED] writes:
| IMHO, it would be easier the other way round (put the info into
| LyXAction in the first place).
| - { LFUN_ACUTE, accent-acute, Noop },
| + { LFUN_ACUTE, accent-acute, Noop, , },
this is
On 13.06.05, [EMAIL PROTECTED] wrote:
On Sun, 12 Jun 2005, Lars Gullik Bjønnes wrote:
But we don't want that kind of documentation for lfuns, we want
documentation that is accesible from inside lyx.
IMHO, we need both, a short description for tooltips or the status line
and a full
On 13.06.05, G. Milde wrote:
On 10.06.05, Lars Gullik Bjønnes wrote:
G. Milde [EMAIL PROTECTED] writes:
| IMHO, it would be easier the other way round (put the info into
| LyXAction in the first place).
| - { LFUN_ACUTE, accent-acute, Noop },
| + { LFUN_ACUTE,
On Mon, 13 Jun 2005, G. Milde wrote:
But we don't want that kind of documentation for lfuns, we want
documentation that is accesible from inside lyx.
IMHO, we need both, a short description for tooltips or the status line
and a full description with markup and links etc.
Sure, but I
Recent wiki posts:
(http://wiki.lyx.org/Main/AllRecentChanges)
* http://wiki.lyx.org/Windows/LyX136pre - 18:59 12/06 by Uwe Sthr
* http://wiki.lyx.org/Windows/LyX136pre - 20:03 12/06 by Uwe Sthr
* http://wiki.lyx.org/Windows/LyX136pre - 20:04 12/06 by Uwe Sthr
*
> "chr" == chr <[EMAIL PROTECTED]> writes:
chr> Anyway, although I also feel that the documentation should
chr> (eventually) be stored in the source, I can see why now is not a
chr> good time for that.
I think basically that you should not wait for us :)
chr> I assume Gunter and I can
On 10.06.05, Lars Gullik Bjønnes wrote:
> "G. Milde" <[EMAIL PROTECTED]> writes:
>
> | IMHO, it would be easier the other way round (put the info into
> | LyXAction in the first place).
> >
> | - { LFUN_ACUTE, "accent-acute", Noop },
> | + { LFUN_ACUTE, "accent-acute", Noop,
On 13.06.05, [EMAIL PROTECTED] wrote:
> On Sun, 12 Jun 2005, Lars Gullik Bjønnes wrote:
> > But we don't want that kind of documentation for lfuns, we want
> > documentation that is accesible from inside lyx.
IMHO, we need both, a short description for tooltips or the status line
and a full
On 13.06.05, G. Milde wrote:
> On 10.06.05, Lars Gullik Bjønnes wrote:
> > "G. Milde" <[EMAIL PROTECTED]> writes:
> >
> > | IMHO, it would be easier the other way round (put the info into
> > | LyXAction in the first place).
> > >
> > | - { LFUN_ACUTE, "accent-acute", Noop },
> > | +
On Mon, 13 Jun 2005, G. Milde wrote:
> > > But we don't want that kind of documentation for lfuns, we want
> > > documentation that is accesible from inside lyx.
>
> IMHO, we need both, a short description for tooltips or the status line
> and a full description with markup and links etc.
>
> >
Recent wiki posts:
(http://wiki.lyx.org/Main/AllRecentChanges)
* http://wiki.lyx.org/Windows/LyX136pre - 18:59 12/06 by Uwe Sthr
* http://wiki.lyx.org/Windows/LyX136pre - 20:03 12/06 by Uwe Sthr
* http://wiki.lyx.org/Windows/LyX136pre - 20:04 12/06 by Uwe Sthr
*
12 matches
Mail list logo
