As said...after upgrading to Fedora 11, I can no longer compile either
branch or trunk. The error is in boost:
In file included from ./boost/mpl/lambda.hpp:22,
from ./boost/mpl/apply.hpp:25,
from ./boost/iterator/iterator_facade.hpp:34,
from .
rgheck wrote:
Jean-Marc Lasgouttes wrote:
rgheck writes:
So we have two different Inset*::getCaptionText methods with different
signatures? This looks ugly, I'd rather standardize on one.
I've changed the name to "getCaptionAsPlaintext()", which is what it
does.
And is it warranted to have
Jean-Marc Lasgouttes schrieb:
The only user visible difference to the previous state is that if a user
types \iddots or \adots, the command is not displayed in red, but the
dots are drawn instead.
But this implies that LyX supports them completely.
No. Reread what Georg said.
Done, but ho
Jean-Marc Lasgouttes wrote:
rgheck writes:
So we have two different Inset*::getCaptionText methods with different
signatures? This looks ugly, I'd rather standardize on one.
I've changed the name to "getCaptionAsPlaintext()", which is what it does.
And is it warranted to ha
Le 20 juin 09 à 00:22, Uwe Stöhr a écrit :
The only user visible difference to the previous state is that if a
user
types \iddots or \adots, the command is not displayed in red, but
the dots are drawn instead.
But this implies that LyX supports them completely.
No. Reread what Georg said.
In the physics department they had a defined format for TeX files.
This can be compared to our coding rules for C++. In the TeX world
LyX is a very small player, so I can understand that people don't
care about a TeX format preferred by LyX and therefore think that
tex2lyx cannot assume any
How about trying this? --
\bind "space" "inset-begin"
\bind "Return""inset-end"
That would surely get a response!
Yes, probably :)
I meant: leave inset-begin, inset-begin-select, inset-end, and
inset-end-select all unbound. That way no one would be u
The only user visible difference to the previous state is that if a user
types \iddots or \adots, the command is not displayed in red, but the
dots are drawn instead.
But this implies that LyX supports them completely.
The new commands do not appear in any menu and not in
any documentation. I
Jean-Marc Lasgouttes schrieb:
In this particular example, I used \renewcommand, but as you know, many
people would have used \def, which defeats your patch.
How that? Do you have an example? All \def commands are output as they are.
I am not sure
what exact set of defining commands should be
On 2009-06-19, Liviu Andronic wrote:
> Dear LyX devels,
> In 1.6.3 I encounter paste problems that I did not notice in previous
> versions. Pasting from LyX to LyX (in the same document) will not
> preserve the (LyX) formatting. For example:
> - copying string "Hello" from section one on a newline
Dear LyX devels,
In 1.6.3 I encounter paste problems that I did not notice in previous
versions. Pasting from LyX to LyX (in the same document) will not
preserve the (LyX) formatting. For example:
- copying string "Hello" from section one on a newline standard env
will yield "1 Hello" with no secti
Jean-Marc Lasgouttes wrote:
> Uwe Stöhr writes:
>
>> Jean-Marc Lasgouttes schrieb:
>>
>>> As I understand, there is no plan for now, because the package yhmath
>>> causes incompatibilities with some others.
>>
>> But we should do something since it is our aim to avoid LaTeX errors.
>> So when we
Jean-Marc Lasgouttes wrote:
Pavel Sanda writes:
again as with some other Juergen's patch some weeks ago most of the
diff contains senseless changes in the output. can you pinpoint why
the endlines are so weirdly treated, i was not able to reproduce it
here. pavel
After a long debuggin
On Fri, Jun 19, 2009 at 12:19 PM, Jean-Marc
Lasgouttes wrote:
> BH writes:
>> So one possibility would be to do the following:
>>
>> #\bind "C-Up" "buffer-begin"
>> #\bind "C-Down" "buffer-end"
>> \bind "C-Up" "inset-begin"
>> \bind "C-Down"
BH writes:
> So one possibility would be to do the following:
>
> #\bind "C-Up" "buffer-begin"
> #\bind "C-Down" "buffer-end"
> \bind "C-Up" "inset-begin"
> \bind "C-Down""inset-end"
I would like it too, but I feared p
On Fri, Jun 19, 2009 at 11:57 AM, Jean-Marc
Lasgouttes wrote:
> BH writes:
>> Sorry. I had searched for M-C-Up/Down, not finding it in mac.bind, and
>> so thought it would be good. Unfortunately, C-M-Up/Down is already
>> taken (for paragraph-move-up/down). That being taken, there's no
>> obvious
Abdelrazak Younes wrote:
rgh...@lyx.org wrote:
Author: rgheck
Date: Fri Jun 19 15:50:19 2009
New Revision: 30186
URL: http://www.lyx.org/trac/changeset/30186
+InsetCaption const * InsetText::getCaptionInset() const
+{
+ParagraphList::const_iterator pit = paragraphs().begin();
+for (;
Uwe Stöhr writes:
> Jean-Marc Lasgouttes schrieb:
>
>> As I understand, there is no plan for now, because the package yhmath causes
>> incompatibilities with some others.
>
> But we should do something since it is our aim to avoid LaTeX errors.
> So when we support these commands, we should at le
Abdelrazak Younes writes:
> Hum, this won't work as expected if there's more than one caption. I
> sometimes use this trick to have multiple graphics in a float without
> them being subfigures.
Good point. And this is more than a trick, probably documented in some
tutorials.
JMarc
BH writes:
> Sorry. I had searched for M-C-Up/Down, not finding it in mac.bind, and
> so thought it would be good. Unfortunately, C-M-Up/Down is already
> taken (for paragraph-move-up/down). That being taken, there's no
> obvious binding to use. Perhaps C-Home/End is best, but see below.
And M-Up
rgheck writes:
>> So we have two different Inset*::getCaptionText methods with different
>> signatures? This looks ugly, I'd rather standardize on one.
>>
> I've changed the name to "getCaptionAsPlaintext()", which is what it does.
And is it warranted to have one with strings and one with stre
Hi all,
Before entering a bug report, I thought I'd check and see if this is a
known phenomenon (since I've seen other reports of issues with recent
versions of Qt).
In LyX 1.6.3-1 on Win XP, with the LyX window maximized (and with or
without a document open), if I change anything in the Loo
Pavel Sanda writes:
> again as with some other Juergen's patch some weeks ago most of the
> diff contains senseless changes in the output. can you pinpoint why
> the endlines are so weirdly treated, i was not able to reproduce it
> here. pavel
After a long debugging session, I found out a solutio
Jean-Marc Lasgouttes schrieb:
As I understand, there is no plan for now, because the package yhmath causes
incompatibilities with some others.
But we should do something since it is our aim to avoid LaTeX errors. So when we support these
commands, we should at least show the users a message t
What needs doing here is pretty simple: If necessary, we convert the
image to a format acceptable for HTML (png, I guess) and deposit it
wherever it needs to be; then we write an image tag. I see more or less
how the conversion can be done, but I'm wondering if anyone has any
helpful ideas ab
rgh...@lyx.org wrote:
Author: rgheck
Date: Fri Jun 19 15:50:19 2009
New Revision: 30186
URL: http://www.lyx.org/trac/changeset/30186
+InsetCaption const * InsetText::getCaptionInset() const
+{
+ ParagraphList::const_iterator pit = paragraphs().begin();
+ for (; pit != paragraphs().
On Fri, Jun 19, 2009 at 9:30 AM, Jean-Marc Lasgouttes wrote:
> BH writes:
>>> There is a need for adding bindings in files other than CUA. Bennett?
>>
>> I'd suggest the attached, also pasted below.
>
> Thanks, it is in.
#&*...@!! (It is Friday, right? Can I swear at myself?)
Sorry. I had search
Jean-Marc Lasgouttes wrote:
rgh...@lyx.org writes:
+docstring InsetCollapsable::getCaptionText(OutputParams const & runparams)
const
Is there a reason why this is in InsetCollapsable and not InsetText? It
would be a good thing to lean up in InsetCollapsable all the stuff that
is not
Jean-Marc Lasgouttes wrote:
rgheck writes:
This must be a problem with my setup. On both branch and trunk, I get
errors of the form "caption undefined" when trying to compile this
manual. Help?
I do not see this. Do you have a recent latex. This manual uses as many
things as possible
BH writes:
>> There is a need for adding bindings in files other than CUA. Bennett?
>
> I'd suggest the attached, also pasted below.
Thanks, it is in.
JMarc
rgheck writes:
> This must be a problem with my setup. On both branch and trunk, I get
> errors of the form "caption undefined" when trying to compile this
> manual. Help?
I do not see this. Do you have a recent latex. This manual uses as many
things as possible, and you;d better have texlive200
rgh...@lyx.org writes:
> +docstring InsetCollapsable::getCaptionText(OutputParams const & runparams)
> const
Is there a reason why this is in InsetCollapsable and not InsetText? It
would be a good thing to lean up in InsetCollapsable all the stuff that
is not related to collapsableness.
It (and
This must be a problem with my setup. On both branch and trunk, I get
errors of the form "caption undefined" when trying to compile this
manual. Help?
Richard
Pavel Sanda writes:
> maybe we _can_ use severity too. as i understand severity is not default field
> and 'we' turned it on when migrating. thats why it is not listed in that
> page...?
I tried to do it by patching ticket/query.py in trac source, and
miserably failed. The SQL query is built here
Uwe Stöhr writes:
> Hello Georg,
>
> \iddots and \adots look in LyX exactly the same, is that correct? When
> I use the new commands, the document is not compilable because the
> needed packages weren't loaded as you wrote in syntax.default. But
> what are your plans that the users don't get LaTe
Uwe Stöhr writes:
> Jean-Marc Lasgouttes schrieb:
>
>>> I'll send an example instead, where one wants to redefine \lyxarrow. Try
>>> exporting and reimporting and see what happens. This show that
>>> filtering lyx commands based on their name is not the panacea you make
>>> it to be, and that fil
rgh...@lyx.org wrote:
Author: rgheck
Date: Thu Jun 18 22:44:38 2009
New Revision: 30164
URL: http://www.lyx.org/trac/changeset/30164
Log:
Disable XHTML output for InsetExternal---for the time being.
As said in the comment, someone who knows what these are supposed
to do should have a look, pl
37 matches
Mail list logo
