>>>>>>> >>>>>>> You still have to C-c ' to get back to the full buffer, mind you, but >>>>>>> that's better, IMO, than changing the behaviour of such a fundamental >>>>>>> key binding as C-x C-s. >>>>> >>>>> >>>>> It appears that this bug is Emacs-version dependent: it functions as >>>>> you describe with 23.2, but the buffer gets buried (with an error >>>>> message "basic-save-buffer: Wrong type argument: stringp, nil") in >>>>> 24.0.92. Org mode is the current git HEAD. I tried to step through >>>>> basic-save-buffer in edebug, but I couldn't catch the error (I'm not >>>>> very experienced with edebug). Can someone test this on Emacs 24 and >>>>> confirm what I'm seeing? >>>> >>>> >>>> I am using 24.0.92 and I have no problems at all (just tried right >>>> now). >>>> >>>> One difference, however, could be the window configurations we >>>> use. Specifically, I have >>>> >>>> (setq org-src-window-setup (quote current-window)) >> >> >> Yes, this works. It's also a more sensible default. However, it >> doesn't change the fact that there's a bug, it just switches to a case >> where the bug isn't triggered :) > > > It is also not triggered by the "other-window" option, which behaves more > like > "reorganize-frame" than "current-window" (emacs 24.0.92)
Folks, I still think that the fact that buffer-file-name is not nil is a bug and should be fixed. If I'm wrong, can someone point out why this is so? I have seen many functions that test whether or not a buffer is visiting a file by checking buffer-file-name. For instance, if I wanted to enable autosave for org-src buffers, it would break since my make-auto-save-file-name checks whether a file is being visited. --Leo
