On Thu, 10 Jan 2008, Jean-Marc Lasgouttes wrote:
[EMAIL PROTECTED] writes:
As you say, alphabetical sort can be done through a script later.
However, this is also true for a thematical order - we could place a
category tag in each entry and then sort according to that tag. E.g.
LFUN-t
[EMAIL PROTECTED] writes:
> As you say, alphabetical sort can be done through a script later.
> However, this is also true for a thematical order - we could place a
> category tag in each entry and then sort according to that tag. E.g.
>
> LFUN-type = Cursor Movement
We already have this in
On Tue, 8 Jan 2008, Pavel Sanda wrote:
My hope is that by referring to the sections I mentioned above, we
don't feel it is necessary to sort them now. (If we do sort them, I
think they should be sorted alphabetically).
either sort it thematically or let it be. the alphabetical sort in the
fi
> I'm not familiar with doxygen, so just look at the example at the end as
> something intended to illustrate what I mean. Basically I suggest allowing
> the LFUN enums to be unsorted, but let the documentation of the LFUN refer
> to small documentation sections that describe the category to whi
On Mon, 7 Jan 2008, rgheck wrote:
Yes, that was the idea: that when we auto-generate the doxygen stuff,
we'll get a nicely organized output.
I'm no expert with doxygen, so I'll let you and Pavel figure out if this
is workable.
I'm no expert either, but I don't mind learning to use doxygen -
On Mon, 7 Jan 2008, Pavel Sanda wrote:
If so, couldn't that be done in some other way? What if we just add
for instance a documentation section describing 'word-right',
'word-left', 'word-...' and then for the definition of 'word-right' etc
, we refer to that section.
i dont follow you exac
> If so, couldn't that be done in some other way? What if we just add for
> instance a documentation section describing 'word-right', 'word-left',
> 'word-...' and then for the definition of 'word-right' etc , we refer to
> that section.
i dont follow you exactly. can you show a code example o
[EMAIL PROTECTED] wrote:
On Mon, 7 Jan 2008, Richard Heck wrote:
The code numbers in lfuns.h will be a pain if we're trying to keep
the list organized.
What was the reason for re-arranging the LFUNs? Better/nicer
documentation?
If so, couldn't that be done in some other way? What if we ju
On Mon, 7 Jan 2008, Richard Heck wrote:
The code numbers in lfuns.h will be a pain if we're trying to keep the
list organized.
What was the reason for re-arranging the LFUNs? Better/nicer
documentation?
If so, couldn't that be done in some other way? What if we just add for
instance a doc
Andre Poenitz wrote:
On Mon, Jan 07, 2008 at 09:31:58AM +0100, Abdelrazak Younes wrote:
Jürgen Spitzmüller wrote:
Pavel Sanda wrote:
i also wonder whats the meaning of number-counting of the lfuns.
does anybody use it or can it be deleted too ?
I use it. It's very help
On Mon, Jan 07, 2008 at 09:31:58AM +0100, Abdelrazak Younes wrote:
> Jürgen Spitzmüller wrote:
>> Pavel Sanda wrote:
>>> i also wonder whats the meaning of number-counting of the lfuns.
>>> does anybody use it or can it be deleted too ?
>> I use it. It's very helpful for debugging.
>
> Are you sure
Abdelrazak Younes wrote:
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
For this use case a translation to the LFUN command string would be
more
suited.
Probably. But I see no need to break what we have (the question was
if the numbers should be deleted).
If we are to put some order i
Am 07.01.2008 um 09:45 schrieb Jürgen Spitzmüller:
Abdelrazak Younes wrote:
Are you sure GDB won't directly gives the enum value? I think it did
last time I used that many years ago... Do you use it at the shell or
within some visual frontend?
I don't think of gdb, but of debugging using LyX
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
For this use case a translation to the LFUN command string would be more
suited.
Probably. But I see no need to break what we have (the question was if the
numbers should be deleted).
If we are to put some order in the LFUN, the numbers wil
Abdelrazak Younes wrote:
> For this use case a translation to the LFUN command string would be more
> suited.
Probably. But I see no need to break what we have (the question was if the
numbers should be deleted).
Jürgen
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
Are you sure GDB won't directly gives the enum value? I think it did
last time I used that many years ago... Do you use it at the shell or
within some visual frontend?
I don't think of gdb, but of debugging using LyX's -dbg output. Usually, th
> I don't think of gdb, but of debugging using LyX's -dbg output. Usually, the
> numbers are output there and are helpful especially to debug dispatch
> procedures (also in user's reports).
you are right, the numbers should stay there.
pavel
Abdelrazak Younes wrote:
> Are you sure GDB won't directly gives the enum value? I think it did
> last time I used that many years ago... Do you use it at the shell or
> within some visual frontend?
I don't think of gdb, but of debugging using LyX's -dbg output. Usually, the
numbers are output th
Jürgen Spitzmüller wrote:
Pavel Sanda wrote:
i also wonder whats the meaning of number-counting of the lfuns.
does anybody use it or can it be deleted too ?
I use it. It's very helpful for debugging.
Are you sure GDB won't directly gives the enum value? I think it did
last time I used that
Pavel Sanda wrote:
> i also wonder whats the meaning of number-counting of the lfuns.
> does anybody use it or can it be deleted too ?
I use it. It's very helpful for debugging.
Jürgen
Pavel Sanda wrote:
order, too. Are there opinions on how that should be done---viz.,
alphabetically, thematically, ???
i would vote for thematical (re)grouping
i also wonder whats the meaning of number-counting of the lfuns.
does anybody use it or can it be deleted too ?
The only use
> order, too. Are there opinions on how that should be done---viz.,
> alphabetically, thematically, ???
i would vote for thematical (re)grouping
i also wonder whats the meaning of number-counting of the lfuns.
does anybody use it or can it be deleted too ?
pavel
The LFUNs in lfun.h are, from what I can tell, in no particular order.
Now that we're doxyfying them, it seems as if some sensible order would
be worth having, so that the generated documentation would have a
sensible order, too. Are there opinions on how that should be
done---viz., alphabeti
23 matches
Mail list logo
