Re: saveplace prevent me from quitting if ~/.emacs-places is write-protected

[Karl Fogel <kfogel@floss.red-bean.com>]

Richard Stallman <rms@gnu.org> quotes someone else saying:
>     I have  saveplace enabled, and  I launched Emacs from  another account
>     than mine, so, no permission on ~/.emacs-place. 

Can you say exactly what you did, starting from login?

If you are logged in as user foo, then ~/.emacs-place should expand to
that file in foo's home directory, and you should have permissions on
~foo/.emacs-place (assuming the file was created in some reasonable
manner).  Whether the foo account is "your" account or someone else's
shouldn't make a difference to the permission system...

There may be some crucial bit of your recipe I'm misunderstanding.

(Of course, we could just reproduce this by setting .emacs-place
unwriteable manually, but it sounds like that's not what you did.)

>   C-x C-c to  quit, it asks me if I want  to save ~/.emacs-place anyway,
>   because it's write protected. I say no, and get this error message
>
>   « basic-save-buffer-2:  Attempt to  save to  a file  which  you aren't
>   allowed to write »

Richard, et al,

Assuming we can reproduce this, what is the right solution?  Is there
already a policy for how Emacs should behave when there's an error
saving a file at exit time, and that file is managed by Emacs (i.e.,
is not just a regular file visited for editing by the user)?

Thanks,
-Karl