Re: Understanding the /origin parameter

2015-05-25 Thread Enrico Forestieri
On Mon, May 25, 2015 at 03:19:00PM +0200, Stephan Witt wrote: > > > > Stephan, please can you check whether the attached patch works on Mac? > > For testing it, as an example, first save lib/examples/thesis/thesis.lyx > > in the current format (this is important) and then install LyX as you > > us

Re: Understanding the /origin parameter

2015-05-25 Thread Stephan Witt
Am 24.05.2015 um 20:18 schrieb Enrico Forestieri : > On Mon, May 18, 2015 at 10:09:42AM +0200, Stephan Witt wrote: > >> Am 18.05.2015 um 09:17 schrieb Enrico Forestieri : >> >>> On Sun, May 17, 2015 at 11:54:41PM -0700, Pavel Sanda wrote: Scott Kostyshak wrote: > When I am working on th

Re: Understanding the /origin parameter

2015-05-24 Thread Enrico Forestieri
On Mon, May 18, 2015 at 10:09:42AM +0200, Stephan Witt wrote: > Am 18.05.2015 um 09:17 schrieb Enrico Forestieri : > > > On Sun, May 17, 2015 at 11:54:41PM -0700, Pavel Sanda wrote: > >> Scott Kostyshak wrote: > >>> When I am working on the documentation, any save now adds the following: > >>> >

Re: Understanding the /origin parameter

2015-05-20 Thread Enrico Forestieri
On Wed, May 20, 2015 at 10:07:02AM +0200, Jean-Marc Lasgouttes wrote: > Le 19/05/2015 21:42, Enrico Forestieri a écrit : > >I will rarely use this feature, if ever at all. I was simply asked to > >solve a bug. I proposed a patch; there was a discussion lasting for > >a week on the bug tracker; all

Re: Understanding the /origin parameter

2015-05-20 Thread Jean-Marc Lasgouttes
Le 19/05/2015 21:42, Enrico Forestieri a écrit : I will rarely use this feature, if ever at all. I was simply asked to solve a bug. I proposed a patch; there was a discussion lasting for a week on the bug tracker; all interested parties were in cc. Nobody objected, someone appreciated. I committe

Re: Understanding the /origin parameter

2015-05-19 Thread Georg Baum
Enrico Forestieri wrote: > On Tue, May 19, 2015 at 08:42:45PM +0200, Georg Baum wrote: >> >> I understand the use case for the origin parameter, and I think there >> will be users who appreciate it, but if I don't need it (e.g. because I >> always store relative file names and do only move the co

Re: Understanding the /origin parameter

2015-05-19 Thread Enrico Forestieri
On Tue, May 19, 2015 at 08:42:45PM +0200, Georg Baum wrote: > Enrico Forestieri wrote: > > > On Tue, May 19, 2015 at 11:09:26AM +0200, Jean-Marc Lasgouttes wrote: > >> Le 18/05/2015 20:15, Enrico Forestieri a écrit : > >> >>Something with less magic and more predictability? > >> > > >> >It's magic

Re: Understanding the /origin parameter

2015-05-19 Thread Pavel Sanda
Jean-Marc Lasgouttes wrote: > Le 18/05/2015 20:15, Enrico Forestieri a écrit : >>> Something with less magic and more predictability? >> >> It's magic and it's very predictable. An alternative to reverting >> would be introducing a preference to allow storing the \origin tag >> in the file. Without

Re: Understanding the /origin parameter

2015-05-19 Thread Georg Baum
Enrico Forestieri wrote: > On Tue, May 19, 2015 at 11:09:26AM +0200, Jean-Marc Lasgouttes wrote: >> Le 18/05/2015 20:15, Enrico Forestieri a écrit : >> >>Something with less magic and more predictability? >> > >> >It's magic and it's very predictable. An alternative to reverting >> >would be intro

Re: Understanding the /origin parameter

2015-05-19 Thread Jean-Marc Lasgouttes
Le 19/05/2015 11:50, Enrico Forestieri a écrit : I would rather avoid introducing a new pref. If the concern is really the disclosure of a local path, it could also be avoided by encrypting the path using a key. Then, only lyx (and who is able to know the key and the used algorithm, of course) wo

Re: Understanding the /origin parameter

2015-05-19 Thread Enrico Forestieri
On Tue, May 19, 2015 at 11:09:26AM +0200, Jean-Marc Lasgouttes wrote: > Le 18/05/2015 20:15, Enrico Forestieri a écrit : > >>Something with less magic and more predictability? > > > >It's magic and it's very predictable. An alternative to reverting > >would be introducing a preference to allow stor

Re: Understanding the /origin parameter

2015-05-19 Thread Jean-Marc Lasgouttes
Le 18/05/2015 20:15, Enrico Forestieri a écrit : Something with less magic and more predictability? It's magic and it's very predictable. An alternative to reverting would be introducing a preference to allow storing the \origin tag in the file. Without that tag, everything would go as before.

Re: Understanding the /origin parameter

2015-05-19 Thread Kornel Benko
Am Dienstag, 19. Mai 2015 um 10:17:02, schrieb Enrico Forestieri > On Mon, May 18, 2015 at 05:28:41PM -0700, Pavel Sanda wrote: > > Enrico Forestieri wrote: > > > It's magic and it's very predictable. An alternative to reverting > > > would be introducing a preference to allow storing the \origin

Re: Understanding the /origin parameter

2015-05-19 Thread Enrico Forestieri
On Mon, May 18, 2015 at 05:28:41PM -0700, Pavel Sanda wrote: > Enrico Forestieri wrote: > > It's magic and it's very predictable. An alternative to reverting > > would be introducing a preference to allow storing the \origin tag > > in the file. Without that tag, everything would go as before. > >

Re: Understanding the /origin parameter

2015-05-18 Thread Pavel Sanda
Enrico Forestieri wrote: > It's magic and it's very predictable. An alternative to reverting > would be introducing a preference to allow storing the \origin tag > in the file. Without that tag, everything would go as before. I'm fine with any of the alternatives above. Pavel

Re: Understanding the /origin parameter

2015-05-18 Thread Enrico Forestieri
On Mon, May 18, 2015 at 11:14:19AM +0200, Jean-Marc Lasgouttes wrote: > Le 18/05/2015 11:07, Enrico Forestieri a écrit : > > >Anyway, I am ready to revert everything if this is wanted. > > I do not know whether reverting everything is what is needed. I do not feel > very at ease with a solution w

Re: Understanding the /origin parameter

2015-05-18 Thread Richard Heck
On 05/18/2015 05:09 AM, Jean-Marc Lasgouttes wrote: Le 18/05/2015 11:02, Enrico Forestieri a écrit : Yes, but user files will contain this information... Isn't there a way to avoid it at least when it is not useful? The user files already contain this information when storing absolute paths.

Re: Understanding the /origin parameter

2015-05-18 Thread Jean-Marc Lasgouttes
Le 18/05/2015 11:07, Enrico Forestieri a écrit : Sorry, I am not familiar about how things work on Mac. If you have an installer, you could replace those lines when they get installed but, again, I know nothing about Macs. The idea on Mac is to avoid having an installer, although it is obvious

Re: Understanding the /origin parameter

2015-05-18 Thread Enrico Forestieri
On Mon, May 18, 2015 at 11:09:25AM +0200, Jean-Marc Lasgouttes wrote: > Le 18/05/2015 11:02, Enrico Forestieri a écrit : > >>Yes, but user files will contain this information... Isn't there a way to > >>avoid it at least when it is not useful? > > > >The user files already contain this information

Re: Understanding the /origin parameter

2015-05-18 Thread Jean-Marc Lasgouttes
Le 18/05/2015 11:02, Enrico Forestieri a écrit : Yes, but user files will contain this information... Isn't there a way to avoid it at least when it is not useful? The user files already contain this information when storing absolute paths. If I recall correctly, you strongly wanted absolute pa

Re: Understanding the /origin parameter

2015-05-18 Thread Enrico Forestieri
On Mon, May 18, 2015 at 10:09:42AM +0200, Stephan Witt wrote: > Am 18.05.2015 um 09:17 schrieb Enrico Forestieri : > > > On Sun, May 17, 2015 at 11:54:41PM -0700, Pavel Sanda wrote: > >> Scott Kostyshak wrote: > >>> When I am working on the documentation, any save now adds the following: > >>> >

Re: Understanding the /origin parameter

2015-05-18 Thread Enrico Forestieri
On Mon, May 18, 2015 at 09:50:00AM +0200, Jean-Marc Lasgouttes wrote: > Le 18/05/2015 09:17, Enrico Forestieri a écrit : > >>Do we really have to ship author/login used in the machine? > >>I thought we have big fight already that we do not want to put > >>such kind of things without explicit permis

Re: Understanding the /origin parameter

2015-05-18 Thread Stephan Witt
Am 18.05.2015 um 10:09 schrieb Stephan Witt : > Am 18.05.2015 um 09:17 schrieb Enrico Forestieri : > >> On Sun, May 17, 2015 at 11:54:41PM -0700, Pavel Sanda wrote: >>> Scott Kostyshak wrote: When I am working on the documentation, any save now adds the following: +\origin /home/

Re: Understanding the /origin parameter

2015-05-18 Thread Stephan Witt
Am 18.05.2015 um 09:17 schrieb Enrico Forestieri : > On Sun, May 17, 2015 at 11:54:41PM -0700, Pavel Sanda wrote: >> Scott Kostyshak wrote: >>> When I am working on the documentation, any save now adds the following: >>> >>> +\origin /home/scott/lyxbuilds/master/repo/lib/templates/ >> >> Do we r

Re: Understanding the /origin parameter

2015-05-18 Thread Jean-Marc Lasgouttes
Le 18/05/2015 09:17, Enrico Forestieri a écrit : Do we really have to ship author/login used in the machine? I thought we have big fight already that we do not want to put such kind of things without explicit permission on the user side. There will not be any author/login used in the machine. W

Re: Understanding the /origin parameter

2015-05-18 Thread Enrico Forestieri
On Sun, May 17, 2015 at 11:54:41PM -0700, Pavel Sanda wrote: > Scott Kostyshak wrote: > > When I am working on the documentation, any save now adds the following: > > > > +\origin /home/scott/lyxbuilds/master/repo/lib/templates/ > > Do we really have to ship author/login used in the machine? > I

Re: Understanding the /origin parameter

2015-05-18 Thread Stephan Witt
Am 18.05.2015 um 08:54 schrieb Pavel Sanda : > Scott Kostyshak wrote: >> When I am working on the documentation, any save now adds the following: >> >> +\origin /home/scott/lyxbuilds/master/repo/lib/templates/ > > Do we really have to ship author/login used in the machine? > I thought we have bi

Re: Understanding the /origin parameter

2015-05-18 Thread Enrico Forestieri
On Sun, May 17, 2015 at 09:11:32PM -0400, Scott Kostyshak wrote: > When I am working on the documentation, any save now adds the following: > > +\origin /home/scott/lyxbuilds/master/repo/lib/templates/ > > I just want to confirm that when I commit, it is correct that this > will be added to the L

Re: Understanding the /origin parameter

2015-05-17 Thread Pavel Sanda
Scott Kostyshak wrote: > When I am working on the documentation, any save now adds the following: > > +\origin /home/scott/lyxbuilds/master/repo/lib/templates/ Do we really have to ship author/login used in the machine? I thought we have big fight already that we do not want to put such kind of t

Understanding the /origin parameter

2015-05-17 Thread Scott Kostyshak
When I am working on the documentation, any save now adds the following: +\origin /home/scott/lyxbuilds/master/repo/lib/templates/ I just want to confirm that when I commit, it is correct that this will be added to the LyX documentation files that we will ship. It is indeed expected, right? Scot