emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nick Dokos <nicholas.dokos@hp.com>
To: Bastien <bzg@altern.org>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Possible bug in org-cycle with property drawer
Date: Thu, 26 Jan 2012 08:45:15 -0500	[thread overview]
Message-ID: <6670.1327585515@alphaville> (raw)
In-Reply-To: Message from Bastien <bzg@altern.org> of "Thu, 26 Jan 2012 09:48:25 +0100." <87ipjyg886.fsf@gnu.org>

Bastien <bzg@altern.org> wrote:

> Hi Nick,
> 
> Nick Dokos <nicholas.dokos@hp.com> writes:
> 
> > That's it: I had a 
> >
> > #+DRAWERS: JUNK GARBAGE TRASH
> >
> > line in the file (and I didn't report it in the original email: blush!
> > sorry about that).  Without it, the property drawer behaves normally.
> 
> Thinking again about your problem, I don't find it natural to
> have #+DRAWERS /replacing/ existing drawers specified in `org-drawers',
> instead of just adding new ones.
> 
> Do you agree?
> 
> The attached patch implements a new meaning for #+DRAWERS, as a way
> to declare "additional" drawers.
> 
> Let me know what you think, thanks!
> 

If I've learnt anything from watching the list over the years, it's that
somebody will have a need to replace existing drawers, so be prepared
for that :-)

That said, I can't think of any reason why adding to existing drawers,
instead of replacing them, would lead to problems. So I'm inclined to
agree with you. One question that might arise: are multiple
#+DRAWERS lines legal? and if so, what do they do?

I'll try to take the patch for a spin but I'm not sure when I'll be able
to do it.

Thanks,
Nick

next prev parent reply	other threads:[~2012-01-26 13:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 15:48 Possible bug in org-cycle with property drawer Nick Dokos
2012-01-25 16:03 ` Carsten Dominik
2012-01-25 16:09   ` Nick Dokos
2012-01-25 16:07 ` Bastien
2012-01-25 16:17   ` Nick Dokos
2012-01-26  8:48     ` Bastien
2012-01-26 13:45       ` Nick Dokos [this message]
2012-01-26 17:38       ` Achim Gratz
2012-01-28 23:50         ` Bastien
2012-01-29  8:05           ` Achim Gratz
2012-01-29  9:53             ` Bastien
2012-01-31 18:46               ` Achim Gratz
2012-01-31 20:41               ` Nicolas Goaziou
2012-01-25 16:10 ` Bastien
2012-01-26  8:54   ` Eric S Fraga

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=6670.1327585515@alphaville \
    --to=nicholas.dokos@hp.com \
    --cc=bzg@altern.org \
    --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

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