[LyX/master] Amend(1) 689f26d2: Add default path to server pipe (cmake build)

Stephan Witt st.witt at gmx.net
Sat Apr 18 20:11:36 UTC 2020


Am 18.04.2020 um 21:44 schrieb Kornel Benko <kornel at lyx.org>:
> 
> Am Sat, 18 Apr 2020 21:11:28 +0200
> schrieb Stephan Witt <st.witt at gmx.net>:
> 
>> Am 18.04.2020 um 21:00 schrieb Kornel Benko <kornel at lyx.org>:
>>> 
>>> Am Sat, 18 Apr 2020 20:11:01 +0200
>>> schrieb Stephan Witt <st.witt at gmx.net>:
>>> 
>>>> Am 18.04.2020 um 15:58 schrieb Kornel Benko <kornel at lyx.org>:  
>>>>> 
>>>>> Am Sat, 18 Apr 2020 11:47:18 +0200
>>>>> schrieb Stephan Witt <st.witt at gmx.net>:
>>>>> 
>>>>>> Am 18.04.2020 um 08:50 schrieb Kornel Benko <kornel at lyx.org>:    
> 
> ...
> 
>>>> Yes, we could. But it doesn’t change anything, AFAICS.   
>>> 
>>> Good.  
>> 
>> It’s good that it changes nothing? :)
> 
> Yes, because I did not want to change the behaviour for normal user.
> 
> ...
>>> Using lyx2.3 Skim finds the correct lyxeditor, but if you use lyx2.4 it does not.
>>> Or vice versa. You are never on the really safe side.  
>> 
>> Why shouldn’t that work? I can install only one of the LyX versions at the same time 
>> at the „well known“ location. And then it works with the currently installed one.
> 
> If you use versioned lyx, you can install more than one version side by side.
> Are you saying, you never done it?

Yes, it’s possible. But not at the same location. /Applications/LyX.app is 2.3 or 2.4
but not at the same time. And Skim looks there as I said.

One can change Skim’s preference to look at some other place -
but unfortunately there is no automatic solution for this.

It doesn’t matter what version is used. lyxeditor is able to lookup the pipe location
to direct the reverse lookup command of Skim to the running LyX instance.

>> Again, I don’t see what the goal or use case of your change is.
>> 
>> A developer should be able to modify the environment to fit the task to solve.
>> A user should be able to use it out-of-the-box w/o any trouble.
> 
> +1
> 
>>> I would like to have nearly same handling for unix, Windows and MacOSX, that's why.  
>> 
>> That’s not possible anyway.
> 
> True, but trying to unify most things is not wrong IMHO.

Yes.

My primary goal is to not break a working solution.

Stephan


More information about the lyx-devel mailing list