Andre Poenitz wrote:
On Fri, Oct 05, 2007 at 12:24:45AM +0200, Bernhard Roider wrote:
hello all,
the attached patch adds
- the possibility to define macros in the bind file, like
\define "my macro" "command-sequence inset-insert ert 1; char-backward;
self-insert some important latex code; cha
Andre Poenitz wrote:
On Thu, Oct 04, 2007 at 09:19:04PM +0200, Andre Poenitz wrote:
I am looking for a way to solve the "controller problem".
[...]
Hm, with all the fuss about insets and ranges, any comment on that?
I think that what we call "controllers" are really just abstraction
layers
Edwin Leuven wrote:
Uwe Stöhr wrote:
- Why do the dialogs look fine on my system and not on yours?
didn't look at it closely, but i think that you put a lot of stuff in
hboxlayouts and then widgets won't always align nicely in a grid. to
achieve this best to position the widgets and them put
John Levon wrote:
On Fri, Oct 05, 2007 at 12:06:50AM +0300, Martin Vermeer wrote:
_Especially_ from the writing process viewpoint you should appreciate
the ease with which you can undo things in the inset paradigm. Regret an
applied emphasis? Put the cursor inside and dissolve. No need to
caref
Please do not commit anything for the time being. I'm trying to set up the
release.
Thanks,
Jürgen
On Fri, Oct 05, 2007 at 07:15:39AM +0100, John Levon wrote:
> > Not if the chunk is larger than you'd might expect.
>
> You're tying yourself up in knots precisely because you won't do the
> right thing: delete the character in front of the cursor.
No. I usually want to delete entities when there
On Fri, Oct 05, 2007 at 07:09:56AM +0100, John Levon wrote:
> On Fri, Oct 05, 2007 at 08:05:22AM +0200, Andre Poenitz wrote:
>
> > > Well indeed. This makes me somewhat dubious that your experience is
> > > relevant. I'm not anti-inset in any way where they make sense, and I
> > > think the branch
I am currently getting tons of spam like that to my [EMAIL PROTECTED]
address.
Is there some spam filtering set up?
I don't really use this address so I guess I could sent those mails to
the bitbucket as well if there is no filtering.
Andre'
- Forwarded message from johan ximenes <[EMAIL P
John Levon wrote:
On Thu, Oct 04, 2007 at 09:28:25PM +0300, Martin Vermeer wrote:
Could you list the advantages of an exposed inset UI?
1) You know precisely where a typed character goes -- or where an
already typed character belongs. Inside or outside any given inset.
A special case of this i
On Fri, Oct 05, 2007 at 06:52:41AM +0300, Martin Vermeer wrote:
> On Thu, Oct 04, 2007 at 11:22:01PM +0200, Andre Poenitz wrote:
> > On Fri, Oct 05, 2007 at 12:09:11AM +0300, Martin Vermeer wrote:
> > > > Almost! A text with many charstyles is now much easier to read.
> > > >
> > > > The only thin
On Fri, Oct 05, 2007 at 08:12:28AM +0200, Andre Poenitz wrote:
> > > > > The only thing I could ask for here, is to see the borders also when
> > > > > the cursor is right in front of the inset, because the "delete" key
> > > > > will delete the entire inset if used at that point. That is obvious
On Fri, Oct 05, 2007 at 01:09:44AM +0100, John Levon wrote:
> On Thu, Oct 04, 2007 at 11:22:01PM +0200, Andre Poenitz wrote:
>
> > > > The only thing I could ask for here, is to see the borders also when
> > > > the cursor is right in front of the inset, because the "delete" key
> > > > will delet
On Fri, Oct 05, 2007 at 08:05:22AM +0200, Andre Poenitz wrote:
> > Well indeed. This makes me somewhat dubious that your experience is
> > relevant. I'm not anti-inset in any way where they make sense, and I
> > think the branches stuff is a great example.
> >
> > I'm somewhat bemused by your com
Uwe Stöhr wrote:
> So why not directly stating that
> an optional parameter is optional?
I agree with Edwin here. We shouldn't do that. The fact that something can
be selected or not indicates clearly enough that it's optional.
Jürgen
On Fri, Oct 05, 2007 at 12:54:28AM +0100, John Levon wrote:
> On Thu, Oct 04, 2007 at 11:16:50PM +0300, Martin Vermeer wrote:
>
> > Branches are not charstyles, of course.
>
> Well indeed. This makes me somewhat dubious that your experience is
> relevant. I'm not anti-inset in any way where they
Martin Vermeer wrote:
> And distorting someone's words is no good guideline for fruitful debate,
> IMHO.
I'm not aware that I distorted it.
Jürgen
Uwe Stöhr wrote:
- Why do the dialogs look fine on my system and not on yours?
didn't look at it closely, but i think that you put a lot of stuff in
hboxlayouts and then widgets won't always align nicely in a grid. to
achieve this best to position the widgets and them put them in a grid layou
On Fri, Oct 05, 2007 at 06:37:05AM +0300, Martin Vermeer wrote:
> > If what Martin means is that *LyX* will have no ambiguity, e.g, when
> > generating latex/XML, then I think that the disambiguation algorithm
> > suggested in this thread
> > http://permalink.gmane.org/gmane.editors.lyx.devel/9
On Fri, Oct 05, 2007 at 06:07:41AM +0100, John Levon wrote:
> On Fri, Oct 05, 2007 at 06:56:25AM +0300, Martin Vermeer wrote:
>
> > > If I type into say a FirstName charstyle in docbook, the blue banner
> > > beneath just over-writes itself. I think it might be because Author is
> > > centered tex
On Fri, Oct 05, 2007 at 06:56:25AM +0300, Martin Vermeer wrote:
> > If I type into say a FirstName charstyle in docbook, the blue banner
> > beneath just over-writes itself. I think it might be because Author is
> > centered text. It doesn't happen after a certain inset size. Anyone else?
>
> Tho
> Is this correct? Has 1.6svn been responsible for loss of data? Or would
> it be safe enough to use on something important?
I would not use any svn version for serious work, unless you really
need some feature.
As of this parameter-editor dialog, I think Edwin can simply transform
the all_params
On Fri, Oct 05, 2007 at 01:08:54AM +0100, John Levon wrote:
>
> If I type into say a FirstName charstyle in docbook, the blue banner
> beneath just over-writes itself. I think it might be because Author is
> centered text. It doesn't happen after a certain inset size. Anyone else?
Thought I fixed
On Thu, Oct 04, 2007 at 11:22:01PM +0200, Andre Poenitz wrote:
> On Fri, Oct 05, 2007 at 12:09:11AM +0300, Martin Vermeer wrote:
> > > Almost! A text with many charstyles is now much easier to read.
> > >
> > > The only thing I could ask for here, is to see the borders also when
> > > the cursor i
On Thu, Oct 04, 2007 at 10:44:48PM +0200, Helge Hafting wrote:
> Martin Vermeer wrote:
> >On Thu, Oct 04, 2007 at 10:42:35AM +0200, Helge Hafting wrote:
> >
> >>Richard Heck wrote:
> >>
> >>>Without meaning to prejudge the question whether CharStyles should be
> >>>insets, here's my list of
On Fri, Oct 05, 2007 at 02:49:47AM +0200, Dov Feldstern wrote:
>
>
> John Levon wrote:
> >On Thu, Oct 04, 2007 at 09:28:25PM +0300, Martin Vermeer wrote:
> >
> Just to complement John's list of advantages for ranges, I'd also like
> to explain why I think the items on Martin's list do not preclu
On Mon, 2007-10-01 at 14:47 +0100, John Levon wrote:
> I just came across this. Is there a bug filed on fixing this UI?
> I'm a bit concerned that new UI isn't getting the review it deserves.
I for one am afraid to try it because I am working only on one very
important document, and I hear too man
On Sun, 2007-09-30 at 12:47 -0400, Richard Heck wrote:
> > Should be easy to solve.
> Can you fix this, Abdel? Unfortunately, I do not have time now, as I'd
> really, really nice if a fix could be included in 1.5.2. I have been
> thinking I need to go back to using 1.4.5.1 myself, this gets so b
On Thu, Oct 04, 2007 at 09:52:52PM -0400, Richard Heck wrote:
> I don't think it was designed to do so. If it should, then that probably
> isn't terribly hard.
I do think it should...
> >BTW, why do the styles appear as CharStyle:foo in the menu?
> >
> This is a consequence of some of Martin'
John Levon wrote:
Copy and paste doesn't seem to carry the style with it.
I don't think it was designed to do so. If it should, then that probably
isn't terribly hard.
BTW, why do the styles appear as CharStyle:foo in the menu?
This is a consequence of some of Martin's recent work, which
Dov Feldstern wrote:
3) No ambiguity about nesting order.
I'm confused about the difference between 2 and 3. They sound like the
same thing: an inset UI enforces, clearly, a hierarchical style tree.
If what Martin means is that *LyX* will have no ambiguity, e.g, when
generating latex/XML, then
John Levon wrote:
On Thu, Oct 04, 2007 at 09:28:25PM +0300, Martin Vermeer wrote:
Just to complement John's list of advantages for ranges, I'd also like
to explain why I think the items on Martin's list do not preclude the
use of ranges:
Could you list the advantages of an exposed inset UI?
Hello Edwin,
I was really talking bullshit yesterday. I need to test things out properly the next time before
raising my voice. I was angry because nothing was working after I updated SVN. In the end your
cleanup was absolutely correct and my further Ui-changes I had im my tree were pointing to
On Thu, Oct 04, 2007 at 11:22:01PM +0200, Andre Poenitz wrote:
> > > The only thing I could ask for here, is to see the borders also when
> > > the cursor is right in front of the inset, because the "delete" key
> > > will delete the entire inset if used at that point. That is obvious if
> > > the
If I type into say a FirstName charstyle in docbook, the blue banner
beneath just over-writes itself. I think it might be because Author is
centered text. It doesn't happen after a certain inset size. Anyone else?
I can see a similar thing during selection too.
Copy and paste doesn't seem to car
I put it in. When everybody encounters any problem with it, please shout.
regards Uwe
On Fri, Oct 05, 2007 at 12:06:50AM +0300, Martin Vermeer wrote:
> _Especially_ from the writing process viewpoint you should appreciate
> the ease with which you can undo things in the inset paradigm. Regret an
> applied emphasis? Put the cursor inside and dissolve. No need to
> carefully select t
On Thu, Oct 04, 2007 at 11:16:50PM +0300, Martin Vermeer wrote:
> Branches are not charstyles, of course.
Well indeed. This makes me somewhat dubious that your experience is
relevant. I'm not anti-inset in any way where they make sense, and I
think the branches stuff is a great example.
I'm some
On Thu, Oct 04, 2007 at 09:28:25PM +0300, Martin Vermeer wrote:
> > Could you list the advantages of an exposed inset UI?
>
> 1) You know precisely where a typed character goes -- or where an
> already typed character belongs. Inside or outside any given inset.
> A special case of this is for bla
On Thu, Oct 04, 2007 at 09:42:09PM +0300, Martin Vermeer wrote:
> > > > Why do we need to nest insets then ? :-P
> > >
> > > Actually I don't think we should (usually). In text, cases where we
> > > want to nest (charstyle) insets ought to be rare, if we have defined
> > > them as sensible semant
On Thu, Oct 04, 2007 at 09:48:33PM +0200, Andre Poenitz wrote:
> And for The Honoured Believers in Single Keystroke Navigation (formerly
> known as The Finger Painting Faction) the multiple "pos 5, range *"
> positions can be collapsed to a single one. A simple boolean preference,
> maybe even tog
See attached.
"only" 48 lines of our code saved (529 remaining)
40365 + 64275 - 78251 = 26389 lines of compiled code saved.
Two intermediate layers (ControlRef and ControlCommand) gone.
We have 50+ of such things, so a by a very crude approximation
one should expect to be able to throw out 24
Andre Poenitz wrote:
Here's an idea, for example: in the status bar, clearly display the
"currently active" character attributes / styles. Or even better, this
could be a very unintrusive check-list of the currently active
attributes, allowing me to also uncheck any attributes that I want to
t
On Fri, Oct 05, 2007 at 12:24:45AM +0200, Bernhard Roider wrote:
> hello all,
>
> the attached patch adds
> - the possibility to define macros in the bind file, like
>
> \define "my macro" "command-sequence inset-insert ert 1; char-backward;
> self-insert some important latex code; char-forward"
hello all,
the attached patch adds
- the possibility to define macros in the bind file, like
\define "my macro" "command-sequence inset-insert ert 1; char-backward; self-insert some important
latex code; char-forward"
- the lfun "call" to execute that macro. this call can be used in key bindi
Helge Hafting wrote:
The only thing I could ask for here, is to see the borders also when
the cursor is right in front of the inset, because the "delete" key
will delete the entire inset if used at that point. That is obvious if
the frame is there, not so if it isn't.
I'd prefer if it didn't do t
Helge Hafting wrote:
Second bug:
I had this:
#\DeclareLyXModule[multicol.sty]{Adds support for text in multiple
columns}{Multicol}
So I expected multicol.sty to load automatically, but no. I had to add
that to "Preamble...EndPreamble" as well. What is the purpose
of having [multicol.sty] in de
On Thu, Oct 04, 2007 at 09:19:04PM +0200, Andre Poenitz wrote:
> I am looking for a way to solve the "controller problem".
> [...]
Hm, with all the fuss about insets and ranges, any comment on that?
Andre'
On Thu, Oct 04, 2007 at 11:09:23PM +0200, Dov Feldstern wrote:
>
>
> Andre Poenitz wrote:
> >On Thu, Oct 04, 2007 at 10:23:25PM +0200, Dov Feldstern wrote:
> >>Andre Poenitz wrote:
> >>>On Thu, Oct 04, 2007 at 12:39:05AM +0200,
> >>>[EMAIL PROTECTED] wrote:
> Andre', could you give an exampl
On Fri, Oct 05, 2007 at 12:09:11AM +0300, Martin Vermeer wrote:
> > Almost! A text with many charstyles is now much easier to read.
> >
> > The only thing I could ask for here, is to see the borders also when
> > the cursor is right in front of the inset, because the "delete" key
> > will delete t
[EMAIL PROTECTED] writes:
>> Yes, I think this is typically a good idea, the kind of idea we
>> should encourage in LyX. Like the break-paragraph-skip lfun that
>> adds a default skip before the paragraph when pressing enter on an
>> empty layout (I am not sure it still works, though). It is a bit
On Thu, Oct 04, 2007 at 10:44:48PM +0200, Helge Hafting wrote:
> Martin Vermeer wrote:
> >On Thu, Oct 04, 2007 at 10:42:35AM +0200, Helge Hafting wrote:
> >
> >>Richard Heck wrote:
> >>
> >>>Without meaning to prejudge the question whether CharStyles should be
> >>>insets, here's my list of
Andre Poenitz wrote:
On Thu, Oct 04, 2007 at 10:23:25PM +0200, Dov Feldstern wrote:
Andre Poenitz wrote:
On Thu, Oct 04, 2007 at 12:39:05AM +0200,
[EMAIL PROTECTED] wrote:
Andre', could you give an example of a case where you'd like the cursor
to stop in between character styles?
Anytime I
On Thu, Oct 04, 2007 at 09:57:27PM +0200, [EMAIL PROTECTED] wrote:
> On Thu, 4 Oct 2007, Abdelrazak Younes wrote:
>
> >What do you mean by extra cursor press? If with the mouse no, I don't
> >mean that. You will have to exit the inset by any means available:
> >Ctrl-i, right-arrow, etc.
>
> I g
On Thu, Oct 04, 2007 at 10:11:27PM +0200, Dov Feldstern wrote:
> Martin Vermeer wrote:
> >On Wed, Oct 03, 2007 at 08:45:07PM +0200, Juergen Spitzmueller wrote:
>
> >>Do you really want to force users to
> >>- dissolve everything,
> >
> >No, the user is doing this to himself. He made an _error_.
On Thu, 4 Oct 2007, Abdelrazak Younes wrote:
What do you mean by extra cursor press? If with the mouse no, I don't
mean that. You will have to exit the inset by any means available:
Ctrl-i, right-arrow, etc.
I guess I belong to the crowd that does not want to have exit or enter
insets. When
Andre Poenitz <[EMAIL PROTECTED]> writes:
> Incidentally, could you please have a look whether there is an rcc on
> your system and how it is named?
It is there, but not on my path.
JMarc
PS: thanks for removing installation of libraries.
On Thu, 4 Oct 2007, Abdelrazak Younes wrote:
Please note that the '\' is kind of difficult to type on e.g. a Swedish
keyboard, it requires 'AltGr-+'. Something that's frequently used sould by
default be mapped to a key that works well on more than english keyboards.
That was just an exmaple
Andre Poenitz <[EMAIL PROTECTED]> writes:
> C-b x C-i gives you a "monolithic" bold x that is traversed in a single
> keystroke.
Yes, but I always forget to do it :)
JMarc
Martin Vermeer wrote:
On Thu, Oct 04, 2007 at 10:42:35AM +0200, Helge Hafting wrote:
Richard Heck wrote:
Without meaning to prejudge the question whether CharStyles should be
insets, here's my list of things that ought to be done if they are
going to stay that way. They are addressed s
On Thu, Oct 04, 2007 at 10:23:25PM +0200, Dov Feldstern wrote:
> Andre Poenitz wrote:
> >On Thu, Oct 04, 2007 at 12:39:05AM +0200,
> >[EMAIL PROTECTED] wrote:
> >>Andre', could you give an example of a case where you'd like the cursor
> >>to stop in between character styles?
> >
> >Anytime I want
On Thu, Oct 04, 2007 at 09:17:32PM +0100, José Matos wrote:
> On Thursday 04 October 2007 21:05:58 Andre Poenitz wrote:
> > Well... then what about
> >
> > emph...strong..
> > emph.strong...
> >
> > This is 1:1 translatable to the structure above _and_ is more robust
> >
Abdelrazak Younes wrote:
Jean-Marc Lasgouttes wrote:
Andre Poenitz
writes:
Insets are straightforward to implement. Font ranges are not.
I recently had a look at our coding rules. "KISS" was and still is
the first item...
Yes, but it should not dictqte the UI (am I repeating myself?)
B
Pavel Sanda wrote:
I have problem with this one:
if (title.empty() && author.empty())
opt += "pdfusetitle,\n "; IMHO we shouldnt do this unless
user decides so.
On Thu, Oct 04, 2007 at 09:11:53PM +0100, José Matos wrote:
> On Thursday 04 October 2007 20:48:33 Andre Poenitz wrote:
> > And for The Honoured Believers in Single Keystroke Navigation (formerly
> > known as The Finger Painting Faction) the multiple "pos 5, range *"
> > positions can be collapsed
Andre Poenitz wrote:
On Thu, Oct 04, 2007 at 09:55:58PM +0200, Dov Feldstern wrote:
[...]
Rather we'd need to store that as something like
...
...
emph
...
...
strong
Hmm, yes, this does describe the structure that I'm thi
Andre Poenitz wrote:
On Thu, Oct 04, 2007 at 12:39:05AM +0200, [EMAIL PROTECTED] wrote:
Andre', could you give an example of a case where you'd like the cursor to
stop in between character styles?
Anytime I want to start typing in one but not the other.
BTW, it's not exactly "one and not th
On Thu, Oct 04, 2007 at 05:23:53PM +0100, John Levon wrote:
> On Thu, Oct 04, 2007 at 06:46:45PM +0300, Martin Vermeer wrote:
>
> > Not very convincing, is it? Most people learn from experience. What
> > would happen here is that they would quickly pick up that -- no, this
> > stuff does not behav
On Thursday 04 October 2007 21:05:58 Andre Poenitz wrote:
> Well... then what about
>
>
> emph...strong..
> emph.strong...
>
>
> This is 1:1 translatable to the structure above _and_ is more robust under
> manual editing.
I find your exchange highly amusing because some
Martin Vermeer wrote:
On Wed, Oct 03, 2007 at 08:45:07PM +0200, Juergen Spitzmueller wrote:
Do you really want to force users to
- dissolve everything,
No, the user is doing this to himself. He made an _error_. The canonical
way to correct an error is to 1) undo it, 2) do it again, this tim
On Thursday 04 October 2007 20:48:33 Andre Poenitz wrote:
> And for The Honoured Believers in Single Keystroke Navigation (formerly
> known as The Finger Painting Faction) the multiple "pos 5, range *"
> positions can be collapsed to a single one. A simple boolean preference,
> maybe even togglable
I tried making a custom inset, and found that
if I don't specify "Font . . . EndFont", then LyX crashes
as soon as I try "Insert->Custom Insets->my inset"
I didn't want to specify a font, I though LyX could use whatever font
that was in effect at the moment. Some cases don't need to
set a font, t
On Thu, Oct 04, 2007 at 09:55:58PM +0200, Dov Feldstern wrote:
> > [...]
> >Rather we'd need to store that as something like
> >
> >
> >
> >
> > ...
> > ...
> > emph
> >
> >
> > ...
> > ...
> > strong
> >
> >
> >
>
> Hmm, yes, t
Andre Poenitz wrote:
On Wed, Oct 03, 2007 at 02:10:09PM +0200, Jean-Marc Lasgouttes wrote:
We define an "attribute precedence" order. Then, we use the following
rules (to be applied when moving from the GUI to non-overlapping
markup) to make sure that at any given position, the
highest-precedenc
On Thu, Oct 04, 2007 at 09:43:44PM +0300, Martin Vermeer wrote:
> On Thu, Oct 04, 2007 at 07:15:18PM +0200, Andre Poenitz wrote:
> > On Thu, Oct 04, 2007 at 06:52:48PM +0300, Martin Vermeer wrote:
> > > On Thu, Oct 04, 2007 at 10:20:43AM +0200, Jean-Marc Lasgouttes wrote:
> > > > Abdelrazak Younes
I am looking for a way to solve the "controller problem".
Actually I really would like to solve that based on gut feelings
but as this is an academical audience I thought we might as well
have on of those mock-up arguments we all enjoy.
So:
The "controller problem" as defined by me is "having t
[EMAIL PROTECTED] wrote:
On Thu, 4 Oct 2007, Abdelrazak Younes wrote:
> No, hence my idea of one word per inset. The fact that there is
more > than one inset will only be visible if the cursor is in or if
you > hover the mouse over it.
What are your criteria for something being a "word"?
Edwin Leuven schrieb:
the behavior of the dialog hasn't changed. the overhang and linespan are
still optional. if they are not checked they are not passed on. i didn't
touch this part of the code.
if you think that changing a label (ie removing the "optional") changes
the behavior of the dialo
On Thu, Oct 04, 2007 at 07:15:18PM +0200, Andre Poenitz wrote:
> On Thu, Oct 04, 2007 at 06:52:48PM +0300, Martin Vermeer wrote:
> > On Thu, Oct 04, 2007 at 10:20:43AM +0200, Jean-Marc Lasgouttes wrote:
> > > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> > >
> > > > Within text the syndrome won
On Thu, Oct 04, 2007 at 05:27:42PM +0100, John Levon wrote:
> On Thu, Oct 04, 2007 at 06:52:48PM +0300, Martin Vermeer wrote:
>
> > > Why do we need to nest insets then ? :-P
> >
> > Actually I don't think we should (usually). In text, cases where we
> > want to nest (charstyle) insets ought to b
[EMAIL PROTECTED] wrote:
On Thu, 4 Oct 2007, Abdelrazak Younes wrote:
What are your criteria for something being a "word"? I.e., does your
approach handle cases like:
"\noun[Peter}'s patch \command{\define}s some new
\program{LyX}-friendly
\command{environtment}s in a \noun{Knuth}ian way"
On Thu, Oct 04, 2007 at 05:03:54PM +0200, [EMAIL PROTECTED] wrote:
> On Thu, 4 Oct 2007, Martin Vermeer wrote:
>
> >Perhaps Andre doesn't suffer fools gladly, in which case I sympathise.
> >Not implying that you're one of those fools, but the refusal by so many
> >on this list to accept a UI par
On Thu, Oct 04, 2007 at 10:23:09AM +0200, Helge Hafting wrote:
...
> Having several cursor positions in front of a word will be
> both confusing and cumbersome to move through. It may not
> be a problem if it happens rarely, but can we be sure of that?
> If charstyles becomes useful & popular, t
On Thu, Oct 04, 2007 at 06:00:36PM +0200, Juergen Spitzmueller wrote:
> Martin Vermeer wrote:
>
> > Most people learn from experience.
>
> "People will get used to it" is not a very good guideline for user interface
> design, and a bad excuse for a specific ui implementation, IMHO.
>
> Jürgen
A
On Thu, Oct 04, 2007 at 05:23:53PM +0100, John Levon wrote:
> On Thu, Oct 04, 2007 at 06:46:45PM +0300, Martin Vermeer wrote:
>
> > Not very convincing, is it? Most people learn from experience. What
> > would happen here is that they would quickly pick up that -- no, this
> > stuff does not behav
I'm trying to build LyX on a machine with a fresh installation of Ubuntu
(something I've never done before).
So far I've done:
$ mkdir -p ~/lyx; cd ~/lyx;
$ svn co svn+ssh://svn.lyx.org/lyx/lyx-devel/trunk lyx-devel
$ cd ~/lyx/lyx-devel; ./autogen.sh
LyX requires automake >= 1.5
$ sud
Hello fellow developers,
Please add me to the lyx development mailing list.
Thank you!
Eric des Courtis
On Thu, Oct 04, 2007 at 10:42:35AM +0200, Helge Hafting wrote:
> Richard Heck wrote:
> >
> >Without meaning to prejudge the question whether CharStyles should be
> >insets, here's my list of things that ought to be done if they are
> >going to stay that way. They are addressed specifically to wha
Martin Vermeer wrote:
> Actually I don't think we should (usually). In text, cases where we
> want to nest (charstyle) insets ought to be rare, if we have defined
> them as sensible semantic units. Over-use of nesting is a sign that
> we maybe haven't.
Why? Some elements might need to be attribut
On Thu, Oct 04, 2007 at 06:54:43PM +0200, Andre Poenitz wrote:
> On Thu, Oct 04, 2007 at 02:28:40PM +0200, Jean-Marc Lasgouttes wrote:
> >
> > make[6]: Entering directory `/local/lasgoutt/devbuild/src/frontends/qt4'
> > echo "" > Resources.qrc
> > find ../../../../lyx-devel/lib/images -name '*.png
On Thu, Oct 04, 2007 at 06:52:48PM +0300, Martin Vermeer wrote:
> On Thu, Oct 04, 2007 at 10:20:43AM +0200, Jean-Marc Lasgouttes wrote:
> > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> >
> > > Within text the syndrome won't be as evident because you
> > > generally only have one depth and not
Uwe Stöhr wrote:
No, this is not the way it works! I implemented that we now use the
wrapfig-package for wrap floats. We can therefore provide two new
parameters. These are optional and after a discussion on the list
(see the one about my Box-patch some days ago) and in bug 3242 I
implemented t
On Thu, 4 Oct 2007, Helge Hafting wrote:
I find mathed usable, and it uses fonts-as-insets.
I too find mathed very useable. But it edits math, not text.
I think text have different needs than math.
I agree. Maybe one difference is that when writing text, I'm ok with not
getting it perfect
Martin Vermeer wrote:
> Most people learn from experience.
"People will get used to it" is not a very good guideline for user interface
design, and a bad excuse for a specific ui implementation, IMHO.
Jürgen
On Thu, Oct 04, 2007 at 09:40:55AM -0400, Neal Becker wrote:
> I find equation entry on lyx rather nice (being a long-time latex user), but
> editing leaves something to be desired. I find it almost impossible to
> mark, cut and paste parts of equations. Almost every time I try, I wind up
> selec
On Thu, Oct 04, 2007 at 02:28:40PM +0200, Jean-Marc Lasgouttes wrote:
>
> make[6]: Entering directory `/local/lasgoutt/devbuild/src/frontends/qt4'
> echo "" > Resources.qrc
> find ../../../../lyx-devel/lib/images -name '*.png' \
> | sed -e 's:../../../../lyx-devel/lib/\(.*\):&:' \
> >> Res
I've asked Steve and received a reply off-list, so I've asked him to post
it here.
/Christian
--
Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
On Thu, Oct 04, 2007 at 10:23:09AM +0200, Helge Hafting wrote:
> Having at least two styles beginning at the same point will
> happen, with 3 cursor positions in front of a word. If you
> click there and want to delete the previous word, will
> you remove styles as well? Or if you want to remove st
-- Forwarded message --
Date: Thu, 4 Oct 2007 12:31:57 -0400
From: Steve Litt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Use cases for charstyles (Was: *not* everything is an inset!)
On Wednesday 03 October 2007 18:20, you wrote:
Hi Steve,
There's a discussion going
> The unicode character is #309 but the one in the wiki and also in the
UserGuide is #770. So a
> simple correction should solve the problem. I don't get a crash here anyway
when selecting the
> small black square used to represent #770.
When you found a solution, could you please fix this in t
On Thu, Oct 04, 2007 at 06:52:48PM +0300, Martin Vermeer wrote:
> > Why do we need to nest insets then ? :-P
>
> Actually I don't think we should (usually). In text, cases where we
> want to nest (charstyle) insets ought to be rare, if we have defined
> them as sensible semantic units. Over-use o
1 - 100 of 192 matches
Mail list logo