Re: Per-file attachment directories

[Viktor Rosenfeld <listuser36@googlemail.com>]

Hi,

putting the definition at the end of the file appears to work. At least
for two org files of mine which didn't work before. But it's still a
bug that definitions at the beginning are silently ignored for seemingly
unrelated parts, isn't it? I'll post a bug report to the mailing list.

Anyway, thanks for your help!

Cheers,
Viktor

Darlan Cavalcante Moreira wrote:

> 
> I tested here and it didn't work for the bad files as you said. However,
> putting the "Local Variables" at the end of the file worked. In fact, I
> have always written local variables like this at the end of the file,
> although I don't remember if this was because of a restriction of just
> because I'm used to.
> 
> A good tip is to put them inside a "* File Local Variables" heading so that
> they don't stay inside another heading. You can set the noexport tag to
> avoid exporting this heading.
> 
> Also, you can use the function add-file-local-variable to add a new local
> variable. Notice how this function put the local variables at the end of
> the file.
> 
> --
> Darlan Cavalcante Moreira
> 
> At Wed, 21 Sep 2011 20:29:25 +0200,
> Viktor Rosenfeld <listuser36@googlemail.com> wrote:
> > 
> > Hi,
> > 
> > this works for simple files but breaks silently for my org files. I've
> > narrowed it down to two seemingly unrelated parts and attached two
> > examples below.
> > 
> > - good1.org contains an entry with two tables. When I visit the file,
> >   Emacs asks me to evaluate the local variable. In bad1.org the first
> >   table contains another section with the entry "Rechnungsbeitrag". When
> >   I visit the file, Emacs does not ask me and I can verify that the
> >   local variable is not evaluated by attaching something to the task.
> > 
> > - In bad2.org the offending part is a long LOGBOOK drawer. Removing any
> >   two lines from the drawer makes the example work. In good2.org I've
> >   removed the first two lines.
> > 
> > If it weren't for those bugs, this would fit my needs exactly!
> > 
> > Cheers,
> > Viktor
> > 
> > Darlan Cavalcante Moreira wrote:
> > 
> > > 
> > > One way to do this is to use file variables to change the value of
> > > org-attach-directory. This works particularly well when you use just a few
> > > org files as in your case.
> > > 
> > > For instance, you could put
> > > --8<---------------cut here---------------start------------->8---
> > > # Local Variables:
> > > # org-attach-directory: "~/org/data/personal"
> > > # End:
> > > --8<---------------cut here---------------end--------------->8---
> > > in your personal.org file and 
> > > --8<---------------cut here---------------start------------->8---
> > > # Local Variables:
> > > # org-attach-directory: "~/org/data/work"
> > > # End:
> > > --8<---------------cut here---------------end--------------->8---
> > > in your work.org file.
> > > 
> > > --
> > > Darlan Cavalcante Moreira
> > > 
> > > At Wed, 21 Sep 2011 11:49:39 +0200,
> > > Viktor Rosenfeld <listuser36@googlemail.com> wrote:
> > > > 
> > > > Hi everybody,
> > > > 
> > > > so far I've only used one org file, but it's getting unwieldy and I've
> > > > decided to split it up.
> > > > 
> > > > I'd also like to split up my attachment directory to reduce clutter.
> > > > For example, if I have two org files "personal.org" and "work.org" I
> > > > would like attachments to go into automatically created directories
> > > > below "~/org/data/personal" and "~/org/data/work". If a file has no
> > > > custom attachment directory specified, attachments should be created
> > > > below a default path (same as now).
> > > > 
> > > > Is this possible?
> > > > 
> > > > Thanks,
> > > > Viktor
> > > > 
> > > 
>