> -void Cursor::niceInsert(docstring const & t, Parse::flags f, bool enter)
> +int Cursor::niceInsert(docstring const & t, Parse::flags f, bool enter)
> {
> MathData ar(buffer());
> asArray(t, ar, f);
> - if (ar.size() == 1 && (enter || selection()))
> + if (ar.size() ==
Are there any languages where it is correct to typeset \emph{ word }
including white space around the word?
If not, it may be better to trim the part inside \emph{...}.
As an alternative, one could also either (a) trim any white-space-only
\emph argument when emphasis is toggled, or (b) remove
Tommaso Cucinotta wrote:
> AFAIK, LyX incorporates something that allows me to achieve this.
afaik there is no such thing. on the other many things you have written should
be easily doable via lyx server (look on lyxclient binary). to get precise
info about cursor or selection info one may need ne
Hi,
I'd like to have a set of automated tests for:
-) searching stuff in a number of cases (e.g., various combinations of
options from the GUI) for a few simple test .lyx files;
-) emulating the hit of the "Find Next" button by the user and checking
whether the selected text matches with what s
Il 27/01/2011 01:25, Pavel Sanda ha scritto:
@@ -1234,10 +1234,13 @@
regex_replace(s, s, "\\[(.*)\\]", "$1");
repl_latex = from_utf8(s);
LYXERR(Debug::FIND, "Replacing by niceInsert()ing latex: '"<<
repl_latex<< "'");
- cur
tomm...@lyx.org wrote:
> Author: tommaso
> Date: Thu Jan 27 00:54:12 2011
> New Revision: 37335
> URL: http://www.lyx.org/trac/changeset/37335
>
> Log:
> Fixing regression bug after last commit. Couldn't find anything better,
> however now it apparently works and doesn't crash
> (when replacing t
Il 16/01/2011 10:06, Pavel Sanda ha scritto:
i meant lets try to commit it and have some testing for sideeffects...
the bug you described is fixed for me as well.
It's in: r37334.
T.
Is this
cur.pos() >= 0 && cur.pos() <= cur.lastpos()
a correct assert identifying legal pos() values, or is there any other
legal border position that goes beyond this condition ?
Thanks,
T.
Le 26 janv. 2011 à 22:10, Enrico Forestieri a écrit :
> On Wed, Jan 26, 2011 at 09:52:39PM +0100, Jean-Marc Lasgouttes wrote:
>
> Yep, but an explicit method also helps in the line counting task,
> otherwise YA method has to be called to get that info. Currently it
> is done such as "lines = os.c
On Wed, Jan 26, 2011 at 09:52:39PM +0100, Jean-Marc Lasgouttes wrote:
> Le 26 janv. 2011 à 20:55, Enrico Forestieri a écrit :
> >> I would have preferred a more explicit syntax like
> >> os << breakl << "\\begin"
> >> and have all explicit \n be output.
> >
> > Hmm... iomanip's work at a lower lev
Le 26 janv. 2011 à 20:55, Enrico Forestieri a écrit :
>> I would have preferred a more explicit syntax like
>> os << breakl << "\\begin"
>> and have all explicit \n be output.
>
> Hmm... iomanip's work at a lower level and that is a simple wrapper
> around an output stream. You are however right t
On Wed, Jan 26, 2011 at 05:10:53PM +0100, Jean-Marc Lasgouttes wrote:
> Le 26/01/2011 16:37, Pavel Sanda a écrit :
> >Enrico Forestieri wrote:
> >>As already said, the class is simply a wrapper around odocstream, so it
> >>should be safe
> >
> >i see one possible collision. we maintain TeXRow struc
On Wed, Jan 26, 2011 at 05:24:24PM +0100, Jean-Marc Lasgouttes wrote:
> Le 26/01/2011 17:13, Pavel Sanda a écrit :
> >Enrico Forestieri wrote:
> >>No, I already tried to audit that. The only possibility of missing
> >>a newline would be when outputing "\nblabla", i.e., when the '\n'
> >>is the firs
On 2011-01-26, Pavel Sanda wrote:
> Guenter Milde wrote:
>> However, there are clear claims that all of LyX 2 is experimental :-)
>> I agree that this should be improved before the actual release.
> guys, were you happy if we have "Use non-TeX fonts (via XeTeX/LuaTeX) -
> Experimental" checkbox
Julien Rioux wrote:
> Everyone's time is short so I suppose all issues with this won't get fixed
> before the release candidate. So yes, a up-front mention that it is an
> experimental feature would be good from my point of view. We could also
> have a list of specific requirements or known issu
On 26/01/2011 5:17 AM, Pavel Sanda wrote:
Guenter Milde wrote:
However, there are clear claims that all of LyX 2 is experimental :-)
I agree that this should be improved before the actual release.
guys, were you happy if we have "Use non-TeX fonts (via XeTeX/LuaTeX) -
Experimental"
checkbox a
Pavel Sanda wrote:
> Ben Goodrich wrote:
> > Pavel Sanda lyx.org> writes:
> > > most trivial patch would be something like
> > > #ifdef linux
> > > void fixdamnedext4(){fopen(f);fsync(f);fclose(f);}
> > > #endif
> > > and call it somewhere after saving file.
> > > it would need some brave ext4 sou
Le 26/01/2011 17:19, Pavel Sanda a écrit :
Jean-Marc Lasgouttes wrote:
Actually, I think texrow should be integrated inside the otexstream. But
this is more work, of course.
does not this object disappear after export?
anyway the only good excuse to refactorize texrow now is #7186...
At leas
Le 26/01/2011 17:13, Pavel Sanda a écrit :
Enrico Forestieri wrote:
No, I already tried to audit that. The only possibility of missing
a newline would be when outputing "\nblabla", i.e., when the '\n'
is the first char of a string. So, checking is quite strightforward.
thanks for looking into
Jean-Marc Lasgouttes wrote:
> Actually, I think texrow should be integrated inside the otexstream. But
> this is more work, of course.
does not this object disappear after export?
anyway the only good excuse to refactorize texrow now is #7186...
pavel
Enrico Forestieri wrote:
> No, I already tried to audit that. The only possibility of missing
> a newline would be when outputing "\nblabla", i.e., when the '\n'
> is the first char of a string. So, checking is quite strightforward.
thanks for looking into this. if no other comments appear
this lo
Le 26/01/2011 16:37, Pavel Sanda a écrit :
Enrico Forestieri wrote:
As already said, the class is simply a wrapper around odocstream, so it
should be safe
i see one possible collision. we maintain TeXRow structure to keep
mapping between .lyx cursor position<-> .tex lines.
Actually, I think
Le 26/01/2011 15:27, Richard Heck a écrit :
On 01/26/2011 08:01 AM, Enrico Forestieri wrote:
On Wed, Jan 26, 2011 at 12:04:42PM +0100, lasgout...@lyx.org wrote:
Author: lasgouttes
Date: Wed Jan 26 12:04:42 2011
New Revision: 37328
URL: http://www.lyx.org/trac/changeset/37328
Log:
Unify handlin
On Wed, Jan 26, 2011 at 04:37:29PM +0100, Pavel Sanda wrote:
> Enrico Forestieri wrote:
> > As already said, the class is simply a wrapper around odocstream, so it
> > should be safe
>
> i see one possible collision. we maintain TeXRow structure to keep
> mapping between .lyx cursor position <-> .
Enrico Forestieri wrote:
> As already said, the class is simply a wrapper around odocstream, so it
> should be safe
i see one possible collision. we maintain TeXRow structure to keep
mapping between .lyx cursor position <-> .tex lines.
the moment you start do something magical inside newline stru
Enrico Forestieri wrote:
> Unfortunately, I do not. If you select " not ", then this is to be
> emphasized.
i tend to agree here.
pavel
On Wed, Jan 26, 2011 at 09:27:41AM -0500, Richard Heck wrote:
> On 01/26/2011 08:01 AM, Enrico Forestieri wrote:
> >On Wed, Jan 26, 2011 at 12:04:42PM +0100, lasgout...@lyx.org wrote:
> >>Author: lasgouttes
> >>Date: Wed Jan 26 12:04:42 2011
> >>New Revision: 37328
> >>URL: http://www.lyx.org/trac/
On Wed, Jan 26, 2011 at 09:00:04AM -0500, Richard Heck wrote:
> On 01/25/2011 08:45 PM, Cyrille Artho wrote:
> >I have looked into this glitch, and it seems to be an issue of the
> >GUI doing exactly what the user does, which is not always what the
> >user wants. In particular, it comes from the fa
On 01/26/2011 08:01 AM, Enrico Forestieri wrote:
On Wed, Jan 26, 2011 at 12:04:42PM +0100, lasgout...@lyx.org wrote:
Author: lasgouttes
Date: Wed Jan 26 12:04:42 2011
New Revision: 37328
URL: http://www.lyx.org/trac/changeset/37328
Log:
Unify handling of pass thru insets and paragraphs by i
On 01/25/2011 08:45 PM, Cyrille Artho wrote:
I have looked into this glitch, and it seems to be an issue of the GUI
doing exactly what the user does, which is not always what the user
wants. In particular, it comes from the fact that one may not always
select parts of a text with exact consiste
On Wed, Jan 26, 2011 at 12:04:42PM +0100, lasgout...@lyx.org wrote:
> Author: lasgouttes
> Date: Wed Jan 26 12:04:42 2011
> New Revision: 37328
> URL: http://www.lyx.org/trac/changeset/37328
>
> Log:
> Unify handling of pass thru insets and paragraphs by introducing
> Paragraph::isPassThru. Many
Just as a follow-up. This is bug http://www.lyx.org/trac/ticket/7187
and will be fixed in the next release.
Vincent
Guenter Milde wrote:
> However, there are clear claims that all of LyX 2 is experimental :-)
> I agree that this should be improved before the actual release.
guys, were you happy if we have "Use non-TeX fonts (via XeTeX/LuaTeX) -
Experimental"
checkbox and maybe some sentence in tooltip as wel
On Tuesday 25 January 2011 14:03:01 Pavel Sanda wrote:
> > I used to use 'svn://', but from where I am now it seems it is blocked,
> > and I get a "no route to host" error.
>
> it works just fine here, so i guess there is some net problem between you
> and server.
>
> pavel
Some corporate/unive
On 2011-01-25, Julien Rioux wrote:
> On 25/01/2011 1:51 PM, Pavel Sanda wrote:
>> Julien Rioux wrote:
>>> On 22/01/2011 3:30 PM, Guenter Milde wrote:
The problem is, that XeTeX, LuaTeX and supporting packgages (fontspec
in this case) are moving targets.
>>> Wouldn't it be better for the
35 matches
Mail list logo
