I checked this on os x and get the same results:
*import osg.cls() # <-- does nothing on macos (darwin), probably same with linux since the procedure checks for "win" onlyg.es <http://g.es/>(os.path.expanduser('~'))# --> /Users/leodudeg.es <http://g.es/>(os.environ["HOME"])# --> /Users/leodudeg.es <http://g.es/>(c.expand_path_expression('~'))# --> ~g.es <http://g.es/>(c.expand_path_expression('$HOME'))# --> $HOME* It looks like there is opportunity to bring Leo into better usability with Linux-ey OS’s. Depending on how much I end up using Leo (I already spent more time in Leo than in emacs org-mode this week), I may be up for contributing towards that end - at least for macos. Subject to correction by Edward or some else who knows more, it looks like > the place to intervene is in c.expand_path_expression() because on even > on Linux it returns this: > > >>> c.expand_path_expression('~') > '~' > > This method is in the class *Commands*. I'm not sure how tricky this > would be to adjust, because you would only want to substitute > */home/{user}* for "~" if it appears at the start of a path expression, > and I don't know yet how to know. Also, it needs to be checked if a change > here would cause troubles anywhere else. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/998b612b-e585-4e0f-a047-6ed55587a85dn%40googlegroups.com.
