Le 12/01/2016 21:04, Guillaume Munch a écrit :
For instance, \origin is going to cause problems if any collaborator
through a VCS decides to store his own local path (which is a setting
global to lyx!). Should we not set \origin unavailable when
store_user_preferences is false? (I am seriously a
Le 12/01/2016 19:36, Georg Baum a écrit :
Pavel Sanda wrote:
Guillaume Munch wrote:
I am not convinced by the naming vcs_simplify_format but maybe there are
other suggestions? What about save_transient_properties or save_state ?
I am fine with save_transient_properties as well. P
me too (a
On Tue, Jan 12, 2016 at 05:18:40PM +, Guillaume Munch wrote:
> Le 12/01/2016 02:23, Pavel Sanda a écrit :
> >Guillaume Munch wrote:
> Scott, do you sum up all these messages as a "+1", as you say?
After a quick look, I do think there is a +1.
Scott
signature.asc
Description: PGP signature
Pavel Sanda wrote:
> Guillaume Munch wrote:
>> I am not convinced by the naming vcs_simplify_format but maybe there are
>> other suggestions? What about save_transient_properties or save_state ?
>
> I am fine with save_transient_properties as well. P
me too (and I do not like vcs_simplify_format
Guillaume Munch wrote:
> I am not convinced by the naming vcs_simplify_format but maybe there are
> other suggestions? What about save_transient_properties or save_state ?
I am fine with save_transient_properties as well. P
Le 12/01/2016 02:23, Pavel Sanda a écrit :
Guillaume Munch wrote:
I understand this idea of "freezing" the setting, in order to set a
custom value on opening. The current approach I have in mind is to read
and save to a per-user-per-document (cursor-location-like) setting when
save_user_preferen
Guillaume Munch wrote:
> I understand this idea of "freezing" the setting, in order to set a
> custom value on opening. The current approach I have in mind is to read
> and save to a per-user-per-document (cursor-location-like) setting when
> save_user_preferences is false, so that the value on ope
Guillaume Munch wrote:
> Thus the per-user approach encompasses a wider set of use-cases,
> overlaps less with the current behaviour, and is simpler to explain and
> understand. Moreover, storing always the same value "false" is similar
> to what is done in LibreOffice's corresponding feature (sav
Le 11/01/2016 16:33, Guillaume Munch a écrit :
Thus the per-user approach encompasses a wider set of use-cases,
overlaps less with the current behaviour, and is simpler to explain and
understand. Moreover, storing always the same value "false" is similar
to what is done in LibreOffice's correspon
Le 11/01/2016 10:14, Jean-Marc Lasgouttes a écrit :
Le 11/01/2016 11:07, Pavel Sanda a écrit :
Kornel Benko wrote:
This all is getting more and more confusing. Too complicated (at
least for me)
You edit document.
You decide to use git.
You set up the look/behaviour things your care about ('Is
Am 11.01.2016 um 12:01 schrieb Kornel Benko :
>
> Am Montag, 11. Januar 2016 um 11:14:30, schrieb Jean-Marc Lasgouttes
>
>> Le 11/01/2016 11:07, Pavel Sanda a écrit :
>>> Kornel Benko wrote:
This all is getting more and more confusing. Too complicated (at least for
me)
>>>
>>> You ed
Am Montag, 11. Januar 2016 um 11:14:30, schrieb Jean-Marc Lasgouttes
> Le 11/01/2016 11:07, Pavel Sanda a écrit :
> > Kornel Benko wrote:
> >> This all is getting more and more confusing. Too complicated (at least for
> >> me)
> >
> > You edit document.
> > You decide to use git.
> > You set up
Le 11/01/2016 11:07, Pavel Sanda a écrit :
Kornel Benko wrote:
This all is getting more and more confusing. Too complicated (at least for me)
You edit document.
You decide to use git.
You set up the look/behaviour things your care about ('Is CT ON/OFF')
You freeze those settings so working wit
Kornel Benko wrote:
> This all is getting more and more confusing. Too complicated (at least for me)
You edit document.
You decide to use git.
You set up the look/behaviour things your care about ('Is CT ON/OFF')
You freeze those settings so working with git is less annoying.
.. and sometimes you
Am Montag, 11. Januar 2016 um 01:38:28, schrieb Pavel Sanda
> Georg Baum wrote:
> > Guillaume Munch wrote:
> >
> > > I agree that the current situation regarding \output_change and
> > > \tracking_change is bad and should be fixed. I gave what I think is the
> > > proper solution, taking into acc
Georg Baum wrote:
> Guillaume Munch wrote:
>
> > I agree that the current situation regarding \output_change and
> > \tracking_change is bad and should be fixed. I gave what I think is the
> > proper solution, taking into account the debate that was on the list.
> > The patch is very simple (see t
16 matches
Mail list logo
