hyperdrive.el added by ~alphapapa on ~ushin/ushin
Ticket created by ~alphapapa on ~ushin/ushin
While testing the behavior of
hyperdrive-open(andhyperdrive-open-url) when called on URLs to non-existent files, I noticed that, when the URL points to a writable hyperdrive (i.e. one's own hyperdrive), rather than showing a message about the URL pointing to a non-existent file, a buffer is opened for the file (i.e. like callingfind-fileon a non-existent filename). This feels slightly unintuitive, as it seems likehyperdrive-open-urlought to behave more like a Web browser, in that it should signal an error if the URL points to a non-existent file; i.e. it seems to me thathyperdrive-find-fileandhyperdrive-open-urlought to behave differently when trying to open non-existent files. To put it another way, this behavior makes it sometimes feel non-obvious whether a filename actually exists on one's own hyperdrive, as it makes it harder to distinguish the case of opening an existent vs. non-existent filename.
~alphapapa assigned ~alphapapa to #200 on ~ushin/ushin
~alphapapa assigned ~alphapapa to #198 on ~ushin/ushin
Comment by ~alphapapa on ~ushin/ushin
On Joseph's system, this doesn't always work without the improvements made to
plzin the yet-to-be-released v0.9.
REPORTED RESOLVED IMPLEMENTED
Comment by ~alphapapa on ~ushin/ushin
REPORTED RESOLVED NOT_OUR_BUG
Comment by ~alphapapa on ~ushin/ushin
AFAICT this was likely caused by our sometimes using
unload-feature, et al, and this problem does not happen outside of using that. Since that's not really a supported workflow in Emacs, it can't be considered a bug inpersist, so this should be safe to consider resolved.
REPORTED RESOLVED INVALID