date:20170724

On Mon, Jul 24, 2017 at 05:49:33PM -0400, Scott Kostyshak wrote:
> On Thu, Jul 20, 2017 at 03:30:14PM -0400, Richard Heck wrote:
> 
> > > I propose to apply this patch and return to productivity.
> > 
> > I would agree with that.
> 
> It seems this patch has some support. I will do some testing and give my
> thoughts soon.

I think the following is unexpected:

Change a different document setting, e.g., "Synchronize with output".
The buttons "OK" and "Apply" are enabled. Then click on "Allow running
external programs". Notice that the "OK" and "Apply" buttons are
disabled, because the settings were applied. I expected only the "Allow
running external programs" setting to be instantly applied, and that the
"Synchronize with output" would only be applied when I click on "OK" or
"Apply".

It did feel strange that the "OK" and "Apply" buttons were not enabled
when checking the "Allow running external programs" checkbox, but I got
used to it quickly.

I wonder if it would be more clear if we append to the current tooltip
"(this setting is changed applied)".

Regarding the message that's displayed when someone manually adds
-shell-escape to a converter, I think we should point the user to more
information so that they can learn how to use the built-in LyX feature.

Where is the appropriate place in our documentation for this feature?

Similarly, we should point the user to the relevant information for the
minted example files.

Scott

signature.asc
Description: PGP signature

Re: [LyX/master] Win installer: prepare for a new 2.3 release (hopefully a beta)

On Tue, Jul 25, 2017 at 12:31:50AM +0200, Uwe Stöhr wrote:
> commit 52025d5c9b5857ae9a0df67d78cd75f8e955e288
> Author: Uwe Stöhr 
> Date:   Tue Jul 25 00:31:45 2017 +0200
> 
> Win installer: prepare for a new 2.3 release (hopefully a beta)
> ---
>  .../Win32/packaging/installer/ChangeLog.txt|9 -
>  development/Win32/packaging/installer/settings.nsh |6 +++---
>  2 files changed, 11 insertions(+), 4 deletions(-)
> 
> diff --git a/development/Win32/packaging/installer/ChangeLog.txt 
> b/development/Win32/packaging/installer/ChangeLog.txt
> index 1e56edf..d7836a3 100644
> --- a/development/Win32/packaging/installer/ChangeLog.txt
> +++ b/development/Win32/packaging/installer/ChangeLog.txt
> @@ -1,4 +1,11 @@
> -Changelog for LyX-230-alpha1:
> +Changelog for LyX-230-alpha2:

Should this be beta1?

Scott


signature.asc
Description: PGP signature

Re: Types of LyX users (Was: Can shell-escape take advantage of needauth framework?)

On Tue, Jul 25, 2017 at 01:03:00AM +0200, Tommaso Cucinotta wrote:
> 
> ... hope you like it as a start ;-P ...

I like it. We need some illustrations.

Scott


signature.asc
Description: PGP signature

Re: Can shell-escape take advantage of needauth framework?


On 19/07/2017 11:06, Pavel Sanda wrote:

I disagree though that we should ban needauth mechanism right now and
if the argument really is that I can trick someone into unchecking
whatever I want, then I can directly trick him into writing rm -rf /
on the commandline.


+1, albeit quite evidently implicit from my side :-)!

T.

Re: Can shell-escape take advantage of needauth framework?


On 18/07/2017 21:50, Christian Ridderström wrote:

I do not know how many KGB/CIA agents will be willing attend the 'hack LyX' 
classes. How much is it worth on a spy resume ?


haha! something like that must have been said by someone in Redmond while coming out with 
this new brilliant and super-useful business-oriented automation feature called 
"Word Macro", before Melissa came out in 1999!

Personally, I wrote patent applications using LyX during one of my prior jobs in 
industry, and helped my colleagues into getting used to LyX, disregarding recommendations 
of my colleagues in that I should have used the "proper" .docx template... that 
can be conveniently edited using a much more secure program and OS?!?

Btw, +1 on threat analysis, and np with the minefield, even simply talking 
about security risks is being a good thing for LyX, and a few mines could 
already be spotted :-)!

Cheers,

T.

Re: Types of LyX users (Was: Can shell-escape take advantage of needauth framework?)


On 25/07/2017 00:15, Scott Kostyshak wrote:

Then we could easily say "I think this feature
would benefit Lucie, would hurt Raimundo, and would not affect Sara at


Alice was beginning to get very tired of sitting by her sister on the bank, and of having 
nothing to do: once or twice she had peeped into the book her sister was reading, but it had 
no pictures or conversations in it, "and what is the use of a book," thought Alice 
"without pictures or or conversations, or R scripts or automatically generated Gnuplot or 
Python plots?
So, Alice started to write a book using the wildly popular & largely known LyX text editor, allowing her to embed 
Animated contents and even interactive chats within chapters of her new book, which she loves to exchange with Bob the 
Lizzard. Although, Bob is used to write so fast, to get to annoy every one with its resounding theme sounds for each and 
every key press, to the point that Alice likes to send him chapters incorporating little jokingly hazardous scripts that, 
when previewed on the screen, cause Bob's sound volume to definitely shutdown (via removal of the snd-* ALSA drivers from 
the kernel through a root escalation exploit, but that's an unimportant technical detail). Bob would never try to preview 
nor compile those chapters, if it were not for the carefully placed and beautifully decorated "PUSH ME" labels 
that Alice placed on Bob's "View" button in the application Toolbar (if you're curious, other carefully crafted 
icons included "DRINK ME" and "ORANGE MARMELADE" in the same toolbar, all of them calling external 
'needauth' converters), when she helped out with LyX installation on his Linux box, quite a though task for a Lizard. So, 
there he goes, pressing that button over and over again through the day.
However, despite the apparent risks coming from the encrypted arguments of the Caterpillar, Alice 
and Bob didn't realize how much should they have been suspicious about the seemingly harmless and 
well-educated tea sessions they regularly had with Mallory the Mad Hatter, who used to like to 
confuse their little unaware friends with innocent paragraphs like: You might just as well say that 
"I see what I eat" is the same thing as "I eat what I see." Albeit literally 
interesting, Alice would fail to realize the full extent of the so big and remarkable differences 
in the font size between the two seemingly and confusingly self-resembling paragraphs, which, at a 
closer look (i.e., zoom at least 15000x in the preferences/settings pane), would indeed be 
recognized in their very nature of peculiar R and Gnuplot insets embedding scripts able to produce 
original hand-crafted output images with the contents just mentioned before, in addition to little, 
unforgettable changes to Alice and Bob home directories...

... hope you like it as a start ;-P ...

T.

Re: short report from LyX under Linux

2017-07-24 Thread Paul A. Rubin


On 07/24/2017 05:39 PM, Uwe Stöhr wrote:


Next thing was to read at least 3D PDFs generated by CAD programs. 
Then I found out that only the abandoned Adobe reader can do this.
I don't recall if anyone mentioned this (the thread is getting a bit 
long), but Adobe Reader 9.5.5 is available for Ubuntu, Linux Mint, and 
maybe some other Debian-based distributions. I assume it's not the 
latest version of Reader, but it's fine for my purposes (which, 
admittedly, do not include CAD output). Again, I'm not sure if it's 
available for Manjaro.


FWIW, I've also had to put up with the occasional important program not 
available (at least that I can find) under Linux. Most recently, my 
school installed a firewall that initially lacked a Linux client at all, 
then had one that wouldn't install properly. Fortunately, an open-source 
client for a different firewall product works reasonably well, but 
sorting this out had me cursing in multiple languages. (You know its bad 
when Americans, notoriously monolingual, run out of expletives and have 
to go to other languages.)


Paul

Re: Silent/automatic execution of converter and needauth, concrete questions to clarify my understanding


On 23/07/2017 22:08, Christian Ridderström wrote:

Are the settings that needauth remember done:
a) per document, regardless of converter
b) per document-and-converter pair?
c) Also per snippet of code?


it's only a), but pls keep in mind this is only for those (few) converters 
tagged with the 'needauth' option in configure.py.

The rationale is that trust should be an issue with new docs never 
seen/compiled earlier only. What would it mean to trust Sweave insets in this 
doc, but NOT Gnuplot insets ? If I don't trust the document, then I should keep 
the warning every time a potentially harmful converter is attempted to be run. 
On the other hand, once I'm sure this is the doc I was expecting from my 
colleague, and I trust him/her, then it will be safe to authorize any converter 
in that doc.


E.g., what happens if I'm keeping a document on say a network drive. I
put some code in the document and execute it. When asked by needauth
the first time, I say "always allow for the document".   So the next
time I execute the document I'm not asked again.

What happens now if someone else modifies the code embedded in the
document?  Will the permission(s) still be active, so that the
document executes the new code?  Am I warned in any way?


no further warning happens here: that's to facilitate collaborative editing with 
colleagues: once I said I trust that pathname, then if I check out (git pull) a change 
from my colleagues, I don't want to be bugged again and again about risks. On the other 
hand, if I don't trust the folks I'm co-editing a .lyx doc with (which I assume to be a 
very very unlikely use-case), then I should never check that box saying "Never ask 
me again for the same doc".

Perhaps a variant could be that, even when I don't say "Never ask me again", if 
I authorize the use of a converter on a specific .lyx filename, then any further use of 
the same converter on the same file with the same time-stamp could be allowed without 
further questions to the user ?


If not, perhaps a future improvement could be to be able to approve
specific code snippets to be executed.
The user-dir could e.g. contain a hash of code snippets that's
approved to be run for a certain document. Or perhaps even for all
kinds of documents.


I'd be for keeping track of possible enhancements like this to 'needauth' as 
individual Trac items, to be linked to

  http://www.lyx.org/trac/ticket/10481

T.

Re: [LyX/master] Preferences shows current zoom instead of preference's default zoom (#10455)

2017-07-24 Thread racoon


On 25.07.2017 07:49, Scott Kostyshak wrote:

On Sat, Jul 22, 2017 at 07:41:32PM +1000, racoon wrote:

On 22.07.2017 08:38, Scott Kostyshak wrote:



No, sorry. Most importantly, I do not understand what the debug messages
mean. Unfortunately, I also do not have much time at my hands at the moment
either. I am happy to help though, if something in my code is unclear.


No problem, Daniel. Thanks for the reply. I'll take a look at it
hopefully within the next week.


Thanks Scott.

Re: Silent/automatic execution of converter and needauth, concrete questions to clarify my understanding

On Tue, Jul 25, 2017 at 12:13:05AM +0200, Tommaso Cucinotta wrote:
> On 18/07/2017 00:49, Guillaume MM wrote:
> > (Another one is if the path is ~/Download/new1.lyx and you happen to
> > have given permanent permissions for a file with the same path three
> > years earlier, deleted and forgotten about since...)
> 
> there's been discussion during the needauth development about an expiry time 
> for the per-document authorization
> 
>   http://www.lyx.org/trac/ticket/10481
> 
> perhaps we should recover that add-on as a separate #, and give it a proper 
> priority ?

+1

Scott


signature.asc
Description: PGP signature

Re: Types of LyX users (Was: Can shell-escape take advantage of needauth framework?)

On Sun, Jul 23, 2017 at 09:52:37PM +0200, Christian Ridderström wrote:

> I think Scott is partly verging towards the topic of types of users
> and user scenarios.

Yes I think so. The problem (as you mentioned) is that we really don't
know what the distribution of our users looks like.

> Perhaps there's more kinds of users?

I think your descriptions of users is very helpful, even more generally.
In fact, some companies assign a name to each type of users to make them
easy to reference. That might be useful for us to put in the
Development.lyx manual. Then we could easily say "I think this feature
would benefit Lucie, would hurt Raimundo, and would not affect Sara at
all," where Lucie, Raimundo, and Sara would be defined in the
development.lyx manual.

Scott

signature.asc
Description: PGP signature

Re: Silent/automatic execution of converter and needauth, concrete questions to clarify my understanding


On 18/07/2017 00:49, Guillaume MM wrote:

(Another one is if the path is ~/Download/new1.lyx and you happen to
have given permanent permissions for a file with the same path three
years earlier, deleted and forgotten about since...)


there's been discussion during the needauth development about an expiry time 
for the per-document authorization

  http://www.lyx.org/trac/ticket/10481

perhaps we should recover that add-on as a separate #, and give it a proper 
priority ?

Thanks,

T.

Re: [LyX/master] Make "devel mode" configurable at run time

Am Montag, 24. Juli 2017 um 17:22:54, schrieb Richard Heck 
> On 07/24/2017 04:15 PM, Jean-Marc Lasgouttes wrote:
> > commit 9fe8190364d27a538efa3928d2166b09e1cef2d5
> > Author: Jean-Marc Lasgouttes 
> > Date:   Mon Jul 24 00:21:43 2017 +0200
> >
> > Make "devel mode" configurable at run time
> > 
> > Traditionally LyX behaves differently when the directive DEVEL_VERSION
> > is defined at compile time. This covers
> > * more detailed description of current position in status bar
> > * the help files are open in read/write mode
> > * more detailed debug output in the View Source panel
> > 
> > This patch introduces the new function devel-mode-toggle that allows
> > to use devel mode in stable releases, and vice versa.
> > 
> > The information is saved in the session file. The default is to
> > disable devel mode.
> > 
> > Remove all traces of DEVEL_VERSION in autoconf and cmake
> 
> So what do we do now to include debug symbols when building?
> 
> Richard

This had nothing to do with debug symbols IMHO.
For cmake it still is
# cmake ... -DLYX_DEBUG=ON -DLYX_DEBUG_GLIBC=ON 
-DLYX_DEBUG_GLIBC_PEDANTIC=ON -DLYX_STDLIB_DEBUG=ON

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: short report from LyX under Linux

On 24/07/2017 23:39, Uwe Stöhr wrote:

One of my daily work is CAD and common programs like Solidworks are not
available under Linux:
https://forum.solidworks.com/thread/90517
The only program I found so far is VariCAD:
http://www.varicad.com/en/home/products/download/

now I see your point, if you get into professional desktop applications needed
in specific areas, then you'll get good/complete/professional ones just for
Windows and perhaps Mac, Linux has very little chances... albeit there's more
and more open-source clones coming out.

I have myself an example of a Windows freeware application I love for
annotating PDFs, which I'm lucky I can use through wine ;-).

Next step was to check for a tax program. There are no German tax programs
available for Linux:
https://wiki.ubuntuusers.de/Steuer-Spar-Erkl%C3%A4rung/

My wife is an accounting consultant ... no way you can see a Linux supported app talking the right
standards that allow official submissions to the IRS website ("Agenzia delle Entrate"),
with periodic upgrades due to new laws/regulations issued every year etc. :-). But, would you like
to hear a sad story ? The software she uses and pays for, officially supported on Windows only, and
on a specific version of Windows only, needs this particular nasty dependency called
"JRE", but there doesn't seem to exist an easy way to run it on Linux (likely one should
crack its licensing scheme, making use of a USB license physical key).

The low market share of Linux is for sure a reason

yes, just for desktops, but don't worry it's already changing, as witnessed by the
"Linux subsystem" embedded within Windows 10 ;-P!

https://msdn.microsoft.com/en-us/commandline/wsl/install_guide
https://msdn.microsoft.com/en-us/commandline/wsl/faq

(don't know much about this, just weird to see all these explanations about
getting Linux stuff working throughout the MSDN docs!)

Re: [LyX/master] We have new translation which slipped through the cracks.

On Fri, Jul 21, 2017 at 10:38:33PM +0200, Jean-Pierre Chrétien wrote:
> Le 19/07/2017 à 13:51, Pavel Sanda a écrit :
> > Pavel Sanda wrote:
> > > commit cd7b1dad6713e0dba2b90e7757fce5b0ca8e
> > > Author: Pavel Sanda 
> > > Date:   Wed Jul 19 13:36:06 2017 +0200
> > > 
> > > We have new translation which slipped through the cracks.
> > 
> > Scott, I am sorry I did not catch that before.
> > 
> > If/when you will be sending the announcement to translators for
> > RC, please add paragraph requesting ack for particular string
> > in layouttranslation table.
> > 
> > I guess we can get quick ack for de, de_alt, fr.
> 
> The current version of lib/layouttranslations is OK for French.

Noted your check at f477b5b.

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] Make "devel mode" configurable at run time


Le 24/07/2017 à 23:22, Richard Heck a écrit :

So what do we do now to include debug symbols when building?


This is completely different. With cmake, something like LYX_RELEASE=OFF

With autoconf, with --enable-build-type=devel or prerelase, but this is 
done automatically from version.


What this one do is change the amount of information in status bar, and 
the fact that help documents are opened read-only.


JMarc

Re: Can shell-escape take advantage of needauth framework?


[slowly catching up...]

On 18/07/2017 19:46, Christian Ridderström wrote:

I just did a test with gnuplot. In the LyX settings I had unchecked 'Forbid of 
use of needauth converters' and unchecked 'Use needauth option'. Then I opened 
a LyX doc with a gnuplot script. Result: LyX tried to run the script due to the 
preview, without asking or alerting me.


that's the purpose of the "Use needauth option", namely, allow for a workflow 
without burdens for those who know what they're doing, disabling needauth (which you did) 
just gets rid of the security measures, opens up your firewall, turns off security etc., 
compare with these other common software like a firewall or antivirus, if I go the its 
admin panel and turn it off...

What if, when unchecking that option, LyX would have popped up another dialog 
with a HUGE SECURITY warning ? I'm now feeling this would be needed.


In my opinion this demonstrates a case where the security is _not_ good enough, 
as I don't think it'd very difficult to trick someone into unchecking these 
boxes.


aware of the limitations of needauth, the final remedy was ...


- ?


sandboxing, as discussed in http://www.lyx.org/trac/ticket/10481, where there's 
a few notes about how to possibly design a portable mechanism across Win, Mac 
and Lin.

Thanks,

T.

Re: [LyX/master] Preferences shows current zoom instead of preference's default zoom (#10455)

On Sat, Jul 22, 2017 at 07:41:32PM +1000, racoon wrote:
> On 22.07.2017 08:38, Scott Kostyshak wrote:

> No, sorry. Most importantly, I do not understand what the debug messages
> mean. Unfortunately, I also do not have much time at my hands at the moment
> either. I am happy to help though, if something in my code is unclear.

No problem, Daniel. Thanks for the reply. I'll take a look at it
hopefully within the next week.

Scott

> Daniel

Re: Different LaTeX output when exporting than when previewing

On Fri, Jul 21, 2017 at 08:57:41PM +, Guenter Milde wrote:

> > Good to know that this specific issue is not important, thanks Günter.
> > Yes, I'm still worried about the underlying bug.
> 
> I am not sure this difference is a bug, it may just be some indeterminalism,
> maybe caused by existence or non-existence of an auxiliary or chache file
> (changing the order in which the secondary languages are "identified" by LyX).

Perhaps, but I'm not sure it's not a bug. I thought that there were no
exceptions in theory that the LaTeX output of the LyX GUI should be
equivalent to the LaTeX output from the LyX CL. I think it is fair for
the user to expect that. I think that LyX must be compiled with Qt, so
even if some cache is being used by the GUI, I think it could also be
used from the CL.

Scott

Re: Going into dangerous mode (Was: Can shell-escape take advantage of needauth framework?)

On Sat, Jul 22, 2017 at 01:09:09AM +0200, Jean-Marc Lasgouttes wrote:
> Le 21/07/2017 à 21:02, Scott Kostyshak a écrit :
> > > except if I disable needauth globally :(
> > 
> > What about editing the session file to add the paths of the .lyx files
> > that you want? If you're interested, I could write a Python/Bash script
> > that does it for you. I might end up using it also.
> 
> Well, I should not have to do that... Or it will be done automatically if I
> edit the file and try to typeset it, right?

Indeed. Rereading your question, I think I misunderstood it. I thought
you were looking for a way to get your scripts run without going through
the GUI for each one.

Scott

Re: Options for resolving the minted + shell-escape issue

On Thu, Jul 20, 2017 at 03:30:14PM -0400, Richard Heck wrote:

> > I propose to apply this patch and return to productivity.
> 
> I would agree with that.

It seems this patch has some support. I will do some testing and give my
thoughts soon. I'm still traveling but will be back and start having
more time hopefully by Thursday.

Scott

Re: Options for resolving the minted + shell-escape issue

On Mon, Jul 17, 2017 at 12:49:05AM +0200, Christian Ridderström wrote:

Hi Christian,

I did not respond to your other questions since I've been traveling, and
others have done so in the mean time. Let me know if some of your
questions have gone unanswered.

> As an aside, I've used org-mode documents in Emacs to invoke MATLAB on
> snippets from within the document and it's very nice, except the really
> annoying part where you for each snippet have to approve that it's run.
> Each time. A big bug in org-mode is that it's not properly showing the
> snippet that's about to be executed before you approve it to be run...
> Perhaps I'm a masochist...

I would want that feature also.

> I'm sorry for not being of more help, but hopefully my comments will
> trigger someone else to contribute something more helpful.

You have been a great help! Thank you for bravely jumping in! I know it
is not the most fun, but as you've mentioned it is an important issue.

Scott

Re: short report from LyX under Linux


El 24.07.2017 a las 17:14, Tommaso Cucinotta escribió:


I think that explains why software companies don't offer Linux versions.


Just a couple of well-known names...


As a new user I tried bit by bit if things that worked under Windows do 
under Linux as well. I just noted that many non-free programs that I 
need are only available under Windows. For example:


One of my daily work is CAD and common programs like Solidworks are not 
available under Linux:

https://forum.solidworks.com/thread/90517
The only program I found so far is VariCAD:
http://www.varicad.com/en/home/products/download/

Next thing was to read at least 3D PDFs generated by CAD programs. Then 
I found out that only the abandoned Adobe reader can do this.


Next thing was to use an USB microscope - no driver and software for Linux.

Next step was to check for a tax program. There are no German tax 
programs available for Linux:

https://wiki.ubuntuusers.de/Steuer-Spar-Erkl%C3%A4rung/

I read about Wine and will also try out VirtualBox. However, my point 
was that there must be a reason why companies don't sell Linux versions 
of their programs. The low market share of Linux is for sure a reason 
and I assume the support work is another one. I mean I use for example 
CAD support several times a year and this just for Windows. I think for 
Linux it would be a very hard job for the software companies to give 
support but support is essential so sell products.


regards Uwe

Re: Any descriptions of the security aspects (related to needauth and shell-escape)?


On 23/07/2017 16:56, Christian Ridderström wrote:

Does anyone feel we should _not_ keep such a security document in the general 
LyX repository?

Note: Generally speaking I'm all for being open and transparent, but such a 
document might end up containing descriptions of ways in which LyX could be 
compromised. It sort of goes with the territory of describing threat 
scenarios/mechanisms.


also during the needauth work, I remember we exchanged a few jokingly dangerous 
.lyx documents off-list, via private e-mails, if memory serves, exactly just to 
avoid providing ourselves a bad starting point :-)... albeit these can be 
crafted in 5 mins.

T.

Re: Any descriptions of the security aspects (related to needauth and shell-escape)?


On 21/07/2017 22:28, Scott Kostyshak wrote:

I support the suggestion to create such a document and suppose to make it
a section in "Development.lyx":

+ bundled with other project policies and developer documentation
+ write access for all developers
+ we can use LyX's version control for to-be-reviewed parts and diverging
   opinions/comments


+1

Development.lyx does not have a rigorous structure. If anyone is
interested in writing something more formal, when we can at reference
that file from within Development.lyx.


I support the idea as well, and I'm interested in contributing to it.

As a starting point for the needauth stuff, I had put a recap of the problem 
and motivations within this TT:

  http://www.lyx.org/trac/ticket/10481

and, just as a reminder, the shell-escape was one of the mentioned use-cases, 
albeit not the very one under my hands at that moment.

I'd suggest not to create a .lyx document, but rather start from a wiki page 
under

  https://wiki.lyx.org/Devel/Devel

with a recap of the current status and exchanged ideas, and pointers to the 
Trac TTs tracking TODOs which we agreed upon.

My2c,

T.

Re: [LyX/master] Make "devel mode" configurable at run time

2017-07-24 Thread Richard Heck

On 07/24/2017 04:15 PM, Jean-Marc Lasgouttes wrote:
> commit 9fe8190364d27a538efa3928d2166b09e1cef2d5
> Author: Jean-Marc Lasgouttes 
> Date:   Mon Jul 24 00:21:43 2017 +0200
>
> Make "devel mode" configurable at run time
> 
> Traditionally LyX behaves differently when the directive DEVEL_VERSION
> is defined at compile time. This covers
> * more detailed description of current position in status bar
> * the help files are open in read/write mode
> * more detailed debug output in the View Source panel
> 
> This patch introduces the new function devel-mode-toggle that allows
> to use devel mode in stable releases, and vice versa.
> 
> The information is saved in the session file. The default is to
> disable devel mode.
> 
> Remove all traces of DEVEL_VERSION in autoconf and cmake

So what do we do now to include debug symbols when building?

Richard

Re: Going into dangerous mode (Was: Can shell-escape take advantage of needauth framework?)


On 23/07/2017 20:55, Christian Ridderström wrote:

Regarding setting something in the preference file manually: The only
thing I mind is that it adds a global state to LyX, as opposed to
starting LyX with some parameters. The global state would likely
affect e.g. testing.


the good thing is that we already have the -userdir command-line optionthat 
allows testing from a predictable initial state, doesn't it :-) ?
(AFAICR, extensively used in autotests for advanced F).

T.

Re: Going into dangerous mode (Was: Can shell-escape take advantage of needauth framework?)


On 22/07/2017 00:47, Guenter Milde wrote:

Enrico's patch did not touch "needauth" but has some nice features for
"shell-escape": it addressed the "set and forget" issue by

a) adding a red icon to the status bar if a document has the "allow
shell-escape" flag.
   
b) revoking the permission, if the document is moved/copied to another

location.
   
I like the approach


+1, I like the idea of a visual feedback on the current security/trust status, 
e.g., it resembles the lock icon used in web browsers for https://.


From a user perspective, a common interface to "needauth" and "allow

shell escape" seems the best. "needauth" could actually take advantage of
Enrico's patch.


once I'll gain some spare time this summer, I'll try a merge :-)...


* Add "unsafe pdflatex" (== pdflatex --shell-escape) and "unsafe xelatex"
   as new converters requiring "needauth".


this sounds like something easy but already discussed and unliked/discarded.


* Allow per-converter permission settings (instead of one generic: "I
   trust/don't trust all unsafe converters").


the current system-wide setting is for all converters (disable any needauth,
allow them but warn me, allow them without constraints), whilst the memory
about trusted documents is per-document -- this makes sense because the
main source of untrust seems the document when coming from who knows where;
once the user acks that the doc is trusted, then we go without bugging the
user for each conversion. However, how would a per-converter settings
work, and how could I trust unconditionally, let's say, a R kneave/sweave
inset in a LyX doc coming from unknown sources, while at the same time
trust that an embedded gnuplot script or shell-escape command would not
delete my home folder ?


* Give users the possibility to check scripts before allowing to run them
   with shell-escape or at least list all parts of the document that will be
   allowed to run in unsafe mode
   (e.g. all gnuplot scripts for "gnuplot allowed", all ERT, preamble,
   document classes and packages for latex with shell escape).


that sounds like a feature enhancement deserving an entry on Trac ?

T.

Re: [LyX/master] Do not error on missing ZWNJ (ligature break) characters.

On 2017-07-24, Jean-Pierre Chrétien wrote:
> Le 23/07/2017 à 18:42, Juergen Spitzmueller a écrit :
>> commit a40868510d36ccdcf3c431cdee17f8204d4b258a
>> Author: Juergen Spitzmueller 
>> Date:   Sun Jul 23 18:41:06 2017 +0200

>> Do not error on missing ZWNJ (ligature break) characters.
...
>> Fixes: #10727

> Works fine with Additional.lyx and system fonts in German.
> In French, leaves correctly errors on em dashes non existing in the selected 
> font.
> I replaced these em dashes by parentheses to avoid test errors.

Just for the record: it turned out these were not EM DASHES (u2014) but
HORIZONTAL BARS (u2015). The former are present in Latin Modern fonts, the
latter are missing.

This is now fixed, too. 

Thanks to Jean-Pierre and Jürgen,

Günter

Re: CMake deprecation warnings


El 24.07.2017 a las 11:46, Kornel Benko escribió:


Yes please, ignore. It happens only with CMake 3.9, and I did not dare to
butcher the code without enough testing.


OK. Thanks you for having a look.

regards Uwe

Re: short report from LyX under Linux


El 24.07.2017 a las 14:37, Jean-Marc Lasgouttes escribió:

Indeed. Personally, I never use enumitem :) There is probably a good 
reason why it is not in the main texlive distribution.


The UserGuide is not designed to cover special interests but to show 
what LyX can do. It is up to the users to use certain features or not.


To repeat; the problem I encountered is that the only dependency for LyX 
is the package "texlive-bin" and that misses almost all packages so that 
even simple document s won't be compilable. As I wrote I will contact 
the packages to add some more texlive packages as dependency.


regards Uwe

Re: short report from LyX under Linux


El 24.07.2017 a las 12:14, Jean-Marc Lasgouttes escribió:

Indeed Adobe Reader for Linux has been abandoned. Personnally I do not 
regret it and I always install SumatraPDF on windows.


I construct parts with 3D CAD. therefore I need a PDF program to view 3D 
PDFs. Sumatra cannot handle it, Evince and other programs I tried can 
also not.


However, this thread was about the LyX experience from a new user's 
perspective. It seems that we cannot do much. That is sad. I thought one 
could force a TeXLive installation or something. However, it is how it is.


Concerning Skype, you should probably change your favorite source of 
information:

https://wiki.archlinux.org/index.php/skype


I did and tried the 5.x beta but it did not work.


Basically, now Skype works in your web browser


You mean the web application? I'll try it out. Thanks for the hint.

regards Uwe

Re: [PATCH][RFC] Make "devel mode" configurable at run time


Le 24/07/2017 à 21:17, Jean-Marc Lasgouttes a écrit :

Le 24/07/2017 à 18:16, Jean-Marc Lasgouttes a écrit :

I could do that indeed. I'll propose another iteration.


Here it is. I also removed all traces of (LYX_)DEVEL_VERSION in cmake. 
Kornel, does it look OK?


Can I apply this?


I put it in.

JMarc

Re: [PATCH][RFC] Make "devel mode" configurable at run time

Am Montag, 24. Juli 2017 um 22:00:06, schrieb Jean-Marc Lasgouttes 

> Le 24/07/2017 à 21:38, Kornel Benko a écrit :
> > Looks OK for cmake. I miss the patch of config.h.in (for automake)
> 
> This one is autogenerated by autoheader (as is written at the top) and 
> not in the git repo.
> 
> JMarc

Yes, I should have git-checked.

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: [PATCH][RFC] Make "devel mode" configurable at run time


Le 24/07/2017 à 21:38, Kornel Benko a écrit :

Looks OK for cmake. I miss the patch of config.h.in (for automake)


This one is autogenerated by autoheader (as is written at the top) and 
not in the git repo.


JMarc

Re: [PATCH][RFC] Make "devel mode" configurable at run time

Am Montag, 24. Juli 2017 um 21:17:10, schrieb Jean-Marc Lasgouttes 

> Le 24/07/2017 à 18:16, Jean-Marc Lasgouttes a écrit :
> > I could do that indeed. I'll propose another iteration.
> 
> Here it is. I also removed all traces of (LYX_)DEVEL_VERSION in cmake. 
> Kornel, does it look OK?
> 
> Can I apply this?
> 
> JMarc
> 

Looks OK for cmake. I miss the patch of config.h.in (for automake)

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: [PATCH][RFC] Make "devel mode" configurable at run time


Le 24/07/2017 à 18:16, Jean-Marc Lasgouttes a écrit :

I could do that indeed. I'll propose another iteration.


Here it is. I also removed all traces of (LYX_)DEVEL_VERSION in cmake. 
Kornel, does it look OK?


Can I apply this?

JMarc



>From 18da500ecfdd70fea22bc385ab1a68fc57818633 Mon Sep 17 00:00:00 2001
From: Jean-Marc Lasgouttes 
Date: Mon, 24 Jul 2017 00:21:43 +0200
Subject: [PATCH] Make "devel mode" configurable at run time

Traditionally LyX behaves differently when the directive DEVEL_VERSION
is defined at compile time. This covers
* more detailed description of current position in status bar
* the help files are open in read/write mode
* more detailed debug output in the View Source panel

This patch introduces the new function devel-mode-toggle that allows
to use devel mode in stable releases, and vice versa.

The information is saved in the session file. The default is to
disable devel mode.

Remove all traces of DEVEL_VERSION in autoconf and cmake
---
 CMakeLists.txt |  1 -
 INSTALL.cmake  |  1 -
 config/lyxinclude.m4   |  1 -
 development/cmake/TODO.txt |  2 --
 development/cmake/config.h.cmake   |  6 --
 src/BufferView.cpp |  2 +-
 src/Cursor.cpp | 23 ---
 src/Cursor.h   |  4 ++--
 src/FuncCode.h |  1 +
 src/LyXAction.cpp  | 13 +
 src/Text.cpp   | 34 +-
 src/Text.h |  4 ++--
 src/frontends/qt4/GuiApplication.cpp   |  7 +--
 src/frontends/qt4/GuiCommandBuffer.cpp |  6 --
 src/frontends/qt4/GuiCommandBuffer.h   |  3 ---
 src/frontends/qt4/GuiView.cpp  | 18 --
 src/frontends/qt4/GuiView.h|  5 +
 src/frontends/qt4/GuiViewSource.cpp| 27 ++-
 src/mathed/InsetMathHull.cpp   |  2 +-
 19 files changed, 85 insertions(+), 75 deletions(-)

diff --git a/CMakeLists.txt b/CMakeLists.txt
index 3c737c7ba2..7490545c1d 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -117,7 +117,6 @@ LYX_OPTION(REQUIRE_SPELLCHECK "Abort if no spellchecker available" OFF ALL)
 LYX_OPTION(ASPELL   "Require aspell" OFF ALL)
 LYX_OPTION(ENCHANT  "Require Enchant" OFF ALL)
 LYX_OPTION(HUNSPELL "Require Hunspell" OFF ALL)
-LYX_OPTION(DEVEL_VERSION"Build developer version" OFF ALL)
 LYX_OPTION(RELEASE  "Build release version, build debug when disabled" OFF ALL)
 LYX_OPTION(DEBUG"Enforce debug build"  OFF ALL)
 LYX_OPTION(NO_OPTIMIZE  "Don't use any optimization/debug flags"  OFF ALL)
diff --git a/INSTALL.cmake b/INSTALL.cmake
index ffe5866b00..4c8d4789f3 100644
--- a/INSTALL.cmake
+++ b/INSTALL.cmake
@@ -141,7 +141,6 @@ Build options
 -- LYX_ASPELL   = OFF: Require aspell
 -- LYX_ENCHANT  = OFF: Require Enchant
 -- LYX_HUNSPELL = OFF: Require Hunspell
--- LYX_DEVEL_VERSION= OFF: Build developer version
 -- LYX_RELEASE  = OFF: Build release version, build debug when disabled
 -- LYX_PACKAGE_SUFFIX   = ON : Use version suffix for packaging
 -- LYX_PCH  = OFF: Use precompiled headers
diff --git a/config/lyxinclude.m4 b/config/lyxinclude.m4
index b07bf38f24..ead704b166 100644
--- a/config/lyxinclude.m4
+++ b/config/lyxinclude.m4
@@ -33,7 +33,6 @@ AC_MSG_RESULT([$build_type])
 lyx_flags="$lyx_flags build=$build_type"
 case $build_type in
 development) lyx_devel_version=yes
- AC_DEFINE(DEVEL_VERSION, 1, [Define if you are building a development version of LyX])
 		 LYX_DATE="not released yet" ;;
 prerelease) lyx_prerelease=yes ;;
 esac
diff --git a/development/cmake/TODO.txt b/development/cmake/TODO.txt
index 45c1e0df84..32cf54b292 100644
--- a/development/cmake/TODO.txt
+++ b/development/cmake/TODO.txt
@@ -26,8 +26,6 @@ Bug fixing
 
 Documentation
   * Better documentation, variable naming, more automake-like
-  * what does LYX_DEVEL_VERSION do?
-  * What is the difference with LYX_RELEASE=OFF?
   * how do I specify whether I want debug informations (-g flag) for unix?
 
 
diff --git a/development/cmake/config.h.cmake b/development/cmake/config.h.cmake
index f0a504a81a..7fac0b00b5 100644
--- a/development/cmake/config.h.cmake
+++ b/development/cmake/config.h.cmake
@@ -24,12 +24,6 @@
 #endif
 
 
-#cmakedefine LYX_DEVEL_VERSION 1
-#if defined(LYX_DEVEL_VERSION)
-	#define DEVEL_VERSION 1
-#else
-	#undef DEVEL_VERSION
-#endif
 #cmakedefine PACKAGE "${PACKAGE}"
 #cmakedefine PACKAGE_VERSION "${PACKAGE_VERSION}"
 #define PACKAGE_STRING "LyX ${PACKAGE_VERSION}"
diff --git a/src/BufferView.cpp b/src/BufferView.cpp
index 2f256369f6..03e7723fd1 100644
--- a/src/BufferView.cpp
+++ b/src/BufferView.cpp
@@ -1391,7 +1391,7 @@ void

Re: Aw: Re: short report from LyX under Linux

2017-07-24 Thread Jean-Pierre Chrétien


Le 24/07/2017 à 16:21, Guenter Milde a écrit :

On 2017-07-24, Uwe Stöhr wrote:


My advice to new Linux folks is always to start with a 'mainstream'
distribution. I.e., start with Ubuntu.



The distribution is not the question.


It is, as with Debian or Ubuntu, you would have had a working LyX out of the
box.


Sure, the only reason why I don't use it  is that I need to run several
versions of LyX for translation needs, so I install texlive from tug.org.

--
Jean-Pierre

Re: [PATCH][RFC] Make "devel mode" configurable at run time


Le 24/07/2017 à 17:40, Guillaume MM a écrit :

The information is saved in the session file. Only the default value
depends on the compile-time #define.


It makes sense to me to entirely remove the compile-time switch.


I could do that indeed. I'll propose another iteration.

JMarc

Re: [LyX/master] Do not error on missing ZWNJ (ligature break) characters.

2017-07-24 Thread Jean-Pierre Chrétien


Le 23/07/2017 à 18:42, Juergen Spitzmueller a écrit :

commit a40868510d36ccdcf3c431cdee17f8204d4b258a
Author: Juergen Spitzmueller 
Date:   Sun Jul 23 18:41:06 2017 +0200

Do not error on missing ZWNJ (ligature break) characters.

Since TeXLive 2016, "fontspec" maps the ligature break command
\textcompwordmark to the ZWNJ character (U+200C).
This character is missing in many fonts (including the default: Latin
Modern) which leads to "Missing character" warnings in the XeTeX/LuaTeX
log file if a document using non-TeX fonts contains a ligature break.

LyX reports missing characters as error since fixing #9610.
In case of "invisible" characters, there is no data loss, in case of the
ZWNJ the functionality is kept: ligatures are prevented also if the ZWNJ
is missing in a font.

Therefore, a missing ZWNJ is now treated similar to missing characters
in "nullfont" (see [63f41711/lyxgit], bug #10394) and does not trigger
an error.

Fixes: #10727


Works fine with Additional.lyx and system fonts in German.
In French, leaves correctly errors on em dashes non existing in the selected 
font.
I replaced these em dashes by parentheses to avoid test errors.

--
Jean-Pierre


---
 src/LaTeX.cpp |   17 -
 1 files changed, 12 insertions(+), 5 deletions(-)

diff --git a/src/LaTeX.cpp b/src/LaTeX.cpp
index a768c99..1054064 100644
--- a/src/LaTeX.cpp
+++ b/src/LaTeX.cpp
@@ -936,11 +936,18 @@ int LaTeX::scanLogFile(TeXErrors & terr)
// Warning about missing glyph in selected font
// may be dataloss (bug 9610)
// but can be ignored for 'nullfont' (bug 
10394).
-   retval |= LATEX_ERROR;
-   terr.insertError(0,
-from_local8bit("Missing 
glyphs!"),
-from_local8bit(token),
-child_name);
+   // as well as for ZERO WIDTH NON-JOINER 
(0x200C) which is
+   // missing in many fonts and output for 
ligature break (bug 10727).
+   // Since this error only occurs with utf8 
output, we can safely assume
+   // that the log file is utf8-encoded
+   docstring const utoken = from_utf8(token);
+   if (!contains(utoken, 0x200C)) {
+   retval |= LATEX_ERROR;
+   terr.insertError(0,
+from_ascii("Missing 
glyphs!"),
+utoken,
+child_name);
+   }
} else if (!wait_for_error.empty()) {
// We collect information until we know we have 
an error.
wait_for_error += token + '\n';

Re: [PATCH][RFC] Make "devel mode" configurable at run time

2017-07-24 Thread Guillaume MM


Le 24/07/2017 à 16:23, Jean-Marc Lasgouttes a écrit :

Hi,

Anyone against putting this in master?

JMarc


0001-Make-devel-mode-configurable-at-run-time.patch


 From 5488f8f06eae75bf2265e88a344be246130b9ada Mon Sep 17 00:00:00 2001
From: Jean-Marc Lasgouttes
Date: Mon, 24 Jul 2017 00:21:43 +0200
Subject: [PATCH] Make "devel mode" configurable at run time

Traditionally LyX behaves differently when the directive DEVEL_VERSION
is defined at compile time. This covers
* more detailed description of current position in status bar
* the help files are open in read/write mode
* more detailed debug output in the View Source panel

This patch introduces the new function devel-mode-toggle that allows
to use devel mode in stable releases, and vice versa.


Sounds good.



The information is saved in the session file. Only the default value
depends on the compile-time #define.


It makes sense to me to entirely remove the compile-time switch.

Guillaume

Re: short report from LyX under Linux


Le 24/07/2017 à 17:23, Tommaso Cucinotta a écrit :

Ubuntu way, AFAIK:
-) Depends means LyX would be totally broken without them, e.g., you 
wouldn't be able to launch LyX, thus there's no way to install LyX 
without its dependencies, unless you're an advanced user, you know what 
you're doing, you like to use the command-line and the "--force" flags, 
ignoring any warning you get about things that may get broken afterwards
-) Recommends means the average user probably needs this as well, so 
it's also pulled in by default, unless the user explicitly decides to 
skip them (command-line with --no-install-recommends, probably there are 
similar options in some GUI tool)
-) Suggests means if you like to have a complete installation with all 
possible features, then install these as well (command-line with 
--install-suggests, or likely using some GUI tool)


Thanks for the explanation. So recommend and depends are the things that 
count in practice.


That suits me well.

JMarc

Re: short report from LyX under Linux


On 24/07/2017 16:24, Jean-Marc Lasgouttes wrote:

I am not sure what the difference between recommend and require is in practice. 
Could you expand on that?


Ubuntu way, AFAIK:
-) Depends means LyX would be totally broken without them, e.g., you wouldn't be able to 
launch LyX, thus there's no way to install LyX without its dependencies, unless you're an 
advanced user, you know what you're doing, you like to use the command-line and the 
"--force" flags, ignoring any warning you get about things that may get broken 
afterwards
-) Recommends means the average user probably needs this as well, so it's also 
pulled in by default, unless the user explicitly decides to skip them 
(command-line with --no-install-recommends, probably there are similar options 
in some GUI tool)
-) Suggests means if you like to have a complete installation with all possible 
features, then install these as well (command-line with --install-suggests, or 
likely using some GUI tool)

T.

Re: short report from LyX under Linux


On 24/07/2017 10:30, "Uwe Stöhr" wrote:

I think that explains why software companies don't offer Linux versions.


Just a couple of well-known names...

  https://www.redhat.com/en/store/linux-platforms
  
https://buy.ubuntu.com/?_ga=2.96387035.693003821.1500908991-595300039.1443300335
  
https://platforms.linaro.org/documentation/Reference-Platform/Platforms/Enterprise/README.md/
  https://android.googlesource.com/

Linux is used on billion machines nowadays :-), albeit big numbers are 
especially for servers and mobile devices, not so much for desktops.

T.

Re: Aw: Re: short report from LyX under Linux

On 2017-07-24, Uwe Stöhr wrote:

>> My advice to new Linux folks is always to start with a 'mainstream'
>> distribution. I.e., start with Ubuntu.

> The distribution is not the question. 

It is, as with Debian or Ubuntu, you would have had a working LyX out of the
box.

> The point is that users start LyX and get a cryptic error message
> instead of a PDF document. The vast majority of users don't care about
> what is going on in the background, they want programs to just work out
> of the box. I mean with LibreOffice under Linux one can just begin to
> write, with LyX one cannot.

Not under all Linuxes, but under your distribution.

> That is why I spent so much time to get everything to work on Windows
> by just clicking OK a few time in the installer. And my thought is that
> when it works on Windows, it must work on Linux too.

However, the work you did for Windows is done by the "packagers" from the
various distributions under Linux. Hence your mileage regarding LyX may vary
from distro to distro and you should report to the distro the startup
problems you had with LyX (or switch the distro).

Günter

Re: short report from LyX under Linux


Le 24/07/2017 à 16:16, Guenter Milde a écrit :

As under Debian, LyX "recommends" this package (it is installed by default
if you install LyX), the UserGuide compiles out of the box with an default
install.


I am not sure what the difference between recommend and require is in 
practice. Could you expand on that?


JMarc

[PATCH][RFC] Make "devel mode" configurable at run time


Hi,

Anyone against putting this in master?

JMarc

>From 5488f8f06eae75bf2265e88a344be246130b9ada Mon Sep 17 00:00:00 2001
From: Jean-Marc Lasgouttes 
Date: Mon, 24 Jul 2017 00:21:43 +0200
Subject: [PATCH] Make "devel mode" configurable at run time

Traditionally LyX behaves differently when the directive DEVEL_VERSION
is defined at compile time. This covers
* more detailed description of current position in status bar
* the help files are open in read/write mode
* more detailed debug output in the View Source panel

This patch introduces the new function devel-mode-toggle that allows
to use devel mode in stable releases, and vice versa.

The information is saved in the session file. Only the default value
depends on the compile-time #define.
---
 src/BufferView.cpp |  2 +-
 src/Cursor.cpp | 23 ---
 src/Cursor.h   |  4 ++--
 src/FuncCode.h |  1 +
 src/LyXAction.cpp  | 13 +
 src/Text.cpp   | 34 +-
 src/Text.h |  4 ++--
 src/frontends/qt4/GuiApplication.cpp   |  7 +--
 src/frontends/qt4/GuiCommandBuffer.cpp |  6 --
 src/frontends/qt4/GuiCommandBuffer.h   |  3 ---
 src/frontends/qt4/GuiView.cpp  | 28 +---
 src/frontends/qt4/GuiView.h|  5 +
 src/frontends/qt4/GuiViewSource.cpp| 27 ++-
 src/mathed/InsetMathHull.cpp   |  2 +-
 14 files changed, 94 insertions(+), 65 deletions(-)

diff --git a/src/BufferView.cpp b/src/BufferView.cpp
index 2f256369f6..03e7723fd1 100644
--- a/src/BufferView.cpp
+++ b/src/BufferView.cpp
@@ -1391,7 +1391,7 @@ void BufferView::dispatch(FuncRequest const & cmd, DispatchResult & dr)
 		break;
 
 	case LFUN_FONT_STATE:
-		dr.setMessage(cur.currentState());
+		dr.setMessage(cur.currentState(false));
 		break;
 
 	case LFUN_BOOKMARK_SAVE:
diff --git a/src/Cursor.cpp b/src/Cursor.cpp
index 1223782c35..b99ab6cb53 100644
--- a/src/Cursor.cpp
+++ b/src/Cursor.cpp
@@ -1057,7 +1057,7 @@ void Cursor::updateTextTargetOffset()
 }
 
 
-void Cursor::info(odocstream & os) const
+void Cursor::info(odocstream & os, bool devel_mode) const
 {
 	for (int i = 1, n = depth(); i < n; ++i) {
 		operator[](i).inset().infoize(os);
@@ -1069,6 +1069,14 @@ void Cursor::info(odocstream & os) const
 		if (inset)
 			prevInset()->infoize2(os);
 	}
+	if (devel_mode) {
+		InsetMath * math = inset().asInsetMath();
+		if (math)
+			os << _(", Inset: ") << math->id();
+		os << _(", Cell: ") << idx();
+		os << _(", Position: ") << pos();
+	}
+
 }
 
 
@@ -2106,23 +2114,16 @@ docstring Cursor::selectionAsString(bool with_label) const
 }
 
 
-docstring Cursor::currentState() const
+docstring Cursor::currentState(bool devel_mode) const
 {
 	if (inMathed()) {
 		odocstringstream os;
-		info(os);
-#ifdef DEVEL_VERSION
-		InsetMath * math = inset().asInsetMath();
-		if (math)
-			os << _(", Inset: ") << math->id();
-		os << _(", Cell: ") << idx();
-		os << _(", Position: ") << pos();
-#endif
+		info(os, devel_mode);
 		return os.str();
 	}
 
 	if (inTexted())
-		return text()->currentState(*this);
+		return text()->currentState(*this, devel_mode);
 
 	return docstring();
 }
diff --git a/src/Cursor.h b/src/Cursor.h
index d1e13f684e..5c675c493a 100644
--- a/src/Cursor.h
+++ b/src/Cursor.h
@@ -205,7 +205,7 @@ public:
 	///
 	docstring selectionAsString(bool with_label) const;
 	///
-	docstring currentState() const;
+	docstring currentState(bool devel_mode) const;
 
 	/// auto-correct mode
 	bool autocorrect() const { return autocorrect_; }
@@ -300,7 +300,7 @@ public:
 	/// access to owning BufferView
 	BufferView & bv() const;
 	/// get some interesting description of top position
-	void info(odocstream & os) const;
+	void info(odocstream & os, bool devel_mode) const;
 	/// are we in math mode (2), text mode (1) or unsure (0)?
 	int currentMode();
 	/// reset cursor bottom to the beginning of the top inset
diff --git a/src/FuncCode.h b/src/FuncCode.h
index 7949bce41a..92d5e35268 100644
--- a/src/FuncCode.h
+++ b/src/FuncCode.h
@@ -473,6 +473,7 @@ enum FuncCode
 	LFUN_BUFFER_ZOOM,   // daniel, 20161028
 	LFUN_TOOLBAR_MOVABLE,   // daniel, 20160712
 	LFUN_FONT_CROSSOUT, // uwestoehr 20170404
+	LFUN_DEVEL_MODE_TOGGLE, // lasgouttes 20170723
 	LFUN_LASTACTION // end of the table
 };
 
diff --git a/src/LyXAction.cpp b/src/LyXAction.cpp
index 56b810306e..6aaec92428 100644
--- a/src/LyXAction.cpp
+++ b/src/LyXAction.cpp
@@ -1396,6 +1396,19 @@ void LyXAction::init()
 
 
 /*!
+ * \var lyx::FuncCode lyx::LFUN_DEVEL_MODE_TOGGLE
+ * \li Action: toggle a mode where more information is given in UI
+ * \li Syntax: devel-mode-toggle
+ * \li Notion: in so called "devel" mode, the information given in the
+ * status bar is more precise, and the help

Re: short report from LyX under Linux

On 2017-07-24, Jean-Marc Lasgouttes wrote:
> Le 24/07/2017 à 14:18, mn a écrit :
>> – Simplify UserGuide in regard to dependencies

> Indeed. Personally, I never use enumitem :) There is probably a good 
> reason why it is not in the main texlive distribution.

Enumitem is in texlive. 

It is, however, a relatively new package. Therefore, Debian has it in
texlive-latex-extra.

As under Debian, LyX "recommends" this package (it is installed by default
if you install LyX), the UserGuide compiles out of the box with an default
install.

Günter

Re: short report from LyX under Linux


Le 24/07/2017 à 14:18, mn a écrit :

– Simplify UserGuide in regard to dependencies


Indeed. Personally, I never use enumitem :) There is probably a good 
reason why it is not in the main texlive distribution.


JMarc

Re: short report from LyX under Linux

2017-07-24 Thread mn

On 24.07.17 10:30, "Uwe Stöhr" wrote:
>> back to the UserGuide, perhaps what we could actually do is, to
>> simplify the UserGuide so that it can compile without the need for
>> installing additional packages besides a minimal latex
>> installation
> 
> The point is that almost nothing works out of the box. Not simple
> documents, not the tutorial. Because only texlive-bin package is
> installed together with LyX. I will report to the packagers that they
> should add more texlive packages to the install dependencies.

When I was new to LyX I suffered the same fate. "Nothing worked", since
I wanted to load the program, type new words, hit print and feel smug
(about using Latex). That was the way I used other apps, that was also
the way I interpreted how LyX was "advertised." We know it doesn't work
like that. Although splash.lyx still has this kind of 'false
advertising' in place.
Together with Uwe's experience, referring to 3,4 in splash.lyx
There it tries to hide too much of the the complexities involved.

Having a system within LyX to automagically pull all dependencies
on-the-fly might be attractive. But it's a huge task, not really
compatible with unix-philosophy in general, specific distros in
particular. For having UserGuide compiled it's also already covered with
having TeXLive-full installed.
Using LaTeX/LyX is not the same as using office-processors.

But currently UserGuide already says:
1.5 "You can edit documents in LyX without having LaTeX installed, but
you will not be able to create PDFs or print your documents unless you
do have it installed."

And it's been a while, but doesn't the "smaller" Win-installer lead a
potential new user into a similar situation?
On Mac LyX doesn't pull or offer MacTex/TeXLive, and I do not know what
happens if a frugal user chooses to try the much smaller basicTeX. On
debian nothing from TeXLive is in the depends section of the package
description.

What you bemoan is really different things:

Help-docs are nowadays usually built into the app, under 'Help' – LyX
has that. (But it's different enough from most other apps and their
concepts.)

Manuals, like UserGuide.lyx are usually shipped as PDFs, if at all – LyX
gives you a pretty readable source to generate these PDFs. This last
step may fail as we both learned be making mistakes. But you can read
the relevant info within LyX. That's several steps up from "lost". And
having a low-distracting _user-readable_ source is THE killer point for
LyX anyway.

You want a new user to be able to open an example file, hit compile and
then read the PDF and marvel about the "Beauty of TeX" – a Job for
Intro.lyx and "examples".

To not alienate new users. That is a noble goal I totally support. But
this suffers from the crux that total newbies will be bewildered with
the fact they have to compile PDFs in the first place. Among other
idiosyncrasies if being either a total neophyte or used to office apps.

None of these arguments are likely applicable for LyX-newbies coming the
other way: being fed up with plain text editors and the convoluted LaTeX
source display. When actually writing or (proof) reading LyX bests them all.

My conclusion from this presents several options:
– Amend the first-launch-ever readme splash.lyx.
Really urging totally new users with even stronger words to start their
way into LyX by opening and reading Intro and UserGuide, esp UG-1.5.
With further amendments concerning PDF generation and further
dependencies. Better explaining  there that LyX, as is, is just an
editor, but that it is really meant to be a a frontend on a huge
mountain of a system of software packages.
– Simplify UserGuide in regard to dependencies
–– test this on a wider range of likely base systems
– Maybe: attach a LyX-Note to the top of the respective docs listing
potentially unusual dependencies and how to get them (giving at least
optimized search engine search terms)

greetings
Mike

Re: [LyX/master] Account for spaces in paths in the windows reverse search proposals

2017-07-24 Thread Jürgen Spitzmüller

2017-07-24 13:28 GMT+02:00 Jürgen Spitzmüller :

> 2017-07-24 13:16 GMT+02:00 Enrico Forestieri :
>
>> Jürgen, the correct syntax is %~1 rather than ~%1. See:
>> https://stackoverflow.com/questions/28597379/what-does-1-do-
>> in-this-batch-file
>>
>>
> Thanks. Could you check and correct, please? I just used what was proposed
> on trac.
>

Never mind. I did it.

Thanks again
Jürgen


>
> Jürgen
>
>
>> --
>> Enrico
>>
>
>

Re: [LyX/master] Account for spaces in paths in the windows reverse search proposals

2017-07-24 Thread Jürgen Spitzmüller

2017-07-24 13:16 GMT+02:00 Enrico Forestieri :

> Jürgen, the correct syntax is %~1 rather than ~%1. See:
> https://stackoverflow.com/questions/28597379/what-does-
> 1-do-in-this-batch-file
>
>
Thanks. Could you check and correct, please? I just used what was proposed
on trac.

Jürgen


> --
> Enrico
>

Re: [LyX/master] Account for spaces in paths in the windows reverse search proposals

2017-07-24 Thread Enrico Forestieri

On Mon, Jul 24, 2017 at 11:14:54AM +0200, Juergen Spitzmueller wrote:

> commit bbb6318730f7383292e33f01baf687756de350b0
> Author: Juergen Spitzmueller 
> Date:   Mon Jul 24 11:14:00 2017 +0200
> 
> Account for spaces in paths in the windows reverse search proposals
> 
> Fixes: #10557
[...]
> -echo LYXCMD:revdvi:server-goto-file-row:%1 %2> 
> +echo LYXCMD:revdvi:server-goto-file-row:
> +\change_inserted -712698321 1500887411
> +~
> +\change_unchanged
> +%1 %2> 

Jürgen, the correct syntax is %~1 rather than ~%1. See:
https://stackoverflow.com/questions/28597379/what-does-1-do-in-this-batch-file

-- 
Enrico

Re: short report from LyX under Linux


Le 24/07/2017 à 10:30, "Uwe Stöhr" a écrit :

Hmm, that is very bad. I think that explains why software companies don't offer 
Linux versions. (I saw yesterday that there are no longer Skype, Adobe Reader 
and other useful programs on Linux.)


Indeed Adobe Reader for Linux has been abandoned. Personnally I do not 
regret it and I always install SumatraPDF on windows.


Concerning Skype, you should probably change your favorite source of 
information:

https://wiki.archlinux.org/index.php/skype

Basically, now Skype works in your web browser (and the application is 
just a wrapper around that), courtesy of the open source actors 
(Mozilla, Google) who worked on the WebRTC standard. Isn't that nice ? ;)


JMarc

Re: short report from LyX under Linux

2017-07-24 Thread Michael Berger




Am 24.07.2017 um 10:30 schrieb "Uwe Stöhr":

back to the UserGuide, perhaps what we could actually do is, to simplify

the UserGuide so that it can compile without the need for installing additional
packages besides a minimal latex installation

The point is that almost nothing works out of the box. Not simple documents, 
not the tutorial. Because only texlive-bin package is installed together with 
LyX. I will report to the packagers that they should add more texlive packages 
to the install dependencies.


I would recommend an established distribution, such as openSuse.

I haven't heard of this distro yet. I see now that Manjaro is on place 3 on 
Distrowatch while openSUSE is on place 6:
http://distrowatch.com
I googled around before I started and openSUSE was not recommended for 
beginners in any article I read. The top proposals for beginners in most 
articles were Mint, Ubuntu and Manjaro.


that's why I always install "vanilla" TeXLive instead of the distribution's).

https://www.tug.org/texlive/acquire-netinstall.html

Many thanks, I will try this out.


Manjaro seems to ship its own (command line) package manager ("TeXLive

Local Manager): https://wiki.archlinux.org/index.php/TeX_Live

I found it by googling and it seems to be installed but I cannot find it. But 
as you know I cannot use command lines because I don't know the commands and 
forget them all the time if I don't use them frequently. That was the reason 
why I came to LyX - because I forgot all the time the different LaTeX commands.


The packagers of a distribution decide which dependencies a package has. 
Nothing _we_ can do here.

Hmm, that is very bad. I think that explains why software companies don't offer 
Linux versions. (I saw yesterday that there are no longer Skype, Adobe Reader 
and other useful programs on Linux.) Giving support for all the different 
dozens of distributions would be a nightmare if every distribution decides on 
its own what to install with a program and what not.

regards Uwe

Hi Uwe,
of course you are entitled to have your own opinion on what is right or 
wrong, good or bad. But sorry, your explanation re software companies 
not offering Linux versions is far fetched and daring. And what is your 
last sentence for - who asked your opinion on the opensource idea? 
Thinking twice may help sometimes.

Cheers,
Michael

Re: [LyX/master] Copy documentation of new features of Additional.lyx in de, es, fr and ja documentation files as change tracking and remove chnage tracking in Additional.lyx

On 2017-07-23, Jean-Pierre Chrétien wrote:
> Le 16/07/2017 à 04:23, Scott Kostyshak a écrit :
>> On Wed, Jul 12, 2017 at 10:34:53PM +0200, jpc wrote:
>>> commit c9f398d7c516f9e9f3df71e74231a87e639180b9
>>> Author: jpc 
>>> Date:   Wed Jul 12 22:31:30 2017 +0200

>>>Copy documentation of new features of Additional.lyx in de, es, fr 
>>> and ja documentation files
>>>as change tracking and remove chnage tracking in Additional.lyx

> The 'Missing glyphs' error with system fonts and xelatex was present at 
> 94479240, before this commit. 

> FYI, I get the missing glyph error with 
> Additional.lyx in system fonts mode whatever the language. 

This should be fixed by Jürgen's patch for ZWNJ
[a40868510d36ccdcf3c431cde].

> In French, I get supplementary errors wirh emdash and endash
> characters.

The EM- and EN-DASH are present in LatinModern. 

After a split and try orgy, I found that the errors are due to missing
2015HORIZONTAL BAR = quotation dash
* long dash introducing quoted text).

This may be masked in the export tests by Kornels script-based replacement
of the default non-TeX fonts with FreeSerif/-Sans/-Mono.

Grep points to:

Additional.lyx:1918:―
Additional.lyx:10468:― 
Additional.lyx:10552: ― 
Additional.lyx:21842:― 
Additional.lyx:21856:― 

Jean-Pierre,
could you please have a look, whether this is intended or an em-dash
could/should be used at these places?

Merci,
Günter

Re: CMake deprecation warnings

Am Sonntag, 23. Juli 2017 um 23:41:58, schrieb Uwe Stöhr 
> I just updated master and the 2.2.x branch to check if I can compile. 
> This worked but I get now 4 CMake deprecation warnings:
> 
> CMake Deprecation Warning at CMakeLists.txt:40 (cmake_policy):
>The OLD behavior for policy CMP0003 will be removed from a future 
> version of CMake.
> The cmake-policies(7) manual explains that the OLD behaviors of all
>policies are deprecated and that a policy should be set to OLD only 
> under specific short-term circumstances.  Projects should be ported to 
> the NEW behavior and not rely on setting a policy to OLD.
> 
> CMake Deprecation Warning at CMakeLists.txt:41 (cmake_policy):
>The OLD behavior for policy CMP0005 will be removed from a future ...
> 
> CMake Deprecation Warning at CMakeLists.txt:45 (cmake_policy):
>The OLD behavior for policy CMP0020 will be removed from a future...
> 
> CMake Deprecation Warning at CMakeLists.txt:48 (cmake_policy):
>The OLD behavior for policy CMP0028 will be removed from a future...
> 
> Kornel, should we ignore them or are they a result because I updated to 
> CMake 3.9?

Yes please, ignore. It happens only with CMake 3.9, and I did not dare to
butcher the code without enough testing.

> thanks and regards
> Uwe

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: short report from LyX under Linux


Le 24/07/2017 à 10:30, "Uwe Stöhr" a écrit :

The point is that almost nothing works out of the box. Not simple documents, 
not the tutorial. Because only texlive-bin package is installed together with 
LyX. I will report to the packagers that they should add more texlive packages 
to the install dependencies.


I guess the one you have to reach are the Arch Linux maintainers. Like 
the packaging for LyX on Ubuntu is really done by debian people.



The packagers of a distribution decide which dependencies a package has. 
Nothing _we_ can do here.


Hmm, that is very bad. I think that explains why software companies don't offer 
Linux versions. (I saw yesterday that there are no longer Skype, Adobe Reader 
and other useful programs on Linux.) Giving support for all the different 
dozens of distributions would be a nightmare if every distribution decides on 
its own what to install with a program and what not.


I see that texlive-latexextra is mentioned as optional dependency:
https://www.archlinux.org/packages/extra/i686/lyx/

I do not know though how this appears in the installation UI. From what 
I read, it seems that it is indicated at some point when you install the 
package.


JMarc

Re: short report from LyX under Linux

> back to the UserGuide, perhaps what we could actually do is, to simplify 
the UserGuide so that it can compile without the need for installing additional 
packages besides a minimal latex installation

The point is that almost nothing works out of the box. Not simple documents, 
not the tutorial. Because only texlive-bin package is installed together with 
LyX. I will report to the packagers that they should add more texlive packages 
to the install dependencies.

> I would recommend an established distribution, such as openSuse.

I haven't heard of this distro yet. I see now that Manjaro is on place 3 on 
Distrowatch while openSUSE is on place 6:
http://distrowatch.com
I googled around before I started and openSUSE was not recommended for 
beginners in any article I read. The top proposals for beginners in most 
articles were Mint, Ubuntu and Manjaro.

> that's why I always install "vanilla" TeXLive instead of the distribution's).
https://www.tug.org/texlive/acquire-netinstall.html

Many thanks, I will try this out.

> Manjaro seems to ship its own (command line) package manager ("TeXLive
Local Manager): https://wiki.archlinux.org/index.php/TeX_Live

I found it by googling and it seems to be installed but I cannot find it. But 
as you know I cannot use command lines because I don't know the commands and 
forget them all the time if I don't use them frequently. That was the reason 
why I came to LyX - because I forgot all the time the different LaTeX commands.

> The packagers of a distribution decide which dependencies a package has. 
> Nothing _we_ can do here.

Hmm, that is very bad. I think that explains why software companies don't offer 
Linux versions. (I saw yesterday that there are no longer Skype, Adobe Reader 
and other useful programs on Linux.) Giving support for all the different 
dozens of distributions would be a nightmare if every distribution decides on 
its own what to install with a program and what not.

regards Uwe

Aw: Re: short report from LyX under Linux

> My advice to new Linux folks is always to start with a 'mainstream'
> distribution. I.e., start with Ubuntu.

The distribution is not the question. Although I can recommend Manjaro because 
I got a new OS after just an hour and everything worked out of the box 
(booting, hardware and software) and I don't need to use a console neither for 
installing nor for settings.

The point is that users start LyX and get a cryptic error message instead of a 
PDF document. The vast majority of users don't care about what is going on in 
the background, they want programs to just work out of the box. I mean with 
LibreOffice under Linux one can just begin to write, with LyX one cannot. So 
what program would people use? So we are loosing many potential users because 
of this problem.
That is why I spent so much time to get everything to work on Windows by just 
clicking OK a few time in the installer. And my thought is that when it works 
on Windows, it must work on Linux too.

@ Paul: Manjaro uses packages from Arch Linux. After installing all texlive 
packages, I cannot open the TeXLive manager. There is no program called tlmgr 
or so. I will investigate what I can do. However, what user will invest an hour 
to get a program running? All other programs like Gimp, Inkscape, Audacity etc. 
work out of the box but LyX not.

> If you have some other old, underpowered machine,

As I wrote it is a brand new laptop. At first I started with XFCE but there I 
missed many things. I switched to the KDE version and I am confident with this 
surface.

regards Uwe

Re: short report from LyX under Linux


On 24/07/2017 08:16, Jürgen Spitzmüller wrote:

One of the first steps was of course to try out LyX. Unfortunately I
could not compile the UserGuide because of the missing package
enumitem.
I wanted to install it but cannot find it. there is also no texlive
program to start to install the missing package there - or better to
install missing packages automatically.
How can I do this?


on a Debian-based system (e.g., Ubuntu, which I'm using), you'd get some
hint with apt-cache search :

:~$ apt-cache search enumitem
texlive-lang-german - TeX Live: German
texlive-latex-extra - TeX Live: LaTeX additional packages

Package management in Linux distributions is quite flexible, so packages
usually come with a set of dependencies, i.e., other software packages
that have to be installed in order to let your new package work, and a
set of additional recommended and/or suggested packages, which are not
mandatory, but allow you to do more with your new package.

This is for example this info in the LyX package on Ubuntu:

:~$ apt-cache show lyx
...

Depends: libboost-signals1.62.0, libc6 (>= 2.15), libenchant1c2a (>= 1.6.0), libgcc1 (>= 1:3.0), 
libmagic1 (>= 5.12), libmythes-1.2-0, libqt5core5a (>= 5.6.0~beta), libqt5gui5 (>= 5.2.0) | 
libqt5gui5-gles (>= 5.2.0), libqt5svg5 (>= 5.6.0~beta), libqt5widgets5 (>= 5.6.0~beta), libstdc++6 
(>= 5.2), zlib1g (>= 1:1.1.4), lyx-common (= 2.2.2-1), xdg-utils

Recommends: texlive-latex-recommended, texlive-latex-extra, texlive-science, 
texlive-generic-recommended, texlive-generic-extra, texlive-fonts-recommended, 
preview-latex-style, dvipng, imagemagick, psutils, ghostscript, poppler-utils, 
fonts-lyx, evince-gtk | pdf-viewer, elyxer | tex4ht | hevea | tth | latex2html

Suggests: rcs, latex-xcolor, groff, libtiff-tools, gnuhtml2latex, wv, chktex, 
noweb, sgmltools-lite, linuxdoc-tools, writer2latex, latex2rtf, librsvg2-bin | 
inkscape, texlive-xetex, lyx-dbg (= 2.2.2-1)


Description-en: document processor
 LyX is an almost WYSIWYG-frontend for LaTeX. It makes the power and
...
 You can extend the functionality of LyX by installing these packages:
  * chktex: check for typographical errors
  * gnuhtml2latex: import HTML documents
  * groff: improved table formatting in plain text exports
  * latex-xcolor: for coloured change tracking
  * librsvg2-bin, inkscape: use the SVG image format in LyX documents
  * linuxdoc-tools: export SGML LinuxDoc documents
  * mythes-*: use the OpenOffice.org/LibreOffice Thesaurus
  * noweb: import noweb files
  * rcs: integrated version control
  * sgmltools-lite: export SGML DocBook documents
  * texlive-xetex: use the XeTeX typesetting system
  * wv: import MS Word documents

Now, back to the UserGuide, perhaps what we could actually do is, to simplify 
the UserGuide so thatit can compile without the need for installing additional 
packages besides a minimal latex installation ?

Anyway, the problem is that, technically, LyX can be used without even latex on 
your system :-)... you're perfectly able to *edit* a LyX document without 
having to compile it, right :-) ? Guess that's the rationale behind texlive-* 
packages being among the Recommended ones, not the Depends ones, in the pkg 
metadata.
However, Ubuntu for example seems to install Recommended packages by default (unless 
you do an explicit: apt-get install --no-install-recommends ), while 
Suggested ones are up to the user to install. Your distributions might come with a 
more minimalistic policy.

Another thing LyX might do, is to provide useful hints to the (newbie) user, as 
to why the compilation is failing, and how to fix that on a few common Linux 
distributions, e.g., pointing to a community wiki page where common issues of 
this kind are addressed.

My2c,

T.

Re: short report from LyX under Linux