On 24/09/2008 01:44, Uwe Stöhr wrote:
Our session handling is incorrect and can break LyX completely:
http://bugzilla.lyx.org/show_bug.cgi?id=5274
(It took me a lot of time to find a workaround to get LyX usable
again, so I think this should be fixed before rc3 is released.)
Are you aware tha
On 24/09/2008 00:25, Uwe Stöhr wrote:
In the preferences there is under Look & Feel the option "Open
documents in tabs". But when I uncheck it and restart LyX, the docs
are still opened in tabs. What is this option supposed to be?
The option doesn't work at restart. Otherwise, it works: it 'Op
Pavel Sanda wrote:
Richard Heck wrote:
G Milde wrote:
On the other side would be a "wizard" like layout-creator with
drop-down and selection lists (like the citation insert dialogue) for
GUI creation of layouts without exposure to the syntax. (However, I
would not call this an editor --
> this patch will sort anything in outliner automatically.
> sort won't be correct for nonascii characters.
This is what I meant, please apply. That it doesn't sort non-ASCII characters in the right order is
no problem as you are only one or two entries away in the worst case, but this is even b
Jack M. Lyon wrote:
> Dear Revered LyX Developers:
>
> I wrote you earlier today about displaying the List of Index Entries in the
> Document Outline. Lo and behold, you've already done this in LyX 6.0. Thanks
> very much!
>
> Now one other (hopefully) small request:
>
> Can you please make it p
>> -
>> -
>> +{ LFUN_LISTINGS_TAB_INSERT, "listings-tab-insert",
SingleParUpdate,
>> +Edit },
>
>maybe we can use LFUN_TAB_INSERT, so we can re-use it somewhere else
when needed?
>
Is possible..
>> +/*!
>> + * \var lyx::FuncCode lyx::LFUN_LISTINGS_TAB_DELETE
>> + * \li Action: Delete
Vincent van Ravesteijn wrote:
> -
> -
> + { LFUN_LISTINGS_TAB_INSERT, "listings-tab-insert",
> SingleParUpdate, Edit },
maybe we can use LFUN_TAB_INSERT, so we can re-use it somewhere else when
needed?
> +/*!
> + * \var lyx::FuncCode lyx::LFUN_LISTINGS_TAB_DELETE
> + * \li Action: D
> This is not new. 1.5 has it as well (I think even 1.4).
Yes this exists since LyX 1.4.0. I missed this until now.
> And it's documented in Extended.lyx 3.1.2.
I updated this section now a bit and reference it in the UserGuide.
Btw. while doing this, I stumbled over the following problem: LyX
Vincent van Ravesteijn wrote:
Vincent van Ravesteijn wrote:
>
> PS. I still used the 'old' LFUNs, I didn't want to stir the patch too
> much.. so small steps at a time (changing the LFUNs is not a large
> change to this patch).
>
An attempt to add two LFUNs for tabbing is Listings. If you like t
Vincent van Ravesteijn wrote:
PS. I still used the 'old' LFUNs, I didn't want to stir the patch too
much.. so small steps at a time (changing the LFUNs is not a large
change to this patch).
An attempt to add two LFUNs for tabbing is Listings. If you like the
names (I'm never that good in think
Pavel Sanda wrote:
Vincent van Ravesteijn - TNW wrote:
> Here it is. It allows :
> -inserting tabs,
> -removing tabs and spacing by backtab,
> -copying code with tabs from other applications.
Vincent, have you worked on this lately? if we want to have it in
before rc3,
the time is
On Wed, Sep 24, 2008 at 09:48:36PM +0200, Vincent van Ravesteijn wrote:
> Well, I wasn't that clear, but all attempts failed until I came across
> the following :
>
> //private:
>/// the anchor position
>DocIterator anchor_;
> Now, I understand why somebody has commented out the private
Andre Poenitz wrote:
On Wed, Sep 24, 2008 at 09:11:19PM +0200, Vincent van Ravesteijn - TNW wrote:
How can I modify the anchor position of a selection ?
void InsetListings::doDispatch(Cursor & cur, FuncRequest & cmd)
{
++cur.anchor().pos()
}
Or something like this..
In the follo
Richard Heck schrieb:
Why do you have to explain them simply to use them?
Imagine you are a rather new or average LyXer and read the docs because you are interested in the
different features. You surely want to know what the black boxes are for. When you found it out, you
surely also want to
On Wed, Sep 24, 2008 at 09:11:19PM +0200, Vincent van Ravesteijn - TNW wrote:
> How can I modify the anchor position of a selection ?
>
> void InsetListings::doDispatch(Cursor & cur, FuncRequest & cmd)
> {
> ++cur.anchor().pos()
> }
>
> Or something like this..
>
>
> In the following cod
Hello,
I think I found one more graphic bug in LyX 1.6.0rc2. If you insert a
graphic and the graphic file extension contains upper case (like
graphic.PNG) LyX will gave me an error. If the graphic file extension
contains lower case (graphic.png) there is no problem creating an
output.
Maybe this
Richard Heck wrote:
> G Milde wrote:
>> On the other side would be a "wizard" like layout-creator with
>> drop-down and selection lists (like the citation insert dialogue) for
>> GUI creation of layouts without exposure to the syntax. (However, I
>> would not call this an editor -- hence my alterna
On Wed, Sep 24, 2008 at 2:46 PM, Stefan Schimanski <[EMAIL PROTECTED]> wrote:
> now the questions:
>> 1. complete was replaced by complete-accept.
>> (complete is trying to complete in the way bash do after tab -
>> find the longest common prefix from the current on.)
>> is there some disagreem
How can I modify the anchor position of a selection ?
void InsetListings::doDispatch(Cursor & cur, FuncRequest & cmd)
{
++cur.anchor().pos()
}
Or something like this..
In the following code, shouldn't we return a const CursorSlice and/or
document that the returned CursorSlice isn't the
Uwe Stöhr wrote:
rgheck schrieb:
Well, if you're going to leave InsetInfo until after 1.6, we can do
this together. You can tell me what character styles you want, and
I'll produce definitions of them that you can use.
This wouldn't help. What we need is a way to define your own character
s
Uwe Stöhr wrote:
rgheck schrieb:
You can see from the diff itself, more or less, what I did.
Yes, but that costs me some time since diffs doesn't read well.
Telling me the changed sections would be enough. I will then read them
find out the differences according to the diff.
I also added
Pavel Sanda wrote:
Uwe Stöhr wrote:
But to use it for the docs I miss the possibility to customize
InsetInfo's output. In the docs, menu names and shortcuts are in sans
serif, icons have a uniform size of 80%. So I need a way to specify the
output of the different InsetInfo types for the cu
as we have brand new lfun for alternative lfuns to be bound to
certain key
we should decide what to do with tab key:
to sum up for people not involved in lengthy discussions:
tab bindings:
1.5 state: used for tables and math arrays
rc2 state: used for completion (complete lfun)
new proposal o
hi,
as we have brand new lfun for alternative lfuns to be bound to certain key
we should decide what to do with tab key:
to sum up for people not involved in lengthy discussions:
tab bindings:
1.5 state: used for tables and math arrays
rc2 state: used for completion (complete lfun)
new propos
Pavel Sanda wrote:
Vincent van Ravesteijn - TNW wrote:
> Here it is. It allows :
> -inserting tabs,
> -removing tabs and spacing by backtab,
> -copying code with tabs from other applications.
Vincent, have you worked on this lately? if we want to have it in
before rc3,
the time is
> The latter (e.g. "song"). It's the second mandatory argument of the CJK
> environment.
Thanks Jürgen for you quick reply. I added this info to th docs.
regards Uwe
Vincent van Ravesteijn - TNW wrote:
> Here it is. It allows :
> -inserting tabs,
> -removing tabs and spacing by backtab,
> -copying code with tabs from other applications.
Vincent, have you worked on this lately? if we want to have it in before rc3,
the time is short :)
pavel
rgheck schrieb:
Well, if you're going to leave InsetInfo until after 1.6, we can do this
together. You can tell me what character styles you want, and I'll
produce definitions of them that you can use.
This wouldn't help. What we need is a way to define your own character styles. That means t
rgheck schrieb:
You can see from the diff itself, more or less, what I did.
Yes, but that costs me some time since diffs doesn't read well. Telling me the changed sections
would be enough. I will then read them find out the differences according to the diff.
I also added a little bit
to th
Uwe Stöhr wrote:
>>> But to use it for the docs I miss the possibility to customize
>>> InsetInfo's output. In the docs, menu names and shortcuts are in sans
>>> serif, icons have a uniform size of 80%. So I need a way to specify the
>>> output of the different InsetInfo types for the current do
Uwe Stöhr wrote:
rgheck schrieb:
But to use it for the docs I miss the possibility to customize
InsetInfo's output. In the docs, menu names and shortcuts are in
sans serif, icons have a uniform size of 80%. So I need a way to
specify the output of the different InsetInfo types for the current
Uwe Stöhr wrote:
Hello Richard,
thanks for your documentation update. But I need to keep the diferent
language versions in sync. So could you please tell me what you
changed in what sections when you update the docs. I can then update
the other language versions or tell the translators.
So
rgheck schrieb:
But to use it for the docs I miss the possibility to customize
InsetInfo's output. In the docs, menu names and shortcuts are in sans
serif, icons have a uniform size of 80%. So I need a way to specify
the output of the different InsetInfo types for the current document.
Can'
Uwe Stöhr wrote:
> Everything is explained in src/insets/InsetInfo.h,
So it is well hidden ;-)
Why is there no GUI? I mean the users will see this inset in the
documentation files and ask how to use it and what it is for.
It's not really meant for ordinary users, I don't think. It gives you
On Wed, 24 Sep 2008, Uwe Brauer wrote:
>>> Correct. It converts wiki (via XML, then LaTeX) to PDF. Please
>>> note that allowing plain, arbitrary LaTeX to be parsed on an open
>>> wiki is a security risk.
>>
>> why is this so, what a pity that would be ideal for collaboration.
> To
Hello Richard,
thanks for your documentation update. But I need to keep the diferent language versions in sync. So
could you please tell me what you changed in what sections when you update the docs. I can then
update the other language versions or tell the translators.
(The French, Japanese,
Why is there no GUI? I mean the users will see this inset in the
documentation files and ask how to use it and what it is for. So
InstInfo should at least be described in the Extended or Customization manual.
Could you do this please?
> Everything is explained in src/insets/InsetInfo.h,
So it is well hidden ;-)
Why is there no GUI? I mean the users will see this inset in the documentation files and ask how to
use it and what it is for. So InstInfo should at least be described in the
> 1. input the type and argument of thi
> Can you please make it possible to sort the index entries in Document
> Outline alphabetically? It would make all the difference in the world to a
> serious indexer.
I fully agree with you. Without a sorting for index entries, labels, etc., the outliner is quite
useless for larger documents. T
On Wednesday 24 September 2008 16:08:47 [EMAIL PROTECTED] wrote:
> Jose: Once the bindings have been sorted out, that will complete the work
> on this we said we wanted to do for rc3.
OK, thanks for taking care of this issue. :-)
--
José Abílio
This has now been committed. Next issue is the bindings. There ought to
be other places we can use this, too, no?
rh
leuven edwin wrote:
bind-sequence
I'll go with command-alternatives, if only because it stays in the
command-* family.
rh
bind-sequence
?
rgheck <[EMAIL PROTECTED]> writes:
> Maybe the former?
I'll let you use your great wisdom to pick one.
JMarc
Dear Revered LyX Developers:
I wrote you earlier today about displaying the List of Index Entries in the
Document Outline. Lo and behold, you've already done this in LyX 6.0. Thanks
very much!
Now one other (hopefully) small request:
Can you please make it possible to sort the index entries in D
Richard Heck wrote:
> So I propose just to commit what I've got
i agree with this.
call + command-sequence allows to work around it.
pavel
Jean-Marc Lasgouttes wrote:
rgheck <[EMAIL PROTECTED]> writes:
All those are great ideas, but none of them are things I have time to
do. ;-) The current proposal is minimally invasive, and this kind of
change is very much so. So I propose just to commit what I've got, and
if we want to change
Richard Heck wrote:
> In the current system, yes. But a better system would display something
> like "Tab (alt)" for those things. This is because the shortcut dialog also
> functions as information: How do I get ?
this could be solved by new additional column with some flag, that this is
al
rgheck <[EMAIL PROTECTED]> writes:
> All those are great ideas, but none of them are things I have time to
> do. ;-) The current proposal is minimally invasive, and this kind of
> change is very much so. So I propose just to commit what I've got, and
> if we want to change the syntax we can do that
Richard Heck wrote:
> Well, complete isn't always enabled---not in the middle of a word---but
> it's almost always enabled, so you do have this problem.
in fact i don't have this problem, since i use completion-accept ;)
it seems we both agree upon this solution, but i would like to listen
others
Pavel Sanda wrote:
Richard Heck wrote:
+\bind "Tab""alternatives completion-accept; cell-forward"
really good approach
I've have a quick go at this. The patch is attached.
These alternative bindings don't show quite right in the shortcut editor.
(Try typing "com
Jean-Marc Lasgouttes wrote:
rgheck <[EMAIL PROTECTED]> writes:
But if we used a different delimiter?
Or accept
alternative command-sequence foo \; bar ; baz
Or ... [snip]
All those are great ideas, but none of them are things I have time to
do. ;-) The current proposal is min
Richard Heck wrote:
>>> +\bind "Tab""alternatives completion-accept; cell-forward"
really good approach
> I've have a quick go at this. The patch is attached.
>
> These alternative bindings don't show quite right in the shortcut editor.
> (Try typing "comp" in the search box.) But p
rgheck <[EMAIL PROTECTED]> writes:
> But if we used a different delimiter?
Or accept
alternative command-sequence foo \; bar ; baz
Or extend command-sequence and alternative to use a syntax like
command-sequence "foo" "bar"
alternative "command-sequence \"foo\" \"bar\"" "baz"
(this la
> But if we used a different delimiter?
that would've been my next question...
Jean-Marc Lasgouttes wrote:
leuven edwin <[EMAIL PROTECTED]> writes:
is it possible to put a command sequence among the alternatives?
No... Our syntax is a bit weak. But you can "call" a macro in there.
But if we used a different delimiter?
rh
leuven edwin <[EMAIL PROTECTED]> writes:
> is it possible to put a command sequence among the alternatives?
No... Our syntax is a bit weak. But you can "call" a macro in there.
JMarc
is it possible to put a command sequence among the alternatives?
rgheck <[EMAIL PROTECTED]> writes:
> I've have a quick go at this. The patch is attached.
Looks good.
JMarc
Jean-Marc Lasgouttes wrote:
G Milde <[EMAIL PROTECTED]> writes:
* or an alternative keyword (similar to the command-sequence)
+\bind "Tab""alternatives completion-accept; cell-forward"
Excellent idea. I see the advantages to this proposal.
+1
This strikes me as a m
I noticed that the errorlist (for chktex in this case) does not work at
all like I intended. When I click on the items one by one, the
description that appears does not match what I want. Instrumenting
GuiErrorList::select() with lyxerr shows that the index used by this
function does not match wha
Pavel Sanda wrote:
Richard Heck wrote:
I guess I saw this the other way around: BOTH completion AND next-cell
should work in tables.
and both bound to tab?
Yes. And this does work if what's bound is completion-accept. If you
bind it to complete, then it works much less well.
Othe
Uwe Stöhr <[EMAIL PROTECTED]> writes:
> Jean-Marc Lasgouttes schrieb:
>
>> I have a question of my own too: do you have plans to use InsetInfo in
>> the docs?
>
> How can I insert an InsetInfo, there is no menu entry for this? Where should
> I use it?
Everything is explained in src/insets/InsetI
Jean-Marc Lasgouttes wrote:
rgheck <[EMAIL PROTECTED]> writes:
My testing has made it seem pretty intuitive to me. You're typing
along, you get a completion suggested, and you hit Tab. If no
completion is being suggested, then Tab takes you to the next cell.
Now, for sure, the details here de
G Milde wrote:
On the other side would be a "wizard" like layout-creator with
drop-down and selection lists (like the citation insert dialogue) for
GUI creation of layouts without exposure to the syntax. (However, I
would not call this an editor -- hence my alternative suggestion.)
A "wizard"
Uwe Stöhr wrote:
Jean-Marc Lasgouttes schrieb:
I have a question of my own too: do you have plans to use InsetInfo in
the docs?
How can I insert an InsetInfo, there is no menu entry for this?
That I do not know either (I always copied from elsewhere), but there
should be an LFUN for it.
Jean-Marc Lasgouttes schrieb:
I have a question of my own too: do you have plans to use InsetInfo in
the docs?
How can I insert an InsetInfo, there is no menu entry for this? Where should I
use it?
regards Uwe
Bennett Helm schrieb:
See bug 4906:
Thanks for the hint.
regards Uwe
Richard Heck wrote:
> I guess I saw this the other way around: BOTH completion AND next-cell
> should work in tables.
and both bound to tab?
> Otherwise, you, the user, have to remember that
> completion has no binding in tables. This is very unintuitive, and it is
> especially nasty with mat
>>>
>>> Correct. It converts wiki (via XML, then LaTeX) to PDF. Please
>>> note that allowing plain, arbitrary LaTeX to be parsed on an open
>>> wiki is a security risk.
>>
>> why is this so, what a pity that would be ideal for collaboration.
> To which of the above parts do
Enrico Forestieri <[EMAIL PROTECTED]> schrieb:
> You managed to convice me. With the attached patch, the unicode accented
> characters are interpreted as math variables when they are entered in
> mathmode. Please test.
Thanks for your work.
Unfortunately, I did not have the time to compile a pat
Uwe Stöhr <[EMAIL PROTECTED]> writes:
> In order to finish the documentation update for LyX 1.6.0 there are
> have several features that I haven't fully understood or no idea how
> they are used. So I'll come up with some questions, here's the first
> one:
I have a question of my own too: do you h
rgheck <[EMAIL PROTECTED]> writes:
> This one:
>\bind "~S-ISO_Left_Tab""cell-backward"
> I found an old thread involving John Levon and lgb about this, but I'm
> not sure whether we now need it. It's causing a bit of a problem in
> the shortcuts dialog, because KeySequence::print(), which
G Milde <[EMAIL PROTECTED]> writes:
> * or an alternative keyword (similar to the command-sequence)
>
> +\bind "Tab""alternatives completion-accept; cell-forward"
+1
This strikes me as a much easier solution to implement than multiple
bindings!
JMarc
rgheck <[EMAIL PROTECTED]> writes:
> My testing has made it seem pretty intuitive to me. You're typing
> along, you get a completion suggested, and you hit Tab. If no
> completion is being suggested, then Tab takes you to the next cell.
> Now, for sure, the details here depend upon exactly which LF
rgheck <[EMAIL PROTECTED]> schrieb:
> Here's the latest version of this patch. The main change is that this
> one addresses the issue of the shortcuts dialog. As I've said elsewhere,
> the dialog in its current state simply can't deal with the binding of
> multiple LFUNs to one key. My solution
Andre Poenitz <[EMAIL PROTECTED]> schrieb:
> On Tue, Sep 23, 2008 at 07:24:17AM +, G Milde wrote:
>> Andre Poenitz <[EMAIL PROTECTED]> schrieb:
>> > On Mon, Sep 22, 2008 at 08:48:46PM +0200, Pavel Sanda wrote:
>> >> it would be possible for me to lead lyx layout editor as a small
>> >> school
77 matches
Mail list logo
