On Fri, Oct 14, 2016 at 04:38:31PM -0400, Scott Kostyshak wrote:
> > The second solution would be to use
> >
> > lyx_name = cmd.getArg(0);
> > x11_name = cmd.getArg(1);
> >
> > In this case, the syntax for set-color would be
> > set-color foo bar
> > set-color "foo bar" baz
> > set-color foo
On Thu, Oct 20, 2016 at 04:07:13PM -0700, Pavel Sanda wrote:
> Enrico Forestieri wrote:
> > On Wed, Oct 19, 2016 at 05:30:20PM -0700, Pavel Sanda wrote:
> > > Enrico Forestieri wrote:
> > > > On Wed, Oct 19, 2016 at 03:09:53PM -0700, Pavel Sanda wrote:
> > > > >
> > > > > Funny thing is that my
Am 21.10.2016 um 01:37 schrieb Uwe Stöhr:
2 such languages are however not yet
supported by LyX. The attached patch changes this...
There are in fact 4 such languages that are not RTL/BiDi. Attached is
therefore a better patch with support for these.
regards Uwe
development/FORMAT |
LyX supports already many languages which are not supported by babel but
polyglossia (Telugu, Tamil etc.). 2 such languages are however not yet
supported by LyX. The attached patch changes this and adds support for
Amharic and Asturian.
This is of course a fileformat change.
regards Uwe
Enrico Forestieri wrote:
> On Wed, Oct 19, 2016 at 05:30:20PM -0700, Pavel Sanda wrote:
> > Enrico Forestieri wrote:
> > > On Wed, Oct 19, 2016 at 03:09:53PM -0700, Pavel Sanda wrote:
> > > >
> > > > Funny thing is that my mutt read the previous message without doing
> > > > what you describe...
On Wed, Oct 19, 2016 at 05:30:20PM -0700, Pavel Sanda wrote:
> Enrico Forestieri wrote:
> > On Wed, Oct 19, 2016 at 03:09:53PM -0700, Pavel Sanda wrote:
> > >
> > > Funny thing is that my mutt read the previous message without doing
> > > what you describe...
> >
> > I guess you are using the
On Thu, Oct 20, 2016 at 03:12:50PM +0200, Jean-Marc Lasgouttes wrote:
>
> I have searched a bit, and the only thing I have found (with my MUA
> Thunderbird)
> is to change _all_ my attachments to be base64. I'll try that, because I
> prefer to have you with me than against me ;), but I may have
Le 20/10/2016 à 16:03, Tommaso Cucinotta a écrit :
so the issue would be to double-check whether all regex-es in
findadv.cpp can be converted to std::regex ones. But, is there a common
syntax among boost::regex and std::regex that we can use so that
libraries become interchangeable? Otherwise,
Le 18/10/2016 à 12:11, racoon a écrit :
Thanks JMarc. Do I understand you correctly that you tested high res
displays and they actually create a problem with those tiny 1px spaces?
One other user tested on a HiDPI display and found that the spaces
(which use several pixels on those displays)
Am 19.10.2016 um 23:54 schrieb Tommaso Cucinotta :
>
> On 19/10/2016 23:10, Scott Kostyshak wrote:
>> See 8b66f9ce. Perhaps the commit introduced a bug?
>
> might be. AFAICS, the attempt to replace $$s centrally in
> filetools.cpp:commandPrep() fails because the string getting
On Wed, Oct 19, 2016 at 03:35:38PM -0700, Pavel Sanda wrote:
> I would start with implementing lfun, which would just take the citation
> and try to
> 1. if pdf file found, trigger pdf viewer with file path (doc dir as a base)
> 2. if url found, trigger browser with url
That sounds like a good
On Wed, Oct 19, 2016 at 11:50:06PM +0200, Enrico Forestieri wrote:
> On Wed, Oct 19, 2016 at 04:12:54PM -0400, Scott Kostyshak wrote:
> > On Wed, Oct 19, 2016 at 07:03:32PM +0200, Enrico Forestieri wrote:
> >
> > > This is because mutt takes them to be separate emails placed somewhere
> > > else
On Wed, Oct 19, 2016 at 11:54:06PM +0200, Tommaso Cucinotta wrote:
> Do you know when / under what condition, such a Python intermediate script is
> created and how to prevent that?
I have no idea. If you don't figure out the problem/fix, I can probably
take a look at this next week.
Scott
Le 18/10/2016 à 19:58, Guillaume Munch a écrit :
The next missing bit in TeXRow is the literate feature, which changes
arbitrarily line offsets. Sweave at leaset offers a concordance file
that allows to fix that, but I suspect that it requires significant
work. Would you feel brave enough to
On 20/10/2016 16:23, Jean-Marc Lasgouttes wrote:
But suddenly I am not sure anymore of what the problem is. The original message in this
thread complains about "[0-9]+" not working. In theory this should work both in
Perl regexes and ECMAscript.
need to debug a bit more, but I suspect the
Le 20/10/2016 à 16:33, Richard Heck a écrit :
On 10/20/2016 09:28 AM, Jean-Marc Lasgouttes wrote:
Le 20/10/2016 à 00:13, Richard Heck a écrit :
As discussed recently, we seem to spend a lot of time figuring out what
formats are exportable. The first of the attached patches introduces
caching
Am Donnerstag, 20. Oktober 2016 um 16:23:05, schrieb Jean-Marc Lasgouttes
> Le 20/10/2016 à 16:03, Tommaso Cucinotta a écrit :
> > On 20/10/2016 15:48, Jean-Marc Lasgouttes wrote:
> >> Le 18/10/2016 à 18:42, Tommaso Cucinotta a écrit :
> >>> So, the problem with Advanced F
On 10/20/2016 09:28 AM, Jean-Marc Lasgouttes wrote:
> Le 20/10/2016 à 00:13, Richard Heck a écrit :
>> As discussed recently, we seem to spend a lot of time figuring out what
>> formats are exportable. The first of the attached patches introduces
>> caching of this information, in a very simple
Le 20/10/2016 à 16:03, Tommaso Cucinotta a écrit :
On 20/10/2016 15:48, Jean-Marc Lasgouttes wrote:
Le 18/10/2016 à 18:42, Tommaso Cucinotta a écrit :
So, the problem with Advanced F might be: how do we package on Mac
OS-X ?
I didn't see an answer to this, yet. Do we package with std::regex
On 20/10/2016 15:48, Jean-Marc Lasgouttes wrote:
Le 18/10/2016 à 18:42, Tommaso Cucinotta a écrit :
So, the problem with Advanced F might be: how do we package on Mac OS-X ?
I didn't see an answer to this, yet. Do we package with std::regex on Mac ?
What problem in packaging using boost
Le 18/10/2016 à 18:42, Tommaso Cucinotta a écrit :
So, the problem with Advanced F might be: how do we package on Mac OS-X ?
Side issue: ideally, we'd like that regex inset to work with all regex
libs also on Linux, no?
(except for complex/advanced regexs...)
Actually, boost::regex supports
Le 18/10/2016 à 19:59, Guillaume Munch a écrit :
From what I got from Georg's explanations, there's already a policy
which is quite clear: std::string must only contain ASCII. Therefore any
code using std::string in UTF-8 must be converted to use docstring instead.
That makes much sense, but I
Le 19/10/2016 à 23:07, Richard Heck a écrit :
In BufferParams, we have both an isExportable method and an
isExportableFormat method. Is there actually any functional difference
between these? The latter may be slightly different, in that it passes
the only_viewable flag to exportableFormats. But
Le 19/10/2016 à 19:37, Richard Heck a écrit :
Yes, good for both. It will get much more testing in stable, and we are
presumably some ways from 2.2.3.
Thanks, I did that.
JMarc
Le 18/10/2016 à 12:06, Guenter Milde a écrit :
Whitespace after a macro (\begin) is ignored, after "\begin{something}" not.
Even if it will not necessarily change something in the output, it is safer
to escape it with %.
Fair enough.
JMarc
Le 20/10/2016 à 00:13, Richard Heck a écrit :
As discussed recently, we seem to spend a lot of time figuring out what
formats are exportable. The first of the attached patches introduces
caching of this information, in a very simple way. The second and third
use this to clean up a few things
Le 19/10/2016 à 19:03, Enrico Forestieri a écrit :
On Wed, Oct 19, 2016 at 06:20:51PM +0200, Jean-Marc Lasgouttes wrote:
Thanks, it seems to work well. Here is the combo commit, for reference.
Jean-Marc, please, can you use some kind of encoding (base64,
quoted-printable or whatever) when
Le 20/10/2016 à 06:54, Stephan Witt a écrit :
Am 20.10.2016 um 06:35 schrieb Stephan Witt :
commit b37d6c9e941068bbf29281ca854687c7717e0d4d
Author: Stephan Witt
Date: Thu Oct 20 06:35:13 2016 +0200
Add shell wrapper for Maxima on MacOSX
The command line
28 matches
Mail list logo