Am 23.01.2017 um 15:06 schrieb Guenter Milde <mi...@users.sf.net>:
>
> On 2017-01-22, Stephan Witt wrote:
>> Am 11.01.2017 um 21:57 schrieb Guenter Milde <mi...@users.sf.net>:
>
>>> I added some X-Apps just behind their anchestors (GNOME equivalents) to
>>> configure.py.
>
> ...
>
>> What if some command in this list does different things on different
>> platforms?
>
> In case of a program name belonging to some out-of-scope program on a
> platform, we have to refine the checks:
>
> * placing a "catchall" for the platform in question before the false
> friend, or
> * adding a platform check to the configure script and use different lists.
>
>> ATM, the command xed on Mac is presumable comparable with xed on Linux.
>> It’s the Xcode editor (from the man page: The xed tool launches the
>> Xcode application and opens the given documents, or opens a new
>> untitled document, optionally with the contents of standard in).
>
> Fortunately, this seems still a good choice to have a look at text files and
> LaTeX sources. If there is a better (or more obvious) choice for the Mac, we
> can insert it at an earlier location (after checking it does not interfere
> with
> other plattforms;)
I’m trying to understand the current situation on a Mac and there are some
questions.
The flow as I understood it is as follows:
1. configure.py checks for an editor and an viewer - but not always
2. in case of a tested but missing editor/viewer this results in „auto“
3. at runtime LyX tests a given format with a command or „auto“ for an
OS-defined command (on Mac and Windows)
4. this test is made by the first extension only (e.g jpg for {„jpg“,“jpeg“})
5. if a matching command is found the viewer/editor is set to „auto“
(regardless of the command at configure time)
6. if a command has an editor but no viewer is expected by configure.py the
viewer remains undefined (see 1)
Why all these tests in step 2?
Why is an editor not an viewer too?
Where is a viewer used by LyX? (I didn’t find the time to look it up myself)
Why not testing for all extensions until a matching command is there?
Why not using the mime-types at all?
I don’t ask you to answer these questions. I only want to clarify that ATM it
doesn’t matter
if configure.py finds „xed“ or something else for e.g. the „asciichess“ format.
Stephan
