* Helmut Eller m2tz7zgte5.fsf@common-lisp.net : Wrote on Fri, 16 Jan 2009 16:30:58 +0100:
| * Ariel Badichi [2009-01-14 17:30+0100] writes: |> I've been using it for a long time, and while I can re-introduce it |> myself, this recurring problem of seemingly random tweaking of |> keybindings and other kinds of user-visible behavior certainly deters |> one from updating to the latest version of slime. I would like to |> see such modifications at least being discussed on the mailing list |> and given a rationale prior to their check-in. | | Well, I will just put it back then.
Could you also revert another user visibile behaviour which changed -- this one was changed to a non-default value? This is from your 2009-01-08 commit.
This affects how filenames are expanded -- the old behaviour was to complete the filename preserving the relative filenames as relative after completion . The new behaviour is to replace a relative filename with the absolute filename. I do not want the new behaviour as I do not want the absolute filename in the repl history.
diff --git a/slime.el b/slime.el index b3fe4fe..70c3904 100644 --- a/slime.el +++ b/slime.el @@ -3665,15 +3665,24 @@ Perform completion more similar to Emacs' complete-symbol." (slime-display-or-scroll-completions completions partial))))))))
+(defcustom slime-when-complete-filename-expand nil + "Use comint-replace-by-expanded-filename instead of +comint-dynamic-complete-as-filename to complete file names" + :group 'slime-mode + :type 'boolean) + (defun slime-maybe-complete-as-filename () "If point is at a string starting with ", complete it as filename. -Return nil if point is not at filename." +Return nil iff if point is not at filename." (if (save-excursion (re-search-backward ""[^ \t\n]+\=" nil t)) (let ((comint-completion-addsuffix '("/" . """))) - (comint-replace-by-expanded-filename) + (if slime-when-complete-filename-expand + (comint-replace-by-expanded-filename) + (comint-dynamic-complete-as-filename)) t) nil))