From: Nick Dokos <nicholas.dokos@hp.com>
To: Charles <millarc@verizon.net>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Access org-tag-alist from #+FILETAGS
Date: Tue, 13 Mar 2012 14:48:24 -0400 [thread overview]
Message-ID: <16933.1331664504@alphaville> (raw)
In-Reply-To: Message from Charles <millarc@verizon.net> of "Tue, 13 Mar 2012 14:01:12 EDT." <4F5F8B68.2080201@verizon.net>
Charles <millarc@verizon.net> wrote:
> I hope my occupation is not the reason for the "no response" to my
> question and comments two weeks ago.
>
Nope - lack of time, energy, inclination, knowledge are all possible.
> Charlie Millar
>
> On 2/28/2012 2:28 PM, Charles wrote:
> > I use a few tags and usually two or three will apply to all entries
> > in a particular file, e.g. :work:Client:OpenFile: or :Personal:Home:
> >
> > All my tags are in my .emacs using the org-tag-alist and I want to
> > use these consistently.
> >
> > Is there a way to access org-tag-alist from the in-buffer settings
> > #+FILETAGS or #+TAGS? C-c C-c, of course, refreshes the local
> > setting; C-c C-q gives an error(?) message "Before first headline at
> > position 1 in buffer . . ."
> >
> > At the moment my work around is: start the file's first line with
> > *<spc>#+FILETAGS, then C-c C-c, and after setting tags delete the
> > *<spc>.
> >
Have you tried a setup file?
tag.org:
--8<---------------cut here---------------start------------->8---
#+TAGS: one two three
--8<---------------cut here---------------end--------------->8---
and the "real" file is:
--8<---------------cut here---------------start------------->8---
#+SETUPFILE: tag.org
#+TAGS: foo bar baz
* two
* four
* three :bar:baz:
* one :foo:
* five :foo:baz:
#+BEGIN_SRC elisp
org-tag-alist
#+END_SRC
#+RESULTS:
| one |
| two |
| three |
| :newline |
| foo |
| bar |
| baz |
everything plus :newline (whatever that is).
--8<---------------cut here---------------end--------------->8---
Nick
> > My system is Windows 7 (home Premium), emacs 24.0.93.1, org 7.8.03
> >
> > If I have overlooked something obvious or easily researched, just
> > say so and I'll continue looking for the answer.
> >
> > BTW, I'm a freelance paralegal. Amongst other uses, a few months
> > ago I used org to draft a contract (from my notes kept in the org
> > file), then exported to LaTeX, then to pdf to print the final draft.
> >
> > Charlie Millar
> >
> >
> >
> > -----
> > No virus found in this message.
> > Checked by AVG - www.avg.com
> > Version: 10.0.1424 / Virus Database: 2113/4837 - Release Date: 02/28/12
> >
> >
>
>
next prev parent reply other threads:[~2012-03-13 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 19:28 Access org-tag-alist from #+FILETAGS Charles
2012-03-13 18:01 ` Charles
2012-03-13 18:48 ` Nick Dokos [this message]
2012-03-14 0:16 ` Charles
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=16933.1331664504@alphaville \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=millarc@verizon.net \
/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).