From: Ken Mankoff <mankoff@gmail.com>
To: Daniel Clemente <n142857@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: IDs w/ human friendly component
Date: Sun, 2 Feb 2014 12:10:57 -0500 (EST) [thread overview]
Message-ID: <alpine.OSX.2.00.1402021210270.46505@tbetbambyn> (raw)
In-Reply-To: <877g9e80yo.wl%n142857@gmail.com>
Yes that is a fairly simple and obvious solution.
-k.
On Sun, 2 Feb 2014, Daniel Clemente wrote:
>
> Have you tried changing the strange ID to the ID that you want?
> (e.g. 7f3b531b-f1c9-41aa-854b-37235500495f → introduction). They
> should be unique. I use my manually written IDs for some important
> headers which I want to detect from outside org. In addition
> there's CUSTOM_ID, but I think that's the id="…" you want in HTML
> exports.
>
>
> El Sat, 1 Feb 2014 14:39:15 -0500 (EST) Ken Mankoff va escriure:
>>
>>
>> I've never cared that the ID field was not human friendly.
>>
>> But I've just learned about the Estimate Table where you can see your estimates
>> and actual clock time to complete tasks. If you want to see the estimates for
>> the current tree, you need to know the ID, which is not human friendly.
>>
>> It seems like with IDO mode, the first few characters or words of the title,
>> stripped of whitespace, could be pre- or ap- pended onto the ID, and then it
>> would be easy to select IDs. If this were how IDs were created, would this break
>> some other features? Do others see this as a good or bad thing? Or is there some
>> other way to tell the Estimate Table to work on the local tree.
>>
>> Cheers,
>>
>> -k.
>>
>
next prev parent reply other threads:[~2014-02-02 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 19:39 IDs w/ human friendly component Ken Mankoff
2014-02-02 6:47 ` Daniel Clemente
2014-02-02 17:10 ` Ken Mankoff [this message]
2014-02-02 17:47 ` John Kitchin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.OSX.2.00.1402021210270.46505@tbetbambyn \
--to=mankoff@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n142857@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.