emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: James Harkins <jamshark70@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: MobileOrg and tags
Date: Fri, 20 Jul 2012 12:20:43 -0400	[thread overview]
Message-ID: <87a9yupfok.wl%jamshark70@dewdrop-world.net> (raw)
In-Reply-To: <87r4sb5d5o.wl%jamshark70@dewdrop-world.net>

At Mon, 16 Jul 2012 22:34:11 -0400,
James Harkins wrote:
> 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.

... snip

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

Following up on my question about transmitting tags over to MobileOrg -- the question being how to make sure MobileOrg knows about the existing tags, so that it's possible to edit tagged nodes without breaking the tags.

I found a reference to a function, org-global-tags-completion-table, that would collect all of the tags currently being used. So, as an experiment, I made a small change to org-mobile.el [1]. And, magically, in index.org, now I get:

#+TAGS: Bug FarShore Hadron Hard Lament lily Lilypond.........

And on my tablet, editing a node shows the correct tags (no more #+DRAWERS::) and, tapping on a tag brings up a full, correct list of tags. Great! IMO, what a typical user would expect.

Obviously this is a hack, and I am 1/ not sophisticated enough with lisp and 2/ not familiar enough with the orgmode codebase to implement a real solution. I guess it would be something like a customization variable to determine whether or not to concatenate the tag completion table onto org-tag-alist-for-agenda, and then a conditional in the spot that I changed.

If no objection, I'll add a feature request (if I don't find an existing one).


[1] Diff vs. release_7.8.11

diff --git a/lisp/org-mobile.el b/lisp/org-mobile.el
index 946e821..5644a05 100644
--- a/lisp/org-mobile.el
+++ b/lisp/org-mobile.el
@@ -430,7 +430,8 @@ agenda view showing the flagged items."
 			       ((listp e)
 				(if (stringp (car e)) (car e) nil))
 			       (t nil)))
-		       org-tag-alist-for-agenda))))
+;		       org-tag-alist-for-agenda))))
+		       (org-global-tags-completion-table)))))
 	(if org-mobile-use-encryption

James Harkins /// dewdrop world

"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

  reply	other threads:[~2012-07-20 16:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17  2:34 MobileOrg and tags James Harkins
2012-07-20 16:20 ` James Harkins [this message]
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:

  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=87a9yupfok.wl%jamshark70@dewdrop-world.net \
    --to=jamshark70@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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