From: James Harkins <jamshark70@gmail.com>
To: emacs-orgmode@gnu.org
Subject: MobileOrg and tags
Date: Mon, 16 Jul 2012 22:34:11 -0400 [thread overview]
Message-ID: <87r4sb5d5o.wl%jamshark70@dewdrop-world.net> (raw)
Been fiddling around with an issue that I noticed in MobileOrg for android... but I just noticed something strange that makes me think it's an issue in org-mode itself.
The issue reveals itself when using MobileOrg to edit a tagged node. Instead of the actual tags, MobileOrg shows "#+DRAWERS::" (as many times as there are tags for that item). Then this gets written back during org-mobile-pull.
What I noticed is this, in index.org:
#+TAGS:
#+DRAWERS: PROPERTIES CLOCK LOGBOOK
So, I guess, really two issues:
- MobileOrg parses the absence of anything after "TAGS" as undifferentiated white space, and assumes that #+DRAWERS: is the name of a valid tag.
- Orgmode doesn't populate the list of tags based on the tags that are actually used in the source files.
So my questions are:
- Where are the #+TAGS: supposed to come from? Only from org-tag-alist? If so, that's a bit of a bother. I don't know in advance what tags I will need. I'd rather not have to customize the variable every time I introduce a new tag.
- If my guess is right, is it a reasonable enhancement to have org-mobile-push append the tags found in the files onto what is already there in org-tag-alist?
Thanks,
James
--
James Harkins /// dewdrop world
jamshark70@dewdrop-world.net
http://www.dewdrop-world.net
"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal." -- Whitman
blog: http://www.dewdrop-world.net/words
audio clips: http://www.dewdrop-world.net/audio
more audio: http://soundcloud.com/dewdrop_world/tracks
next reply other threads:[~2012-07-17 2:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 2:34 James Harkins [this message]
2012-07-20 16:20 ` MobileOrg and tags James Harkins
2012-07-28 17:49 ` Bastien
2012-07-29 20:22 ` James Harkins
2012-07-30 10:20 ` Bastien
2012-08-03 12:31 ` Bastien
2012-08-03 15:41 ` James Harkins
2012-08-03 16:16 ` Bastien
2012-08-03 17:02 ` James Harkins
2012-08-03 17:09 ` Bastien
2012-08-03 18:06 ` Bastien
2012-08-03 18:50 ` James Harkins
2012-08-04 8:24 ` Bastien
2012-08-04 8:24 ` Bastien
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=87r4sb5d5o.wl%jamshark70@dewdrop-world.net \
--to=jamshark70@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).