emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: bugs in org-remember-backup-directory
Date: Thu, 30 Apr 2009 15:30:12 +0200	[thread overview]
Message-ID: <A6AA6CB4-7E5E-48CB-98CF-D59C5DB32638@gmail.com> (raw)
In-Reply-To: <20524da70904251508w523010efj6a07e25f1cbb03fa@mail.gmail.com>

On Apr 26, 2009, at 12:08 AM, Samuel Wales wrote:

> I noticed the following regarding
> org-remember-backup-directory:
>  1) auto-saving does not save contents
>     - solution: put (auto-save-mode 1) before or after (not
>       sure which) the call to org-set-local in the
>       following lines in org-remember:
>        # 	  (expand-file-name
>        # 	   (format-time-string "remember-%Y-%m-%d-%H-%M-%S")
>        # 	   org-remember-backup-directory))
>        #     (save-buffer)
>        #     (org-set-local 'auto-save-visited-file-name t))
>        #   (when (save-excursion


>  2) save-buffer is called before there are any contents
>     - this causes files without useful content to stick
>       around in the dir if the buffer is killed or
>       something.
>     - solution: don't save the buffer; let auto-saving do
>       that work.  will this work?

Usually, the template expansion will have filled in stuff like
links and initial contents, so I would prefer to keep the
save-buffer here and let the user deal with the extra files.

>  3) if you have auto-save-file-name-transforms set,
>     auto-saving is done according to that variable instead
>     of saving in place.

I am now turning that variable off, locally in the remember buffer.
Does that fix the problem?

- Carsten

>     - solution: is this an emacs bug?  i am not sure.  the
>       auto-saving should be done in place, saving in
>       org-remember-backup-directory and not saving in the
>       place where the transforms variable tells it to save.
>       perhaps each user can kludge transforms or perhaps
>       emacs needs fixing?  i have reached debugging ability
>       limit.
> Thanks.
> --  
> Myalgic encephalomyelitis denialism is causing death and severe  
> suffering
> worse than MS.  Greed is corrupting science into foul nonsense.   
> Anybody can
> get the disease at any time permanently.  Do science and justice  
> matter to
> you?  http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2009-05-03 16:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-25 22:08 bugs in org-remember-backup-directory Samuel Wales
2009-04-30 13:30 ` Carsten Dominik [this message]
2009-05-04 17:14   ` Samuel Wales
2009-05-04 17:57     ` Samuel Wales
2009-06-04 14:40       ` Carsten Dominik
2009-06-04 21:29         ` Samuel Wales
2009-06-05  3:59           ` Samuel Wales
2009-06-05  7:00             ` Carsten Dominik
2009-06-18 22:59               ` Samuel Wales
2009-06-26 22:27             ` Samuel Wales

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=A6AA6CB4-7E5E-48CB-98CF-D59C5DB32638@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=samologist@gmail.com \


* 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).