From: Stephan Schmitt <drmabuse@cs.tu-berlin.de>
To: andrea <andrea.crotti.0@gmail.com>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Re: org-agenda-files variable
Date: Mon, 18 Jan 2010 12:45:57 +0100 [thread overview]
Message-ID: <4B5449F5.1090504@cs.tu-berlin.de> (raw)
In-Reply-To: <m18wbvwuzk.fsf@gmail.com>
Hi Andrea,
Also sprach andrea:
> Carsten Dominik <carsten.dominik@gmail.com> writes:
> ...
>> - Carsten
>
> I'm really sorry you're right, I should write a sort for this kind of
> questions, I always forget important details...
> Anyway
>
> emacs-version: "23.1.50.1"
> org-version: "6.33trans"
>
>
> The code for the hook is this
>
> --8<---------------cut here---------------start------------->8---
> (defun org-add-eventually()
> "Adding a file to org-agenda when saved"
> (interactive)
> (if (string= major-mode "org-mode")
> (org-agenda-file-to-front)))
>
> (add-hook 'before-save-hook 'org-add-eventually)
> --8<---------------cut here---------------end--------------->8---
>
> And finally I have different operating systems, linux on the other
> machine and osx 10.6 on this one.
>
> I'm not sure when the filename gets added in the "wrong format", but
> maybe it's my fault, I visit the absolute path.
> Anyway if I can force somehow to only use relative to home paths in
> emacs somehow it would be also fine.
I think the function 'abbreviate-file-name' can help you. Find more
information about file names in this info node:
(Elisp) Top > Files > File Names
>
> By the way when I open the agenda all the org-files are visited and I
> end up with a lot of buffers, is that normal?
>
If you mean all the org files listed in 'org-agenda-files':
That's normal and necessary for all the possible interaction in the agenda
buffer. But you can type 'x' in the agenda:
--8<---------------cut here---------------start------------->8---
x runs the command org-agenda-exit, which is an interactive compiled
Lisp function in `org-agenda.el'.
It is bound to x, <menu-bar> <Agenda> <Exit and Release Buffers>.
(org-agenda-exit)
Exit agenda by removing the window or the buffer.
Also kill all Org-mode buffers which have been loaded by `org-agenda'.
Org-mode buffers visited directly by the user will not be touched.
--8<---------------cut here---------------end--------------->8---
hth,
Stephan
> Thanks and sorry for the incomplete post
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-01-18 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 11:00 org-agenda-files variable andrea
2010-01-18 7:37 ` Carsten Dominik
2010-01-18 10:46 ` andrea
2010-01-18 11:45 ` Stephan Schmitt [this message]
2010-01-22 9:58 ` 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=4B5449F5.1090504@cs.tu-berlin.de \
--to=drmabuse@cs.tu-berlin.de \
--cc=andrea.crotti.0@gmail.com \
--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).