Previewing SVG text in LyX

[Will Furnass]

Any text in SVG images is rendered within LyX (2.1.3) as a opaque black
rectangle.  Is there any way of configuring the previewing of SVGs so that
contained text is readable within LyX?  I could convert all text in my SVGs
to paths to make them easier to render but I'd rather not as this would
make the images more difficult to edit.

I'm not sure if the following is relevant but in the prefs under File
Handling - Converters I have the following for SVG - PNG and SVG - PDF:

inkscape --without-gui --file=$$i --export-png=$$o
inkscape --file=$$i --export-area-drawing --without-gui --export-pdf=$$o

Regards,

Will

Previewing SVG text in LyX

[Will Furnass]

Any text in SVG images is rendered within LyX (2.1.3) as a opaque black
rectangle.  Is there any way of configuring the previewing of SVGs so that
contained text is readable within LyX?  I could convert all text in my SVGs
to paths to make them easier to render but I'd rather not as this would
make the images more difficult to edit.

I'm not sure if the following is relevant but in the prefs under File
Handling - Converters I have the following for SVG - PNG and SVG - PDF:

inkscape --without-gui --file=$$i --export-png=$$o
inkscape --file=$$i --export-area-drawing --without-gui --export-pdf=$$o

Regards,

Will

Previewing SVG text in LyX

[Will Furnass]

Any text in SVG images is rendered within LyX (2.1.3) as a opaque black
rectangle.  Is there any way of configuring the previewing of SVGs so that
contained text is readable within LyX?  I could convert all text in my SVGs
to paths to make them easier to render but I'd rather not as this would
make the images more difficult to edit.

I'm not sure if the following is relevant but in the prefs under File
Handling -> Converters I have the following for SVG -> PNG and SVG -> PDF:

inkscape --without-gui --file=$$i --export-png=$$o
inkscape --file=$$i --export-area-drawing --without-gui --export-pdf=$$o

Regards,

Will

Re: beamer and lyx 2.1.3

[Will Furnass]

On 12/05/15 05:25, Simplice Dossou-Gbété wrote:
 i would like to add short title to a title when using beamer with lyx 2.1.3.

Have a look at 'beamer-conference-ornate-20min.lyx' in the collection of
templates that come with LyX.  FYI by default you can quickly add a
short title using the keyboard shortcut Alt-a 1.

Will

Re: nomname renaming and header

[Will Furnass]

On 12/05/15 15:37, Wolfgang Engelmann wrote:
 I tried to renaming nomname to Glossar and to get the header right (it
 is at the moment taking the name of the preceeding Namensverzeichnis and
 found this one in the Internet which I put in ERT and inserted between
 Namenverzeichnis and Nomenclature
 
 \clearpage \markboth{\nomname}{\Glossar}

Does this do what you want when inserted as ERT before your Nomenclature?

\renewcommand{\nomname}{Glossar}

Will

Re: beamer and lyx 2.1.3

[Will Furnass]

On 12/05/15 05:25, Simplice Dossou-Gbété wrote:
 i would like to add short title to a title when using beamer with lyx 2.1.3.

Have a look at 'beamer-conference-ornate-20min.lyx' in the collection of
templates that come with LyX.  FYI by default you can quickly add a
short title using the keyboard shortcut Alt-a 1.

Will

Re: nomname renaming and header

[Will Furnass]

On 12/05/15 15:37, Wolfgang Engelmann wrote:
 I tried to renaming nomname to Glossar and to get the header right (it
 is at the moment taking the name of the preceeding Namensverzeichnis and
 found this one in the Internet which I put in ERT and inserted between
 Namenverzeichnis and Nomenclature
 
 \clearpage \markboth{\nomname}{\Glossar}

Does this do what you want when inserted as ERT before your Nomenclature?

\renewcommand{\nomname}{Glossar}

Will

Re: beamer and lyx 2.1.3

[Will Furnass]

On 12/05/15 05:25, Simplice Dossou-Gbété wrote:
> i would like to add short title to a title when using beamer with lyx 2.1.3.

Have a look at 'beamer-conference-ornate-20min.lyx' in the collection of
templates that come with LyX.  FYI by default you can quickly add a
short title using the keyboard shortcut Alt-a 1.

Will

Re: nomname renaming and header

[Will Furnass]

On 12/05/15 15:37, Wolfgang Engelmann wrote:
> I tried to renaming nomname to Glossar and to get the header right (it
> is at the moment taking the name of the preceeding Namensverzeichnis and
> found this one in the Internet which I put in ERT and inserted between
> Namenverzeichnis and Nomenclature
> 
> \clearpage \markboth{\nomname}{\Glossar}

Does this do what you want when inserted as ERT before your Nomenclature?

\renewcommand{\nomname}{Glossar}

Will

Re: Strategies for locating errors

[Will Furnass]

 Will Furnass wrote:

 If would be great if LyX would switch to/open the child document
 containing the likely location of the error and move the cursor to that
 location.

Ticket filed: http://www.lyx.org/trac/ticket/9539

Re: Strategies for locating errors

[Will Furnass]

 Will Furnass wrote:

 If would be great if LyX would switch to/open the child document
 containing the likely location of the error and move the cursor to that
 location.

Ticket filed: http://www.lyx.org/trac/ticket/9539

Re: Strategies for locating errors

[Will Furnass]

> Will Furnass wrote:
>>
>> If would be great if LyX would switch to/open the child document
>> containing the likely location of the error and move the cursor to that
>> location.

Ticket filed: http://www.lyx.org/trac/ticket/9539

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 12:47, Nikos Alexandris wrote:
 * Will Furnass wrfurna...@sheffield.ac.uk [2015-05-05 11:51:56 +0100]:
 
 How do others locate compilation errors in large multi-file documents?

snip
 
 Something like binary search: split in two halfs, try to find out
 which half does not compile. Then, again, repeat the same: split in
 half, identify the erroneous part. Sooner or later you'll nail the
 source of the error.

A good idea, but could LyX be improved to make locating errors less
manual though?  For example, if a mapping was generated at compile time
from LyX lines to TeX lines then buttons could be added to the
compilation pane to move the cursor between the lines referenced in
error messages.

Will

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 13:27, Rainer M Krug wrote:
 Will Furnass wrfurna...@sheffield.ac.uk writes:
 
 could LyX be improved to make locating errors less manual
 though? For example, if a mapping was generated at compile time
 from LyX lines to TeX lines then buttons could be added to the
 compilation pane to move the cursor between the lines referenced
 in error messages.
 
 I am by no means a LaTeX expert -0 so I might be wrong, but - the 
 LaTeX error messages are already quite cryptic, and the error you 
 quote (Missing } inserted' error for 'l.1052') means that the 
 missing } is inserted in this line - where it is actually
 missing and what is causing this does not even LaTeX know - so
 there is no chance that LyX will be able to tell you.

True, but the line number associated with a LaTeX error is a useful
clue when fault-finding and being able to quickly move the cursor to
the corresponding line in LyX could make fixing broken documents much
quicker in many situations.  The compilation pane could display a
caveat next to buttons for moving the cursor between error line
numbers saying something like 'the root cause of this error may not
lie at this location'.

Will

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 15:06, Wolfgang Engelmann wrote:
 That was the reason I was asking a while ago, whether the latex
 source panel (under view) could show the tex line number. But I was
 told it is not possible under lyx.

That would certainly be a step in the right direction.  Given that we
already have forward and backward search between LyX and a PDF viewer
using SyncTeX then something similar for LyX to/from TeX should be feasible.

Will

Re: Strategies for locating errors

[Will Furnass]

On 5 May 2015 at 21:38, Georg Baum georg.b...@post.rwth-aachen.de wrote:


 If you select the error item in the error dialog then the corresponding LyX
 contents should should be selected in the main area as well. This is not
 always 100% correct, but usually the error cause is nearby. Does this not
 work in your case?


Ah, I hadn't noticed that before!  That works perfectly if the error is in
the master document but not if the error is in a child document (of which I
have quite a few).

If would be great if LyX would switch to/open the child document containing
the likely location of the error and move the cursor to that location.

Will

Strategies for locating errors

[Will Furnass]

How do others locate compilation errors in large multi-file documents?

I get a 'Missing } inserted' error for 'l.1052' when compiling but can't
relate that line number to the LyX source.  I then try exporting to tex
using pdflatex into a temporary directory and search through all 16 tex
files looking for errors on or near line 1052.

An alternative approach would have been to comment the
'includes'/'inputs' for various chapters of my thesis then try to
recompile but this partitioning approach would be slow given that it
currently takes ~5mins to compile my thesis.

I'm sure I can find the cause of the error eventually; I was just
wondering if there were a neat way of identifying the location of
errors.  At present pretty much everything in LyX is a joy and very
slick apart from locating the source of errors.

FYI, yes I am using a little Evil Red Text (to use \resizebox within
table floats).

Cheers,

Will

Strategies for locating errors

[Will Furnass]

How do others locate compilation errors in large multi-file documents?

I get a 'Missing } inserted' error for 'l.1052' when compiling but can't
relate that line number to the LyX source.  I then try exporting to tex
using pdflatex into a temporary directory and search through all 16 tex
files looking for errors on or near line 1052.

An alternative approach would have been to comment the
'includes'/'inputs' for various chapters of my thesis then try to
recompile but this partitioning approach would be slow given that it
currently takes ~5mins to compile my thesis.

I'm sure I can find the cause of the error eventually; I was just
wondering if there were a neat way of identifying the location of
errors.  At present pretty much everything in LyX is a joy and very
slick apart from locating the source of errors.

FYI, yes I am using a little Evil Red Text (to use \resizebox within
table floats).

Cheers,

Will

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 12:47, Nikos Alexandris wrote:
 * Will Furnass wrfurna...@sheffield.ac.uk [2015-05-05 11:51:56 +0100]:
 
 How do others locate compilation errors in large multi-file documents?

snip
 
 Something like binary search: split in two halfs, try to find out
 which half does not compile. Then, again, repeat the same: split in
 half, identify the erroneous part. Sooner or later you'll nail the
 source of the error.

A good idea, but could LyX be improved to make locating errors less
manual though?  For example, if a mapping was generated at compile time
from LyX lines to TeX lines then buttons could be added to the
compilation pane to move the cursor between the lines referenced in
error messages.

Will

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 13:27, Rainer M Krug wrote:
 Will Furnass wrfurna...@sheffield.ac.uk writes:
 
 could LyX be improved to make locating errors less manual
 though? For example, if a mapping was generated at compile time
 from LyX lines to TeX lines then buttons could be added to the
 compilation pane to move the cursor between the lines referenced
 in error messages.
 
 I am by no means a LaTeX expert -0 so I might be wrong, but - the 
 LaTeX error messages are already quite cryptic, and the error you 
 quote (Missing } inserted' error for 'l.1052') means that the 
 missing } is inserted in this line - where it is actually
 missing and what is causing this does not even LaTeX know - so
 there is no chance that LyX will be able to tell you.

True, but the line number associated with a LaTeX error is a useful
clue when fault-finding and being able to quickly move the cursor to
the corresponding line in LyX could make fixing broken documents much
quicker in many situations.  The compilation pane could display a
caveat next to buttons for moving the cursor between error line
numbers saying something like 'the root cause of this error may not
lie at this location'.

Will

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 15:06, Wolfgang Engelmann wrote:
 That was the reason I was asking a while ago, whether the latex
 source panel (under view) could show the tex line number. But I was
 told it is not possible under lyx.

That would certainly be a step in the right direction.  Given that we
already have forward and backward search between LyX and a PDF viewer
using SyncTeX then something similar for LyX to/from TeX should be feasible.

Will

Re: Strategies for locating errors

[Will Furnass]

On 5 May 2015 at 21:38, Georg Baum georg.b...@post.rwth-aachen.de wrote:


 If you select the error item in the error dialog then the corresponding LyX
 contents should should be selected in the main area as well. This is not
 always 100% correct, but usually the error cause is nearby. Does this not
 work in your case?


Ah, I hadn't noticed that before!  That works perfectly if the error is in
the master document but not if the error is in a child document (of which I
have quite a few).

If would be great if LyX would switch to/open the child document containing
the likely location of the error and move the cursor to that location.

Will

Strategies for locating errors

[Will Furnass]

How do others locate compilation errors in large multi-file documents?

I get a 'Missing } inserted' error for 'l.1052' when compiling but can't
relate that line number to the LyX source.  I then try exporting to tex
using pdflatex into a temporary directory and search through all 16 tex
files looking for errors on or near line 1052.

An alternative approach would have been to comment the
'includes'/'inputs' for various chapters of my thesis then try to
recompile but this partitioning approach would be slow given that it
currently takes ~5mins to compile my thesis.

I'm sure I can find the cause of the error eventually; I was just
wondering if there were a neat way of identifying the location of
errors.  At present pretty much everything in LyX is a joy and very
slick apart from locating the source of errors.

FYI, yes I am using a little Evil Red Text (to use \resizebox within
table floats).

Cheers,

Will

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 12:47, Nikos Alexandris wrote:
> * Will Furnass <wrfurna...@sheffield.ac.uk> [2015-05-05 11:51:56 +0100]:
> 
>> How do others locate compilation errors in large multi-file documents?
>>

> 
> Something like "binary search": split in two halfs, try to find out
> which half does not compile. Then, again, repeat the same: split in
> half, identify the erroneous part. Sooner or later you'll nail the
> source of the error.

A good idea, but could LyX be improved to make locating errors less
manual though?  For example, if a mapping was generated at compile time
from LyX lines to TeX lines then buttons could be added to the
compilation pane to move the cursor between the lines referenced in
error messages.

Will

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 13:27, Rainer M Krug wrote:
> Will Furnass <wrfurna...@sheffield.ac.uk> writes:
>> 
>> could LyX be improved to make locating errors less manual
>> though? For example, if a mapping was generated at compile time
>> from LyX lines to TeX lines then buttons could be added to the
>> compilation pane to move the cursor between the lines referenced
>> in error messages.
> 
> I am by no means a LaTeX expert -0 so I might be wrong, but - the 
> LaTeX error messages are already quite cryptic, and the error you 
> quote (Missing } inserted' error for 'l.1052') means that the 
> missing "}" is inserted in this line - where it is actually
> missing and what is causing this does not even LaTeX know - so
> there is no chance that LyX will be able to tell you.

True, but the line number associated with a LaTeX error is a useful
clue when fault-finding and being able to quickly move the cursor to
the corresponding line in LyX could make fixing broken documents much
quicker in many situations.  The compilation pane could display a
caveat next to buttons for moving the cursor between error line
numbers saying something like 'the root cause of this error may not
lie at this location'.

Will

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 15:06, Wolfgang Engelmann wrote:
> That was the reason I was asking a while ago, whether the latex
> source panel (under >view) could show the tex line number. But I was
> told it is not possible under lyx.

That would certainly be a step in the right direction.  Given that we
already have forward and backward search between LyX and a PDF viewer
using SyncTeX then something similar for LyX to/from TeX should be feasible.

Will

Re: Strategies for locating errors

[Will Furnass]

On 5 May 2015 at 21:38, Georg Baum  wrote:

>
> If you select the error item in the error dialog then the corresponding LyX
> contents should should be selected in the main area as well. This is not
> always 100% correct, but usually the error cause is nearby. Does this not
> work in your case?
>

Ah, I hadn't noticed that before!  That works perfectly if the error is in
the master document but not if the error is in a child document (of which I
have quite a few).

If would be great if LyX would switch to/open the child document containing
the likely location of the error and move the cursor to that location.

Will

Re: lyx 1.6.9 does not work

[Will Furnass]

On 08/10/14 11:16, Renato Pontefice wrote:
 
 on my windows XP, I' ve installed lyX 1.6.9.
 It still does not work. I've problema on preview PDF, DVI etc.

LyX 1.6.9 is now rather old (as is Windows XP).  Have you tried
installing and running the latest version of LyX (v2.1.2)?

Regards,

Will Furnass
Doctoral Student
Pennine Water Group
Department of Civil and Structural Engineering
University of Sheffield

Phone: +44 (0)114 22 25768

Re: lyx 1.6.9 does not work

[Will Furnass]

On 08/10/14 14:57, renato wrote:
 Ok, but I need to install it on Win XP and Debian Jessie, I know, that
 on Ubunu there are a repo for Lyx 2.1.x, can someone Show me this repo?
 I will add to my repository list on Debian (it should works)

See https://launchpad.net/~lyx-devel/+archive/ubuntu/release

Re: lyx 1.6.9 does not work

[Will Furnass]

On 08/10/14 11:16, Renato Pontefice wrote:
 
 on my windows XP, I' ve installed lyX 1.6.9.
 It still does not work. I've problema on preview PDF, DVI etc.

LyX 1.6.9 is now rather old (as is Windows XP).  Have you tried
installing and running the latest version of LyX (v2.1.2)?

Regards,

Will Furnass
Doctoral Student
Pennine Water Group
Department of Civil and Structural Engineering
University of Sheffield

Phone: +44 (0)114 22 25768

Re: lyx 1.6.9 does not work

[Will Furnass]

On 08/10/14 14:57, renato wrote:
 Ok, but I need to install it on Win XP and Debian Jessie, I know, that
 on Ubunu there are a repo for Lyx 2.1.x, can someone Show me this repo?
 I will add to my repository list on Debian (it should works)

See https://launchpad.net/~lyx-devel/+archive/ubuntu/release

Re: lyx 1.6.9 does not work

[Will Furnass]

On 08/10/14 11:16, Renato Pontefice wrote:
> 
> on my windows XP, I' ve installed lyX 1.6.9.
> It still does not work. I've problema on preview PDF, DVI etc.

LyX 1.6.9 is now rather old (as is Windows XP).  Have you tried
installing and running the latest version of LyX (v2.1.2)?

Regards,

Will Furnass
Doctoral Student
Pennine Water Group
Department of Civil and Structural Engineering
University of Sheffield

Phone: +44 (0)114 22 25768

Re: lyx 1.6.9 does not work

[Will Furnass]

On 08/10/14 14:57, renato wrote:
> Ok, but I need to install it on Win XP and Debian Jessie, I know, that
> on Ubunu there are a repo for Lyx 2.1.x, can someone Show me this repo?
> I will add to my repository list on Debian (it should works)

See https://launchpad.net/~lyx-devel/+archive/ubuntu/release

Re: Keyboard shortcut for unicode input not working

[William Furnass]

On 23 January 2014 21:50, Scott Kostyshak skost...@lyx.org wrote:

 On Thu, Jan 23, 2014 at 4:21 PM, William Furnass w...@thearete.co.uk wrote:

 On 23 January 2014 16:23, Scott Kostyshak skost...@lyx.org wrote:

 On Thu, Jan 23, 2014 at 6:37 AM, William Furnass w...@thearete.co.uk 
 wrote:
 I'm running LyX v2.06 on Linux Mint 16.  In other applications I can
 enter a unicode character using ctrl-shift-u then the code point.
 However, I'm unable to do this in LyX, even if I explicitly bind
 'unicode-input' to ctrl-shift-u in the preferences (results in '\bind
 C-S-u unicode-insert' being added to .lyx/bind/user.bind).

 What happens for you when you do ctrl+shift+u? On Ubuntu 13.10 with
 LyX2.1beta2 I get a u with an underline, but on the next character
 it disappears. I have the feeling this is a Qt-related issue (I was
 just wrong on this same feeling in a thread before though so beware).

 I have a list of unicode code points taped to my monitor and want to
 be able to enter the corresponding characters for them all without
 having to set up shortcut keys for each.

 Nice idea. I often forget the usefulness of physical cheat sheets.
 I've been meaning to print some.

 I forgot to mention that Ctrl-Shift-u allows me to subsequently enter
 code points to input unicode characters in LyX on another machine
 running Ubuntu 13.10

 So you are saying that it works as you expect on this machine? Which
 version of LyX is it?

2.0.6-1 on both machines.

 and, more importantly, that pressing Ctrl-Shift-U
 on my machine oddly generates a O with a backslash through it, without
 me entering any characters afterwards.  I've now unset Ctrl-Shift-U in
 the key bindings and still see this behaviour.

 This is why I think it's Qt-related. I don't think there's a built-in
 LyX binding for Ctrl+Shift+U.

You're right: it's an OS issue rather than a LyX one.  The problem
seems to be that the 'ibus' input method isn't installed and enabled
by default on Linux Mint 16 (which comes with the older xim input
method enabled instead).  However, I think that ibus might be
installed and enabled if one installs either the KDE and/or XFCE
desktop environments, both of which are installed on the machine on
which unicode input works as desired.

Now that I've installed and enabled ibus I can enter unicode using
Ctrl-Shift-u code point.  I can add notes on this to the LyX wiki
- would anyone mind if I hijacked [1] and gave it a more general name
e.g. KeyboardInputMethods?

[1] http://wiki.lyx.org/Tips/FixDeadKeysAndCompose

Will

Re: Keyboard shortcut for unicode input not working

[William Furnass]

On 23 January 2014 21:50, Scott Kostyshak skost...@lyx.org wrote:

 On Thu, Jan 23, 2014 at 4:21 PM, William Furnass w...@thearete.co.uk wrote:

 On 23 January 2014 16:23, Scott Kostyshak skost...@lyx.org wrote:

 On Thu, Jan 23, 2014 at 6:37 AM, William Furnass w...@thearete.co.uk 
 wrote:
 I'm running LyX v2.06 on Linux Mint 16.  In other applications I can
 enter a unicode character using ctrl-shift-u then the code point.
 However, I'm unable to do this in LyX, even if I explicitly bind
 'unicode-input' to ctrl-shift-u in the preferences (results in '\bind
 C-S-u unicode-insert' being added to .lyx/bind/user.bind).

 What happens for you when you do ctrl+shift+u? On Ubuntu 13.10 with
 LyX2.1beta2 I get a u with an underline, but on the next character
 it disappears. I have the feeling this is a Qt-related issue (I was
 just wrong on this same feeling in a thread before though so beware).

 I have a list of unicode code points taped to my monitor and want to
 be able to enter the corresponding characters for them all without
 having to set up shortcut keys for each.

 Nice idea. I often forget the usefulness of physical cheat sheets.
 I've been meaning to print some.

 I forgot to mention that Ctrl-Shift-u allows me to subsequently enter
 code points to input unicode characters in LyX on another machine
 running Ubuntu 13.10

 So you are saying that it works as you expect on this machine? Which
 version of LyX is it?

2.0.6-1 on both machines.

 and, more importantly, that pressing Ctrl-Shift-U
 on my machine oddly generates a O with a backslash through it, without
 me entering any characters afterwards.  I've now unset Ctrl-Shift-U in
 the key bindings and still see this behaviour.

 This is why I think it's Qt-related. I don't think there's a built-in
 LyX binding for Ctrl+Shift+U.

You're right: it's an OS issue rather than a LyX one.  The problem
seems to be that the 'ibus' input method isn't installed and enabled
by default on Linux Mint 16 (which comes with the older xim input
method enabled instead).  However, I think that ibus might be
installed and enabled if one installs either the KDE and/or XFCE
desktop environments, both of which are installed on the machine on
which unicode input works as desired.

Now that I've installed and enabled ibus I can enter unicode using
Ctrl-Shift-u code point.  I can add notes on this to the LyX wiki
- would anyone mind if I hijacked [1] and gave it a more general name
e.g. KeyboardInputMethods?

[1] http://wiki.lyx.org/Tips/FixDeadKeysAndCompose

Will

Re: Keyboard shortcut for unicode input not working

[William Furnass]

On 23 January 2014 21:50, Scott Kostyshak <skost...@lyx.org> wrote:
>
> On Thu, Jan 23, 2014 at 4:21 PM, William Furnass <w...@thearete.co.uk> wrote:
>>
>> On 23 January 2014 16:23, Scott Kostyshak <skost...@lyx.org> wrote:
>>>
>>> On Thu, Jan 23, 2014 at 6:37 AM, William Furnass <w...@thearete.co.uk> 
>>> wrote:
>>>> I'm running LyX v2.06 on Linux Mint 16.  In other applications I can
>>>> enter a unicode character using ctrl-shift-u then the code point.
>>>> However, I'm unable to do this in LyX, even if I explicitly bind
>>>> 'unicode-input' to ctrl-shift-u in the preferences (results in '\bind
>>>> "C-S-u" "unicode-insert"' being added to .lyx/bind/user.bind).
>>
>>> What happens for you when you do ctrl+shift+u? On Ubuntu 13.10 with
>>> LyX2.1beta2 I get a "u" with an underline, but on the next character
>>> it disappears. I have the feeling this is a Qt-related issue (I was
>>> just wrong on this same feeling in a thread before though so beware).
>>
>> I have a list of unicode code points taped to my monitor and want to
>> be able to enter the corresponding characters for them all without
>> having to set up shortcut keys for each.
>
> Nice idea. I often forget the usefulness of physical cheat sheets.
> I've been meaning to print some.
>
>> I forgot to mention that Ctrl-Shift-u allows me to subsequently enter
>> code points to input unicode characters in LyX on another machine
>> running Ubuntu 13.10
>
> So you are saying that it works as you expect on this machine? Which
> version of LyX is it?

2.0.6-1 on both machines.

>> and, more importantly, that pressing Ctrl-Shift-U
>> on my machine oddly generates a O with a backslash through it, without
>> me entering any characters afterwards.  I've now unset Ctrl-Shift-U in
>> the key bindings and still see this behaviour.
>
> This is why I think it's Qt-related. I don't think there's a built-in
> LyX binding for Ctrl+Shift+U.

You're right: it's an OS issue rather than a LyX one.  The problem
seems to be that the 'ibus' input method isn't installed and enabled
by default on Linux Mint 16 (which comes with the older xim input
method enabled instead).  However, I think that ibus might be
installed and enabled if one installs either the KDE and/or XFCE
desktop environments, both of which are installed on the machine on
which unicode input works as desired.

Now that I've installed and enabled ibus I can enter unicode using
Ctrl-Shift-u <>.  I can add notes on this to the LyX wiki
- would anyone mind if I hijacked [1] and gave it a more general name
e.g. KeyboardInputMethods?

[1] http://wiki.lyx.org/Tips/FixDeadKeysAndCompose

Will

Keyboard shortcut for unicode input not working

[William Furnass]

I'm running LyX v2.06 on Linux Mint 16.  In other applications I can
enter a unicode character using ctrl-shift-u then the code point.
However, I'm unable to do this in LyX, even if I explicitly bind
'unicode-input' to ctrl-shift-u in the preferences (results in '\bind
C-S-u unicode-insert' being added to .lyx/bind/user.bind).

Anyone got any ideas why this isn't working?  I know I can enter
unicode using alt-x then typing 'unicode-input codepoint' in the
input box that appears at the bottom of the main window but this is
rather cumbersome.

Regards,

Will

Keyboard shortcut for unicode input not working

[William Furnass]

I'm running LyX v2.06 on Linux Mint 16.  In other applications I can
enter a unicode character using ctrl-shift-u then the code point.
However, I'm unable to do this in LyX, even if I explicitly bind
'unicode-input' to ctrl-shift-u in the preferences (results in '\bind
C-S-u unicode-insert' being added to .lyx/bind/user.bind).

Anyone got any ideas why this isn't working?  I know I can enter
unicode using alt-x then typing 'unicode-input codepoint' in the
input box that appears at the bottom of the main window but this is
rather cumbersome.

Regards,

Will

Keyboard shortcut for unicode input not working

[William Furnass]

I'm running LyX v2.06 on Linux Mint 16.  In other applications I can
enter a unicode character using ctrl-shift-u then the code point.
However, I'm unable to do this in LyX, even if I explicitly bind
'unicode-input' to ctrl-shift-u in the preferences (results in '\bind
"C-S-u" "unicode-insert"' being added to .lyx/bind/user.bind).

Anyone got any ideas why this isn't working?  I know I can enter
unicode using alt-x then typing 'unicode-input <>' in the
input box that appears at the bottom of the main window but this is
rather cumbersome.

Regards,

Will