Hi Lior, On Tue, Feb 10, 2015 at 4:23 AM, Lior Silberman <lior3.1...@gmail.com> wrote: > Hi, > > A few days ago I realized that I'd like to locally add and change > definitions in /usr/share/lyx/symbols, and that existing code expects > me to copy the whole file to ~/.lyx and then edit it. This didn't make > sense, so the attached patch (against current git) allows the symbol > file to recursively include other files. This allows ~/.lyx/symbols > to include the system-wide file before making changes. I should > probably implement "remove" semantics as well, but this is enough for > me at the moment.
I'm curious -- what is the use case here? Do you have custom LaTeX definitions and you want to provide symbols for them? Or do you add support for more packages? The reason I'm asking is maybe we would like to have some of it upstream. I'm trying to think about how what you're proposing is consistent with other situations in LyX. For the bind file, we don't require the user to copy the lib bind. We just add on anything in the user bind. So that seems consistent. On the other hand, for layouts you need to copy the entire file, which also makes sense to me. > The one downsite to this is an interaction with the script > <development/tools/generate_symbols_images.py> which uses debug output > from the symbol-reading code. If a symbol is redefined the script > will see it twice. I'm not sure if that's a problem. > > Cheers, > Lior > > PS: I am not subscribed to the list. Too bad, it would be nice to have another LyX hacker around :) Scott
