emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <c.dominik@uva.nl>
To: Levin Du <zslevin@gmail.com>
Cc: Org-mode Mode <emacs-orgmode@gnu.org>
Subject: Re: Org mode release 6.04
Date: Wed, 28 May 2008 06:36:28 +0200	[thread overview]
Message-ID: <C3324DCB-FCE6-455B-8D42-8CBEC2D58821@uva.nl> (raw)
In-Reply-To: <9649271a0805272101r193c5713of86e13d4726dd0f@mail.gmail.com>

Fixed thanks.

I cannot make an error message when you have misspelled a tag, because  
Org cannot know
if you have inserted that string on purpose.

But the loop is fixed now, and I am using now contents instead of  
content.

- Carsten

On May 28, 2008, at 6:01 AM, Levin Du wrote:

> I love the feature of "Editing source code example in the proper  
> mode". It's very handy and powerful.
>
> I found a bug with org-mtags.el. The table of content tag in muse is  
> <contents>, but in org is <content>.
>
> If I write a simple org file with the misspelled tag:
> ----8<----8<---
> <contents>
> * title1
> * title2
> ----8<----8<---
>
> then export using "C-c C-e h" will lead to a loop in  org-mtags-get- 
> tag-and-attributes.
>
> I wish I can use <contents> to be consistent with muse, and get a  
> warning from org if the tag is not supported.
>

  reply	other threads:[~2008-05-28  4:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-25  7:31 Org mode release 6.04 Carsten Dominik
2008-05-25 12:41 ` Austin Frank
2008-05-25 21:57   ` Shelagh Manton
2008-05-26  7:43     ` Shelagh Manton
2008-05-26 10:36       ` Daniel Clemente
2008-05-25 15:58 ` Leo
2008-05-27 22:00   ` Adam Spiers
2008-05-26 10:44 ` Daniel Clemente
2008-05-27  6:26   ` Carsten Dominik
2008-05-28  4:01 ` Levin Du
2008-05-28  4:36   ` Carsten Dominik [this message]
2008-05-28  6:34     ` Levin Du
2008-05-28  8:35       ` 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=C3324DCB-FCE6-455B-8D42-8CBEC2D58821@uva.nl \
    --to=c.dominik@uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=zslevin@gmail.com \
    /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).