On 2011-10-06, Liviu Andronic wrote:
But I was wondering whether there was a simple solution to this,
namely re-using the Instant Preview machinery. I am not familiar with
it's internals, but I understand that to display the LaTeX results the
IP uses the 'preview' package to generate images
Julien Rioux wrote:
First step of moving the bibliography settings to the document settings
(needed, e.g., for biblatex support). We define a default there. A
BibTeX inset takes the default style from the buffer if it doesn't
specify a style of its own. No UI yet, but it's coming. OK?
On 2011-10-06, Tommaso Cucinotta wrote:
Il 06/10/2011 18:58, Julien Rioux ha scritto:
We have Export as... at the top of the menu and More options... at
the bottom, could they be moved together?
I struggle at getting the rationale behind the More Options... entry.
You are supposed to enter
spitz wrote:
Author: spitz
Date: Fri Oct 7 09:09:13 2011
New Revision: 39814
URL: http://www.lyx.org/trac/changeset/39814
Log:
Fix biber execution om MikTeX.
This should go to branch as well.
Jürgen
Op 6-10-2011 15:47, tomm...@lyx.org schreef:
Author: tommaso
Date: Thu Oct 6 15:47:42 2011
New Revision: 39805
URL: http://www.lyx.org/trac/changeset/39805
Log:
Added Export As... dialog, exploiting the new destination path that can
be specified when exporting.
This fixes #3402.
Modified:
On Fri, Oct 7, 2011 at 8:54 AM, Guenter Milde mi...@users.berlios.de wrote:
Would this require that Instant Preview is on? (I have it always off.)
If we can perform it automatically, when IP is on, we should be able
to do this on-demand, when selecting an entry in the c-menu. Granted,
the user
Jean-Pierre Chrétien jeanpierre.chretien at free.fr writes:
Here is a patch implementing this (not tested).
Could you commit and regenerate the po files ?
I forgot to mention that the patch is for branch.
--
Jean-Pïerre
Current trunk gives these warnings, which seem related to me.
Buffer.cpp:4197:42: warning: suggest parentheses around ‘’ within ‘||’
int Buffer::spellCheck(DocIterator from, DocIterator to,
[...]
// If from is at the end of the document (which is possible
// when leaving the mathed) LyX will
Am 07.10.2011 um 09:43 schrieb Tommaso Cucinotta:
Current trunk gives these warnings, which seem related to me.
Buffer.cpp:4197:42: warning: suggest parentheses around ‘’ within ‘||’
int Buffer::spellCheck(DocIterator from, DocIterator to,
[...]
// If from is at the end of the document
Il 07/10/2011 09:01, Guenter Milde ha scritto:
Any supported format (*.*)
ps (*.ps)
pdf (*.pdf)
pdf2 (*.pdf)
pdf3 (*.pdf)
LyX should know a user level name of these formats and present it to the
user (also in the preferences GUI). This is what we do with e.g. tex-source
encoding, where
Op 6-10-2011 18:30, jri...@lyx.org schreef:
Author: jrioux
Date: Thu Oct 6 18:30:37 2011
New Revision: 39809
URL: http://www.lyx.org/trac/changeset/39809
Log:
Don't allow newline characters in the command buffer.
I actually got it by this bug while copy-pasting LFUNs into the toolbar.
I am looking at the result of a svn-git conversion, and it is quite
visible that quite a bit of the tagging in the svn repo has been done
wrongly.
A tag should really only be done as a repo-repo copy, never from the
wc. Now there are a lot of tags that are in themselves small branches,
perhaps
Hubert Christiaen wrote:
I managed to get every chapter compiling correctly but still the whole
document has no index. I have Lyx 1.6.9 for Linux and use Pdflatex for
export. When compiling the whole document the Lyx window goes gray for some
seconds while on the status line running index
Il 07/10/2011 09:20, Vincent van Ravesteijn ha scritto:
FileDialog::Result FileDialog::save(QString const path,
-QStringList const filters, QString const suggested)
+QStringList const filters, QString const suggested,
+QString selectedFilter)
[...]
It's anyway a bit
This below is the authors file I used to make the git commits look
better. I am guessing that some of the names/addresses used are not
quite as some of you would want. So I'd like some input so that I can
get it right.
There are also a couple of entries where I have been unable to find
On Fri, Oct 7, 2011 at 7:34 PM, Lars Gullik Bjønnes lar...@gullik.org wrote:
This below is the authors file I used to make the git commits look
better. I am guessing that some of the names/addresses used are not
quite as some of you would want. So I'd like some input so that I can
get it
Am 07.10.2011 um 13:34 schrieb Lars Gullik Bjønnes:
This below is the authors file I used to make the git commits look
better. I am guessing that some of the names/addresses used are not
quite as some of you would want. So I'd like some input so that I can
get it right.
There are also a
On 07/10/2011 1:34 PM, Lars Gullik Bjønnes wrote:
jrioux = Julien Riouxjri...@physics.utoronto.ca
Please use jri...@lyx.org
Thanks,
Julien
On 07/10/2011 12:06 PM, Vincent van Ravesteijn wrote:
This is actually a useful trick to allow to use some lfuns which require
newlines.
Vincent
It didn't occur to me that newlines are needed for some lfuns. If that's
the case then a QLineEdit is the wrong user interface. There's no visual
Richard Heck wrote:
Log:
Fix biber execution om MikTeX.
This should go to branch as well.
Please go ahead.
Done.
Jürgen
Hi all,
in the recently added Export As... dialog, we need to enumerate the
possible export formats for the current LyX document.
Originally I had thought this was achievable by checking the
Format::document()
method, however it was returning true also for XLS, ODS, CSV and other
formats for
On 10/07/2011 10:09 AM, Tommaso Cucinotta wrote:
Hi all,
in the recently added Export As... dialog, we need to enumerate the
possible export formats for the current LyX document.
Originally I had thought this was achievable by checking the
Format::document()
method, however it was returning
Op 7-10-2011 15:43, Julien Rioux schreef:
On 07/10/2011 12:06 PM, Vincent van Ravesteijn wrote:
This is actually a useful trick to allow to use some lfuns which require
newlines.
Vincent
It didn't occur to me that newlines are needed for some lfuns. If
that's the case then a QLineEdit is
Dear All,
I am trying to set-up forward search in lyx 2.0.0 using skim. I have
followed the instructions posted in
trac: http://www.lyx.org/trac/ticket/7186
Lyx side configuration: (File Handling/File Formats/PDF (pdflatex)
[OMITTED]/displayline -b -r $$n $$o $$t
Skim side:
command:
hello,
i like using lyx for mac and wrote a lot of documents with it.
my first was my bachelor thesis and was great, thanks to lyx!
therefor i'd like to offer my help.
sadly my programming skills aren't that good, but writing and designing are!
what can i do?
one question about lyx for iPad:
i
John McCabe-Dansted gma...@gmail.com writes:
| On Fri, Oct 7, 2011 at 7:34 PM, Lars Gullik Bjønnes lar...@gullik.org wrote:
This below is the authors file I used to make the git commits look
better. I am guessing that some of the names/addresses used are not
quite as some of you would want.
lar...@gullik.org (Lars Gullik Bjønnes) writes:
| This below is the authors file I used to make the git commits look
| better. I am guessing that some of the names/addresses used are not
| quite as some of you would want. So I'd like some input so that I can
| get it right.
| There are also a
Il 08/10/2011 01:08, Lars Gullik Bjønnes ha scritto:
One thing I'd like your input on: Do you want the reference to the svn
commit revisions kept in the git commit messages? Or should I prune them
as well?
What happens with Trac integration ? We used to refer to commits
from the wiki, from
On 2011-10-06, Liviu Andronic wrote:
> But I was wondering whether there was a simple solution to this,
> namely re-using the Instant Preview machinery. I am not familiar with
> it's internals, but I understand that to display the LaTeX results the
> IP uses the 'preview' package to generate
Julien Rioux wrote:
> First step of moving the bibliography settings to the document settings
> (needed, e.g., for biblatex support). We define a default there. A
> BibTeX inset takes the "default" style from the buffer if it doesn't
> specify a style of its own. No UI yet, but it's coming. OK?
On 2011-10-06, Tommaso Cucinotta wrote:
> Il 06/10/2011 18:58, Julien Rioux ha scritto:
>> We have "Export as..." at the top of the menu and "More options..." at
>> the bottom, could they be moved together?
> I struggle at getting the rationale behind the "More Options..." entry.
> You are
spitz wrote:
> Author: spitz
> Date: Fri Oct 7 09:09:13 2011
> New Revision: 39814
> URL: http://www.lyx.org/trac/changeset/39814
>
> Log:
> Fix biber execution om MikTeX.
This should go to branch as well.
Jürgen
Op 6-10-2011 15:47, tomm...@lyx.org schreef:
Author: tommaso
Date: Thu Oct 6 15:47:42 2011
New Revision: 39805
URL: http://www.lyx.org/trac/changeset/39805
Log:
Added Export As... dialog, exploiting the new destination path that can
be specified when exporting.
This fixes #3402.
Modified:
On Fri, Oct 7, 2011 at 8:54 AM, Guenter Milde wrote:
> Would this require that Instant Preview is on? (I have it always off.)
>
If we can perform it automatically, when IP is on, we should be able
to do this on-demand, when selecting an entry in the c-menu. Granted,
the
Jean-Pierre Chrétien free.fr> writes:
>
> Here is a patch implementing this (not tested).
> Could you commit and regenerate the po files ?
I forgot to mention that the patch is for branch.
--
Jean-Pïerre
Current trunk gives these warnings, which seem related to me.
Buffer.cpp:4197:42: warning: suggest parentheses around ‘&&’ within ‘||’
int Buffer::spellCheck(DocIterator & from, DocIterator & to,
[...]
// If from is at the end of the document (which is possible
// when leaving the mathed) LyX
Am 07.10.2011 um 09:43 schrieb Tommaso Cucinotta:
> Current trunk gives these warnings, which seem related to me.
>
> Buffer.cpp:4197:42: warning: suggest parentheses around ‘&&’ within ‘||’
>
> int Buffer::spellCheck(DocIterator & from, DocIterator & to,
> [...]
> // If from is at the end of
Il 07/10/2011 09:01, Guenter Milde ha scritto:
Any supported format (*.*)
ps (*.ps)
pdf (*.pdf)
pdf2 (*.pdf)
pdf3 (*.pdf)
LyX should know a "user level" name of these formats and present it to the
user (also in the preferences GUI). This is what we do with e.g. tex-source
encoding, where
Op 6-10-2011 18:30, jri...@lyx.org schreef:
Author: jrioux
Date: Thu Oct 6 18:30:37 2011
New Revision: 39809
URL: http://www.lyx.org/trac/changeset/39809
Log:
Don't allow newline characters in the command buffer.
I actually got it by this bug while copy-pasting LFUNs into the toolbar.
I am looking at the result of a svn->git conversion, and it is quite
visible that quite a bit of the tagging in the svn repo has been done
wrongly.
A tag should really only be done as a repo->repo copy, never from the
wc. Now there are a lot of tags that are in themselves small branches,
perhaps
Hubert Christiaen wrote:
> I managed to get every chapter compiling correctly but still the whole
> document has no index. I have Lyx 1.6.9 for Linux and use Pdflatex for
> export. When compiling the whole document the Lyx window goes gray for some
> seconds while on the status line "running
Il 07/10/2011 09:20, Vincent van Ravesteijn ha scritto:
> FileDialog::Result FileDialog::save(QString const& path,
> -QStringList const& filters, QString const& suggested)
> +QStringList const& filters, QString const& suggested,
> +QString& selectedFilter)
[...]
It's anyway a
This below is the authors file I used to make the git commits look
better. I am guessing that some of the names/addresses used are not
quite as some of you would want. So I'd like some input so that I can
get it right.
There are also a couple of entries where I have been unable to find
On Fri, Oct 7, 2011 at 7:34 PM, Lars Gullik Bjønnes wrote:
>
> This below is the authors file I used to make the git commits look
> better. I am guessing that some of the names/addresses used are not
> quite as some of you would want. So I'd like some input so that I can
> get
Am 07.10.2011 um 13:34 schrieb Lars Gullik Bjønnes:
>
> This below is the authors file I used to make the git commits look
> better. I am guessing that some of the names/addresses used are not
> quite as some of you would want. So I'd like some input so that I can
> get it right.
>
> There are
On 07/10/2011 1:34 PM, Lars Gullik Bjønnes wrote:
jrioux = Julien Rioux
Please use jri...@lyx.org
Thanks,
Julien
On 07/10/2011 12:06 PM, Vincent van Ravesteijn wrote:
This is actually a useful trick to allow to use some lfuns which require
newlines.
Vincent
It didn't occur to me that newlines are needed for some lfuns. If that's
the case then a QLineEdit is the wrong user interface. There's no visual
Richard Heck wrote:
> >> Log:
> >> Fix biber execution om MikTeX.
> >
> > This should go to branch as well.
>
> Please go ahead.
Done.
Jürgen
Hi all,
in the recently added Export As... dialog, we need to enumerate the
possible export formats for the current LyX document.
Originally I had thought this was achievable by checking the
Format::document()
method, however it was returning true also for XLS, ODS, CSV and other
formats for
On 10/07/2011 10:09 AM, Tommaso Cucinotta wrote:
Hi all,
in the recently added Export As... dialog, we need to enumerate the
possible export formats for the current LyX document.
Originally I had thought this was achievable by checking the
Format::document()
method, however it was returning
Op 7-10-2011 15:43, Julien Rioux schreef:
On 07/10/2011 12:06 PM, Vincent van Ravesteijn wrote:
This is actually a useful trick to allow to use some lfuns which require
newlines.
Vincent
It didn't occur to me that newlines are needed for some lfuns. If
that's the case then a QLineEdit is
Dear All,
I am trying to set-up forward search in lyx 2.0.0 using skim. I have
followed the instructions posted in
trac: http://www.lyx.org/trac/ticket/7186
Lyx side configuration: (File Handling/File Formats/PDF (pdflatex)
[OMITTED]/displayline -b -r $$n $$o $$t
Skim side:
command:
hello,
i like using lyx for mac and wrote a lot of documents with it.
my first was my bachelor thesis and was great, thanks to lyx!
therefor i'd like to offer my help.
sadly my programming skills aren't that good, but writing and designing are!
what can i do?
one question about lyx for iPad:
i
John McCabe-Dansted writes:
| On Fri, Oct 7, 2011 at 7:34 PM, Lars Gullik Bjønnes wrote:
>>
>> This below is the authors file I used to make the git commits look
>> better. I am guessing that some of the names/addresses used are not
>> quite as some of you
lar...@gullik.org (Lars Gullik Bjønnes) writes:
| This below is the authors file I used to make the git commits look
| better. I am guessing that some of the names/addresses used are not
| quite as some of you would want. So I'd like some input so that I can
| get it right.
>
| There are also a
Il 08/10/2011 01:08, Lars Gullik Bjønnes ha scritto:
One thing I'd like your input on: Do you want the reference to the svn
commit revisions kept in the git commit messages? Or should I prune them
as well?
What happens with Trac integration ? We used to refer to commits
from the wiki, from
56 matches
Mail list logo