From: Manish <mailtomanish.sharma@gmail.com>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: revert all agenda buffers
Date: Wed, 11 Feb 2009 01:30:22 +0530 [thread overview]
Message-ID: <e7cdbe30902101200n54d0b509x23000a5a44d837f@mail.gmail.com> (raw)
In-Reply-To: <715EF7E3-1393-40AA-83D2-7CC2E3D150BF@uva.nl>
On Wed, Feb 11, 2009 at 1:21 AM, Carsten Dominik wrote:
>
> On Feb 10, 2009, at 8:49 PM, Manish wrote:
>
>> On Wed, Feb 11, 2009 at 12:54 AM, Carsten Dominik wrote:
>>>
>>> On Feb 10, 2009, at 1:21 PM, David Bremner wrote:
>>>
>>>>
>>>> Hi Org-wizards;
>>>>
>>>> I am using git to to sync my org files between various hosts. The
>>>> problem is that when I update the files on disk (i.e. with a git pull)
>>>> then I have to manually revert each current org buffer (or, restart
>>>> emacs, like that is going to happen :-) ). It would be nice if there
>>>> was an analog of org-save-all-org-buffers that reverted them all for
>>>> me. Am I missing an existing solution?
>>>
>>> 6.22b has now `org-revert-all-org-buffers'. I consider this command
>>> slightly dangerous, so you have to confirm with "yes".
>>
>> Org mode is my default mode and many buffers not necessarily part of
>> agenda
>> are open almost all the time. Will this command revert *all* Org buffers
>> or
>> only the ones part of org-agenda-files?
>
> All of them.
I take it that it has to. So far I haven't yet run into David's situation so
I guess I am fine for the moment. But if I need to then I guess I will need
to remember to save (from agenda view, so that all Org buffers are saved)
before executing the git pull and revert command?
--
Manish
next prev parent reply other threads:[~2009-02-10 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 12:21 revert all agenda buffers David Bremner
2009-02-10 19:24 ` Carsten Dominik
2009-02-10 19:49 ` Manish
2009-02-10 19:51 ` Carsten Dominik
2009-02-10 20:00 ` Manish [this message]
2009-02-10 22:37 ` Carsten Dominik
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=e7cdbe30902101200n54d0b509x23000a5a44d837f@mail.gmail.com \
--to=mailtomanish.sharma@gmail.com \
--cc=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).