Am Donnerstag, 18. Juni 2015 um 08:38:28, schrieb Enrico Forestieri
> On Thu, Jun 18, 2015 at 02:24:30AM -0400, Scott Kostyshak wrote:
> >
> > What do you mean? For me M-x does not toggle, it just opens the
> > mini-buffer. Actually I just tested and if I press it rapidly many times
> > sometime
On Thu, Jun 18, 2015 at 02:24:30AM -0400, Scott Kostyshak wrote:
>
> What do you mean? For me M-x does not toggle, it just opens the
> mini-buffer. Actually I just tested and if I press it rapidly many times
> sometimes I can get it to close the mini-buffer. Yours toggles
> perfectly? I wonder if
On Wed, Jun 17, 2015 at 05:51:28PM +0200, Jean-Marc Lasgouttes wrote:
> Le 14/06/2015 07:48, Scott Kostyshak a écrit :
> >>Note though that I do like that if I just press return (that is,
> >>entering an empty string), the command buffer closes. The only reason
> >>I like this though is that a subs
On Wed, Jun 17, 2015 at 11:32:25AM +0200, Jürgen Spitzmüller wrote:
> 2015-06-17 11:03 GMT+02:00 Scott Kostyshak:
>
> > You are right. It does not. But it never has (as far as I recall).
> > However, before the polyglossia commit, it did work with LuaTeX. If I
> > understand correctly, you are say
I would like to use straight double quotes to delimit an argument in a
flex inset, but viewing the source pane shows LyX treats the argument as
if it were an ordinary optional argument, placing it in square brackets.
Is there some trick to using quotes as delimiters? If not, I feel these
would
On 2015-06-17, Richard Heck wrote:
> On 06/17/2015 04:53 AM, Guenter Milde wrote:
>> Indeed. However, when exporting to XeTeX/LuaTeX, LyX uses
>> "utf8-plain", which is the right thing for pandoc, too.
> So, as you suggest, we can make our pandoc converted work with that, yes?
This is just solv
Le 14/06/2015 07:48, Scott Kostyshak a écrit :
Note though that I do like that if I just press return (that is,
entering an empty string), the command buffer closes. The only reason
I like this though is that a subsequent alt + x does not hide the
mini-buffer.
I am not sure that I follow you he
On 06/17/2015 04:53 AM, Guenter Milde wrote:
Indeed. However, when exporting to XeTeX/LuaTeX, LyX uses
"utf8-plain", which is the right thing for pandoc, too.
So, as you suggest, we can make our pandoc converted work with that, yes?
Richard
On 17/06/2015 7:52 p.m., LyX Ticket Tracker wrote:
#9627: Make the document name available to preview insets
---+-
Reporter: aparsloe | Owner: lasgouttes
Type: enhancement| Status: new
Priority: normal |
Am Mittwoch, 17. Juni 2015 um 02:36:25, schrieb Scott Kostyshak
> On Tue, Jun 16, 2015 at 08:33:41AM +0200, Jürgen Spitzmüller wrote:
> > 2015-06-16 1:23 GMT+02:00 Scott Kostyshak :
> >
> > > On Sun, May 17, 2015 at 04:23:14PM +0200, Jürgen Spitzmüller wrote:
> > > > 2015-05-17 15:48 GMT+02:00 Ko
2015-06-17 11:03 GMT+02:00 Scott Kostyshak:
> You are right. It does not. But it never has (as far as I recall).
> However, before the polyglossia commit, it did work with LuaTeX. If I
> understand correctly, you are saying that because it does not work with
> XeTeX it is not a problem that export
On 2015-06-16, Jürgen Spitzmüller wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> 2015-06-16 15:45 GMT+02:00 Guenter Milde:
>> Dear LyX developers,
>> some LICR (LaTeX internal character representation) macros require
>> termination by a {}, so that the macro name can be separat
On Wed, Jun 17, 2015 at 10:26:47AM +0200, Jürgen Spitzmüller wrote:
> 2015-06-17 8:36 GMT+02:00 Scott Kostyshak :
>
> > Are you sure? I only double-checked the first one you referenced
> > (eu_Additional_pdf5_systemF), but for me, the test is broken by the
> > polyglossia commit. I get the followi
On 2015-06-15, Jürgen Spitzmüller wrote:
> 2015-06-15 1:15 GMT+02:00 Uwe Stöhr :
>> Am 14.06.2015 um 17:58 schrieb Jürgen Spitzmüller:
>> I investigated: pandoc expects utf8 encoded input files. LyX has to take
>>> care about that. The pandoc manual suggests to go via iconv:
...
> You must tak
2015-06-17 8:53 GMT+02:00 Scott Kostyshak:
> Now that TL 2015 has been released, is there anything that should be
> done here? Or did you mean once TL 2015 has been out long enough to be
> the standard?
>
It's probably too early to presuppose TL 2015.
Jürgen
>
> Scott
>
2015-06-17 8:36 GMT+02:00 Scott Kostyshak :
> Are you sure? I only double-checked the first one you referenced
> (eu_Additional_pdf5_systemF), but for me, the test is broken by the
> polyglossia commit. I get the following error:
>
> ! LaTeX Error: \begin{otherlanguage} on input line 5994 ended by
16 matches
Mail list logo
