Le 20/04/2016 20:45, GNU Support a écrit :
Hello,
maybe it should be a space if it is space. Space is a character just as
any other character. Imagine if LyX would not show the characte "a"
after tex command. The space is AFTER the tex command and not WITHIN the
tex command.
"space" is not a
On 20.04.16 21:22, Guenter Milde wrote:
>>> This is on Mac, 10.10, LyX-rc1
>
>>> Is this a known bug;
>>> I couldn't find it on trac?
>
>>> Steps to reproduce:
>>> – launch LyX
>>> – enter some characters
>>> – start new line
>>> – switch OS input-method to “Greek Polytonic”
>>> – enter some
On 2016-04-20, mn wrote:
> On 20.04.16 19:22, mn wrote:
>> This is on Mac, 10.10, LyX-rc1
>> Is this a known bug;
>> I couldn't find it on trac?
>> Steps to reproduce:
>> – launch LyX
>> – enter some characters
>> – start new line
>> – switch OS input-method to “Greek Polytonic”
>> – enter some
On 2016-04-20, bugs@gnu.support wrote:
> Hello,
> There is long standing bug in LyX that I managed to handle on my
> side. That is when I insert TeX code with Control-L and anything
> thereafter, even though there is a space, is not spaced.
This is not a bug but a TeX feature.
Ctrl-L (evil red
Le 20/04/2016 20:29, Guenter Milde a écrit :
The recommended LaTeX-way to deal with this is to ensure that every LaTeX
command is terminated by a pair of {}, either with arguments or empty.
\mycommand{} four five
The pair of braces is uesful as well to avoid pasting a (La)TeX command with
I understand what you mean.
However, space is something I can see.
Why is there the same behavior after tex command which is anyway
surrounded by visible red box, if I hit space or if I don't hit
space. It should not be the same.
If space after tex command is not accepted by LyX then the space
Le 20/04/2016 18:21, Scott Kostyshak a écrit :
And to confirm: you *can* insert a citation when you compile 2.1.0
(i.e. you have the same findings as Bruce) ?
Sure, citations work fine with LyX-2.1.4 and openbox.
I've read your post about bisect.
If I understand correctly, I should bisect
On 2016-04-20, GNU Support wrote:
> I understand what you mean.
> However, space is something I can see.
> Why is there the same behavior after tex command which is anyway
> surrounded by visible red box, if I hit space or if I don't hit
> space. It should not be the same.
The LaTeX command may
Hello,
maybe it should be a space if it is space. Space is a character just as
any other character. Imagine if LyX would not show the characte "a"
after tex command. The space is AFTER the tex command and not WITHIN the
tex command.
This space bug, actually breaks the philosophy os WYSIWYM.
I
On 21/04/16 02:40, Jean-Pierre Chrétien wrote:
Le 20/04/2016 13:31, bruce muirhead a écrit :
Clearly the problem had to be my particular debian setup.
My first port of call was to change the window manager I have been
using, from
xfce running on openbox to xfwm4.
This completely removed the
On 20/04/16 17:21, Jean-Pierre Chrétien wrote:
On Wed, Apr 20, 2016 at 01:32:20AM +, Bruce Muirhead wrote:
Hi,
I've been trying to compile rc1 with limited success.
Compilation occurs, but when tested, on existing 2.1 files and on a
new file (using src/lyx) it is not possible to insert or
On Wed, Apr 20, 2016 at 01:32:20AM +, Bruce Muirhead wrote:
Hi,
I've been trying to compile rc1 with limited success.
Compilation occurs, but when tested, on existing 2.1 files and on a new file
(using src/lyx) it is not possible to insert or edit citations. Everything else
appears to
Le 20/04/2016 03:32, Bruce Muirhead a écrit :
The configure log shows messages such as:
configure:5704: g++ -V >&5
g++: error: unrecognized command line option '-V'
g++: fatal error: no input files
compilation terminated.
I have attached the full configuration log.
At least this part is OK.
On 20/04/16 19:00, Jean-Marc Lasgouttes wrote:
Le 20/04/2016 03:32, Bruce Muirhead a écrit :
The configure log shows messages such as:
configure:5704: g++ -V >&5
g++: error: unrecognized command line option '-V'
g++: fatal error: no input files
compilation terminated.
I have attached the full
On 20/04/16 15:27, Scott Kostyshak wrote:
On Wed, Apr 20, 2016 at 03:19:51PM +1000, bruce muirhead wrote:
On 20/04/16 14:32, Scott Kostyshak wrote:
On Wed, Apr 20, 2016 at 04:21:02AM +, Bruce Muirhead wrote:
From: Scott Kostyshak
Yes, this is all great
Le 20 avril 2016 08:48:16 CEST, bruce muirhead a
écrit :
>On 20/04/16 17:21, Jean-Pierre Chrétien wrote:
>>
>> Hmm, seems rather Debian Stretch (testing) than Jessie (stable) to
>me,
>All I can say is that there are no testing or unstable repositories in
>my apt
On 20/04/16 19:17, Jean-Pierre Chrétien wrote:
Le 20 avril 2016 08:48:16 CEST, bruce muirhead a
écrit :
On 20/04/16 17:21, Jean-Pierre Chrétien wrote:
Hmm, seems rather Debian Stretch (testing) than Jessie (stable) to
me,
All I can say is that there are no
Le 20/04/2016 11:55, bruce muirhead a écrit :
Attached is the beginning of a paper which I am currently drafting, and
the bib file. This is the file with which I first tested 2.2.0rc1.
I use Jabref, so have attached the Jabref created bibliography file.
Needless to say, my latex is texlive.
Le 20/04/2016 10:55, bruce muirhead a écrit :
Attached is the beginning of a paper which I am currently drafting, and the bib
file. This is the file with which I first tested 2.2.0rc1.
I use Jabref, so have attached the Jabref created bibliography file.
Needless to say, my latex is texlive.
Le 19/04/2016 11:01, Jean-Marc Lasgouttes a écrit :
Le 19/04/2016 01:26, Guillaume Munch a écrit :
This turns InsetMathHull::isTable() into a redefinition of
Inset::isTable().
OK, I missed the definition of InsetMathHull::isTable() at that time.
As I see it, your version of isTable means
Hello,
I'm not sure to have correctly understood the threads
about the release of 2.2.0.
Will a string translation round be necessary before the release ?
As far as fr.po is concerned, I have :
"POT-Creation-Date: 2016-04-05 00:21+0200\n"
"PO-Revision-Date: 2016-03-24 14:52+\n"
On 20/04/16 22:03, Jean-Marc Lasgouttes wrote:
Le 20/04/2016 11:55, bruce muirhead a écrit :
Attached is the beginning of a paper which I am currently drafting, and
the bib file. This is the file with which I first tested 2.2.0rc1.
I use Jabref, so have attached the Jabref created bibliography
Le 20/04/2016 14:31, bruce muirhead a écrit :
Clearly the problem had to be my particular debian setup.
My first port of call was to change the window manager I have been
using, from xfce running on openbox to xfwm4.
This completely removed the problem, and all is now working as it
should,
Hello,
There is long standing bug in LyX that I managed to handle on my
side. That is when I insert TeX code with Control-L and anything
thereafter, even though there is a space, is not spaced.
It looks something like:
\mycommand = One two three
And I insert into the LyX document:
[\mycommand]
Le 20/04/2016 17:40, Jean-Pierre Chrétien a écrit :
In addition, some citations appear as TeX code, others as insets (see snapshot
attached).
Oups, same with Gnome and Openbox.
--
Jean-Pierre
\usepackage{xspace}
See:
https://tex.stackexchange.com/questions/180686/acceptable-use-cases-for-xspace-when-will-it-fail
for a discussion.
On Wed, Apr 20, 2016 at 10:25 AM, wrote:
> Hello,
>
> There is long standing bug in LyX that I managed to handle on my
> side. That is
Le 20/04/2016 15:25, bugs@gnu.support a écrit :
Hello,
There is long standing bug in LyX that I managed to handle on my
side. That is when I insert TeX code with Control-L and anything
thereafter, even though there is a space, is not spaced.
It looks something like:
\mycommand = One two three
Hello
You have suggested me to simply cope with it by another method, to
include the space in the TeX command instead of using visible available
space in LyX. It is not an option.
I hope that it is recognized as bug and will be corrected.
Jean Louis
On Wed, Apr 20, 2016 at 05:56:32PM +0100,
This is on Mac, 10.10, LyX-rc1
Is this a known bug;
I couldn't find it on trac?
Steps to reproduce:
– launch LyX
– enter some characters
– start new line
– switch OS input-method to “Greek Polytonic”
– enter some glyphs
– at the end of that string, hold down shift and select the Greek
– open
On Wed, Apr 20, 2016 at 02:39:19PM +0200, Jean-Marc Lasgouttes wrote:
> Le 20/04/2016 14:31, bruce muirhead a écrit :
> > Clearly the problem had to be my particular debian setup.
> >
> > My first port of call was to change the window manager I have been
> > using, from xfce running on openbox to
Le 20/04/2016 17:10, GNU Support a écrit :
Hello
You have suggested me to simply cope with it by another method, to
include the space in the TeX command instead of using visible available
space in LyX. It is not an option.
Try to export in LaTeX and add as many spaces and even newlines, you
On Wed, Apr 20, 2016 at 06:58:08PM +0100, Jean-Pierre Chrétien wrote:
> Le 20/04/2016 17:10, GNU Support a écrit :
> > Hello
> >
> > You have suggested me to simply cope with it by another method, to
> > include the space in the TeX command instead of using visible available
> > space in LyX. It
On Wed, Apr 20, 2016 at 02:19:50PM +0100, Jean-Pierre Chrétien wrote:
> Hello,
>
> I'm not sure to have correctly understood the threads
> about the release of 2.2.0.
> Will a string translation round be necessary before the release ?
> As far as fr.po is concerned, I have :
>
>
Hello,
Now I understand it, it is not something to be handled by LyX, in that
case it is not a "bug".
Thank you much for helping me understand that. It bothered me already
for years.
Jean Louis
On Wed, Apr 20, 2016 at 06:58:08PM +0100, Jean-Pierre Chrétien wrote:
> Le 20/04/2016 17:10, GNU
On Wed, Apr 20, 2016 at 05:40:22PM +0100, Jean-Pierre Chrétien wrote:
> Le 20/04/2016 13:31, bruce muirhead a écrit :
>
> > Clearly the problem had to be my particular debian setup.
> >
> > My first port of call was to change the window manager I have been using,
> > from
> > xfce running on
On 20.04.16 19:22, mn wrote:
> This is on Mac, 10.10, LyX-rc1
>
> Is this a known bug;
> I couldn't find it on trac?
>
> Steps to reproduce:
> – launch LyX
> – enter some characters
> – start new line
> – switch OS input-method to “Greek Polytonic”
> – enter some glyphs
> – at the end of that
On Thu, Apr 21, 2016 at 09:20:04AM +1000, bruce muirhead wrote:
> On 21/04/16 03:34, Scott Kostyshak wrote:
> > On Wed, Apr 20, 2016 at 02:39:19PM +0200, Jean-Marc Lasgouttes wrote:
> > > Le 20/04/2016 14:31, bruce muirhead a écrit :
> > > > Clearly the problem had to be my particular debian
On Thu, Apr 21, 2016 at 11:51:38AM +1000, bruce muirhead wrote:
> On 21/04/16 09:37, Scott Kostyshak wrote:
> > On Thu, Apr 21, 2016 at 09:20:04AM +1000, bruce muirhead wrote:
> > > On 21/04/16 03:34, Scott Kostyshak wrote:
> > > > On Wed, Apr 20, 2016 at 02:39:19PM +0200, Jean-Marc Lasgouttes
On 21/04/16 09:37, Scott Kostyshak wrote:
On Thu, Apr 21, 2016 at 09:20:04AM +1000, bruce muirhead wrote:
On 21/04/16 03:34, Scott Kostyshak wrote:
On Wed, Apr 20, 2016 at 02:39:19PM +0200, Jean-Marc Lasgouttes wrote:
Le 20/04/2016 14:31, bruce muirhead a écrit :
Clearly the problem had to
On Thu, Apr 21, 2016 at 01:30:25AM +0200, mn wrote:
> On 21.04.16 00:21, Guillaume Munch wrote:
> > Le 20/04/2016 22:44, mn a écrit :
> >> On 20.04.16 21:22, Guenter Milde wrote:
> >>
> > This is on Mac, 10.10, LyX-rc1
> > Steps to reproduce:
> > – launch LyX
> > – enter some
On 21/04/16 03:34, Scott Kostyshak wrote:
On Wed, Apr 20, 2016 at 02:39:19PM +0200, Jean-Marc Lasgouttes wrote:
Le 20/04/2016 14:31, bruce muirhead a écrit :
Clearly the problem had to be my particular debian setup.
My first port of call was to change the window manager I have been
using,
On 21.04.16 00:21, Guillaume Munch wrote:
> Le 20/04/2016 22:44, mn a écrit :
>> On 20.04.16 21:22, Guenter Milde wrote:
>>
> This is on Mac, 10.10, LyX-rc1
> Steps to reproduce:
> – launch LyX
> – enter some characters
> – start new line
> – switch OS input-method to
Le 20/04/2016 22:44, mn a écrit :
On 20.04.16 21:22, Guenter Milde wrote:
This is on Mac, 10.10, LyX-rc1
Is this a known bug;
I couldn't find it on trac?
Steps to reproduce:
– launch LyX
– enter some characters
– start new line
– switch OS input-method to “Greek Polytonic”
– enter some
On Wed, Apr 20, 2016 at 10:45:12PM +0200, GNU Support wrote:
> LyX is most professional software I have, I am reporting bug only
> because I love it.
And your feedback is appreciated! Open source software depends on users
like you giving feedback so thank you.
Scott
signature.asc
Description:
On Thu, Apr 21, 2016 at 02:26:12PM +1000, bruce muirhead wrote:
> On 21/04/16 13:10, Scott Kostyshak wrote:
> > On Thu, Apr 21, 2016 at 11:51:38AM +1000, bruce muirhead wrote:
> > > On 21/04/16 09:37, Scott Kostyshak wrote:
> > > > On Thu, Apr 21, 2016 at 09:20:04AM +1000, bruce muirhead wrote:
>
On Thu, Apr 21, 2016 at 03:22:43PM +1000, bruce muirhead wrote:
> On 21/04/16 15:00, Scott Kostyshak wrote:
> > On Thu, Apr 21, 2016 at 02:26:12PM +1000, bruce muirhead wrote:
> > > On 21/04/16 13:10, Scott Kostyshak wrote:
> > > > On Thu, Apr 21, 2016 at 11:51:38AM +1000, bruce muirhead wrote:
>
On 21/04/16 15:00, Scott Kostyshak wrote:
On Thu, Apr 21, 2016 at 02:26:12PM +1000, bruce muirhead wrote:
On 21/04/16 13:10, Scott Kostyshak wrote:
On Thu, Apr 21, 2016 at 11:51:38AM +1000, bruce muirhead wrote:
On 21/04/16 09:37, Scott Kostyshak wrote:
On Thu, Apr 21, 2016 at 09:20:04AM
On 21/04/16 13:10, Scott Kostyshak wrote:
On Thu, Apr 21, 2016 at 11:51:38AM +1000, bruce muirhead wrote:
On 21/04/16 09:37, Scott Kostyshak wrote:
On Thu, Apr 21, 2016 at 09:20:04AM +1000, bruce muirhead wrote:
On 21/04/16 03:34, Scott Kostyshak wrote:
On Wed, Apr 20, 2016 at 02:39:19PM
On 04/20/2016 08:39 AM, Jean-Marc Lasgouttes wrote:
> Le 20/04/2016 14:31, bruce muirhead a écrit :
>
>> I have, apparently, been wasting your time, but all I can say is thank
>> you---without confirmation that the file worked, I would not have found
>> what was causing my problem.
>
> Don't
On 04/20/2016 01:20 PM, GNU Support wrote:
> Hello,
>
> Now I understand it, it is not something to be handled by LyX, in that case
> it is not a "bug".
It is very unexpected, though, I'll agree. One might wonder whether the
space in LyX itself should not be handled as a space in this case. But
On Wed, Apr 20, 2016 at 10:47:38PM +0100, Jean-Pierre Chrétien wrote:
> Le 20/04/2016 18:21, Scott Kostyshak a écrit :
>
> >
> > And to confirm: you *can* insert a citation when you compile 2.1.0
> > (i.e. you have the same findings as Bruce) ?
>
> Sure, citations work fine with LyX-2.1.4 and
51 matches
Mail list logo