On Tuesday, June 27, 2023 at 2:41:21 PM UTC-5 tbp1...@gmail.com wrote: > I have several immediate reactions:
Thomas, I have no idea what you are afraid of. > This kind of proposal will create something new that is not a UNL and not a GNX. It's a UNL because *g.handleUNL* accepts it. It's a valid URL because *LeoQtLog.linkClicked* and *g.handleUrl* accept it. And now (in the latest push) Leo calls *urllib.parse.quote* and *urllib.parse.unquote* in better places so there is no need for weird special-case escapes scattered all over the code. > unl://ekr.leo#g.findUNL, will still not transfer to anyone else's computer or outline. It's still specific to ekr.leo. It already works for me. It will soon work for you provided that myLeoSettings.leo contains *@data unl_path_prefixes* setting that gives the full path to ekr.leo on *your* machine. Unls like this work for me in test.leo with a hack in *g.parsePathData* that uses a dict hard-coded paths to various .leo files. This hack simulates handling @data unl_path_prefixes. So it won't work for you just yet. But soon. *Summary* As you say, cross-file unls are nifty. They now work for both legacy and gnx-based unls. Little or nothing is going to break. leoSettings.leo now contains these settings: *@string unl-status-kind = legacy@bool full-unl-paths = True* Leo will work *exactly* as before with these settings. I know what I am doing. I am putting long hours of work into this project. Everything will soon work as we both want. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/88f70ccf-6f83-40a8-bf29-0534e0751aa6n%40googlegroups.com.
