Am 07.07.2015 um 05:40 schrieb Jerry :
> On Jul 6, 2015, at 4:45 PM, Stephan Witt wrote:
>>>
>>> The process failed with these apparent C++ errors:
>>
>> I think I've seen these errors with Xcode 6 and the accompanying clang
>> compiler.
>> It has something to do with cxx11 if I'm not mistaken
Guenter Milde wrote:
> I assumed this and I answered accordingly (as if you had written literal
> and not literate).
>
> My argument, however, is that we may cosider it more useful to encode
> "unencodable" characters into a LICR instead of throwing an error, as for
> LaTeX this is one representa
On Jul 6, 2015, at 4:45 PM, Stephan Witt wrote:
>>
>> The process failed with these apparent C++ errors:
>
> I think I've seen these errors with Xcode 6 and the accompanying clang
> compiler.
> It has something to do with cxx11 if I'm not mistaken. Sorry, I forgot the
> details.
> I'm on Xcode
Am 07.07.2015 um 01:07 schrieb Jerry :
> On Jul 5, 2015, at 10:58 PM, Stephan Witt wrote:
>
>>> If anything I have said above makes it look like I have a clue what I am
>>> doing it is wrong--I'm at least 50% clueless here.
>>
>> Which version/installation of Qt you'll use is determined by the
On Jul 5, 2015, at 10:58 PM, Stephan Witt wrote:
>> If anything I have said above makes it look like I have a clue what I am
>> doing it is wrong--I'm at least 50% clueless here.
>
> Which version/installation of Qt you'll use is determined by the
> --with-qt-dir switch for autotools builds.
>
On 07/06/2015 02:17 PM, Richard Heck wrote:
I've thought about this from time to time and may even have filed a bug
about it. The idea would be to have "command" insets, like citation,
whose fields can be determined dynamically through the layout machinery.
I'm sure this is possible, but I'm als
On 07/06/2015 12:19 PM, PhilipPirrip wrote:
Hi there,
I don't think there's currently a way to achieve this, but might be a
very powerful feature:
Let's say I want to define an inset that needs input from a LyX
dialog. It could be a new citation inset that'll be used with
biblatex, and the LyX
Am Montag 06 Juli 2015, 17:24:47 schrieb Guenter Milde:
> On 2015-07-05, Jürgen Spitzmüller wrote:
> > Am Sonntag 05 Juli 2015, 14:12:55 schrieb Georg Baum:
> >> The attached patch fixes that and even simplifies the code. Does anybody
> >> know of any reason _not_ to use unicodesymbols replacements
On 2015-07-05, Jürgen Spitzmüller wrote:
> Am Sonntag 05 Juli 2015, 14:12:55 schrieb Georg Baum:
>> The attached patch fixes that and even simplifies the code. Does anybody
>> know of any reason _not_ to use unicodesymbols replacements for the user
>> preamble?
> I consider the preamble to be "lit
Le 06/07/2015 17:17, Richard Heck a écrit :
I'm slightly confused. Is the idea that this inset can go anywhere you
like in the document, but its contents end up in the premable? If not,
then why do we need insets to do this? Why not just have some sort of
paragraph layout that does this? of which
Hi there,
I don't think there's currently a way to achieve this, but might be a
very powerful feature:
Let's say I want to define an inset that needs input from a LyX dialog.
It could be a new citation inset that'll be used with biblatex, and the
LyX dialog in question would be the Insert>Citat
On 07/05/2015 02:53 PM, Enrico Forestieri wrote:
On Sun, Jul 05, 2015 at 07:28:34PM +0100, Guillaume M-M wrote:
Le 05/07/2015 18:06, Enrico Forestieri a écrit :
Thanks for the reproducers. They evidence that the problem is due to
the fact that MathData::metrics is not called when instant previe
On 07/05/2015 10:46 AM, Scott Kostyshak wrote:
On Sun, Jul 5, 2015 at 10:35 AM, Guenter Milde wrote:
On 2015-07-05, Jean-Marc Lasgouttes wrote:
In the preamble, there is no way to make a "LyX-only" comment. :-(
If we implemented InPreamble for insets, then one could create an
ERT-like inset t
Le 06/07/2015 14:56, Scott Kostyshak a écrit :
I think there are some who prefer that for the commit you use your
@lyx.org email address. I forget why. I think the argument was that
your personal email address could someday change where your @lyx.org
address would remain constant.
Irrespectivel
On Mon, Jul 6, 2015 at 8:33 AM, Guenter Milde wrote:
> Dear LyX developers,
>
> after years of comments and patches, I just pushed my first commit to the
> LyX repository. http://www.lyx.org/trac/changeset/c56f0538a00/lyxgit
Great! I'll look forward to your commits.
> This is a minor fix for the
Dear LyX developers,
after years of comments and patches, I just pushed my first commit to the
LyX repository. http://www.lyx.org/trac/changeset/c56f0538a00/lyxgit
This is a minor fix for the clash between marvosym and bbding packages.
Please tell me if something went wrong or should have been do
On Mon, Jul 6, 2015 at 7:34 AM, Liviu Andronic wrote:
> My point being: I'm not sure if it's ideal to comment out the chunks,
> as their output can (and often will) cause compilation troubles.
I think we agree. The keyword for me here is *ideal*.
> The other argument against commenting out is t
On Mon, Jul 6, 2015 at 11:45 AM, Scott Kostyshak wrote:
> On Mon, Jul 06, 2015 at 11:25:57AM +0200, Liviu Andronic wrote:
>> On Mon, Jul 6, 2015 at 11:08 AM, Jean-Marc Lasgouttes
>> wrote:
>> > Le 06/07/2015 00:44, Scott Kostyshak a écrit :
>> >>
>> >> chktex is enabled as follows:
>> >>
>> >> en
On Mon, Jul 06, 2015 at 11:25:57AM +0200, Liviu Andronic wrote:
> On Mon, Jul 6, 2015 at 11:08 AM, Jean-Marc Lasgouttes
> wrote:
> > Le 06/07/2015 00:44, Scott Kostyshak a écrit :
> >>
> >> chktex is enabled as follows:
> >>
> >> enable = params().isLatex() && !lyxrc.chktex_command.empty();
> >>
>
On Sun, Jul 05, 2015 at 11:57:36AM -0700, Lior Silberman wrote:
> Tested with LyX 2.1.3 (so with my own file, not the attachment) and
> got the expected result. "Visual" cursor movement means left and
> right arrow keys always move the cursor left and right. The "logical"
> behaviour is as follow
On Mon, Jul 6, 2015 at 11:08 AM, Jean-Marc Lasgouttes
wrote:
> Le 06/07/2015 00:44, Scott Kostyshak a écrit :
>>
>> chktex is enabled as follows:
>>
>> enable = params().isLatex() && !lyxrc.chktex_command.empty();
>>
>> This excludes it from running when knitr is in the document. Is there
>> any e
On Mon, Jul 06, 2015 at 11:08:01AM +0200, Jean-Marc Lasgouttes wrote:
> Le 06/07/2015 00:44, Scott Kostyshak a écrit :
> >chktex is enabled as follows:
> >
> >enable = params().isLatex() && !lyxrc.chktex_command.empty();
> >
> >This excludes it from running when knitr is in the document. Is there
>
On Mon, Jul 06, 2015 at 11:04:37AM +0200, Jean-Marc Lasgouttes wrote:
> Le 06/07/2015 00:44, Scott Kostyshak a écrit :
> >chktex is enabled as follows:
> >
> >enable = params().isLatex() && !lyxrc.chktex_command.empty();
> >
> >This excludes it from running when knitr is in the document. Is there
>
Le 06/07/2015 00:44, Scott Kostyshak a écrit :
chktex is enabled as follows:
enable = params().isLatex() && !lyxrc.chktex_command.empty();
This excludes it from running when knitr is in the document. Is there
any easy way to have it run on the .tex file that is ultimately
produced by knitr?
C
Le 06/07/2015 00:44, Scott Kostyshak a écrit :
chktex is enabled as follows:
enable = params().isLatex() && !lyxrc.chktex_command.empty();
This excludes it from running when knitr is in the document. Is there
any easy way to have it run on the .tex file that is ultimately
produced by knitr?
T
25 matches
Mail list logo
