emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Charles Berry <ccberry@ucsd.edu>
To: emacs-orgmode@gnu.org
Subject: [bug] org-edit-src-code auto-save glitch
Date: Tue, 26 Mar 2013 19:18:57 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130326T194210-51@post.gmane.org> (raw)

I use Org-mode version 8.0-pre (release_8.0-pre-180-gf09471)

I am getting my src-buffers auto-saved even though

C-h v org-edit-src-auto-save-idle-delay RET gives me

| org-edit-src-auto-save-idle-delay is a variable defined in `org-src.el'.
| Its value is 0
| Documentation:
| Delay of idle time before auto-saving src code buffers.
| When a positive integer N, save after N seconds of idle time.
| When 0 (the default), don't auto-save.

When I open a src buffer and do C-h v buffer-auto-save-file-name RET I get 

| buffer-auto-save-file-name is a variable defined in `C source code'.
| Its value is "org-src-2801BU-2013-26-03.txt"
| Local in buffer *Org Src notes.org[ R ]*; global value is nil
| [deleted]
| Documentation:
| Name of file for auto-saving current buffer.
| If it is nil, that means don't auto-save this buffer.

Also, M-x auto-save-mode echoes "Auto-Save mode disabled" which tells me it was
enabled when I opened that buffer.

IIUC the problem is that this part of the function

| (setq buffer-file-name nil
|       buffer-auto-save-file-name
|       (concat (make-temp-name "org-src-")
| 	      (format-time-string "-%Y-%d-%m") ".txt"))

should consult org-edit-src-auto-save-idle-delay and when it is zero,
set buffer-auto-save-file-name to nil or take some other action to ensure that
auto-save-mode does get enabled.



             reply	other threads:[~2013-03-26 19:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 19:18 Charles Berry [this message]
2013-04-07 20:42 ` [bug] org-edit-src-code auto-save glitch Bastien
2013-04-09 20:51   ` Charles C. Berry
2013-04-09 21:04     ` Bastien
2013-04-10  2:08       ` Charles C. Berry
2013-04-16  8:42         ` Bastien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20130326T194210-51@post.gmane.org \
    --to=ccberry@ucsd.edu \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).