Skip to main content
8 events
when toggle format what by license comment
Oct 24, 2018 at 18:35 comment added user12563 Consider adding these paths conditionally depending on the value of system-type. I haven't tried it, but Emacs might try to look for elisp files in these directories and throw errors when it can't open them, because they don't exist.
Jan 31, 2018 at 14:30 comment added Adam Famous last words! Well, I have only one installation of Windows emacs. And I thought that was what I was using in cygwin too - but I just realised that would be contradictory. If cygwin was launching the Windows emacs, then I wouldn't need the cygwin version of the path in my .emacs. So I double-checked, and yes I have installed emacs-nox via the cygwin package manager.
Jan 31, 2018 at 14:25 comment added Adam Yes, absolutely.
Jan 27, 2018 at 21:39 comment added npostavs Hmm, are you sure you don't have two installations of emacs?
Jan 27, 2018 at 21:23 comment added Adam re cygwin vs windows 10 - would need to investigate further but emacs in cygwin doesn't load the file if I only put the windows format path. re ~/.emacs.d - I'll change that then. Thanks.
Jan 27, 2018 at 0:25 comment added npostavs By the way, it's not recommended to add ~/.emacs.d to load-path because some config files there could then shadow elisp files (e.g., ~/.emacs.d/bookmarks gets loaded instead of the real bookmarks.el). If your ..../OneDrive/.emacs.d isn't ~/.emacs.d/ then ignore this.
Jan 27, 2018 at 0:22 comment added npostavs You said "They both use the same installation of emacs", so shouldn't Emacs understand both kinds of path regardless of whether you start it from cmd.exe or cygwin bash (i.e., one of those entries should not be needed)?
Jan 26, 2018 at 18:01 history answered Adam CC BY-SA 3.0