From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Marc-Oliver Ihm <marc@ihm.name>
Cc: Emacs Org mode <emacs-orgmode@gnu.org>
Subject: Re: [dev] New version of org-index.el --- A personal index for org and beyond
Date: Mon, 23 Sep 2013 08:58:29 +0200 [thread overview]
Message-ID: <m2li2ogh2i.fsf@polytechnique.org> (raw)
In-Reply-To: <877ge998ve.fsf@think.site>
marc@ihm.name writes:
>> Here are a few notes I'm taking as I'm playing with it.
>>
>> First, the table seems to be different from the one on worg. Here are
>> the columns I have:
>>
>> | | | | | | comment |
>> | ref | link | created | count;s | last-accessed | ;c |
>> | | <4> | | | | |
>>
>> I guess "comment" includes Type, description, and Keywords? Or can I
>> extend this table as I see fit?
>>
>
> Yes, just add any further columns you need. As long as the do not have a
> semicolon, they are ignored. You can also reorder columns according to
> your needs.
Ah, good to know, thanks.
>> Also, I noticed it's impossible to create a link to a file. If a file
>> does not have any org entry, then org-index link will fail with "Before
>> first headline at position 35591 in buffer ...". I can go around this by
>> creating an headline, but then I cannot use saveplace or something like
>> that to put me in the same place in the file (typically at the very end
>> of a long data table, to input more data).
>
> Currently org-index uses the function org-id-get-create to create the
> link. This function needs an org-mode nodes and whence org-index has the
> same limitation. However, it might be possible to create more general
> links here, that would be able to point to non-org files. I will check
> this for the next version.
This would be great. Maybe a support for usual org links could be a way
to do this?
>> Finally, what is the workflow to create a new reference? The way I do it
>> is "link" from the place to link, then call "+fill" in the table. Is
>> there a simpler way (that would do both in one stroke)?
>
> Definitely: With the initial prompt just choose "ref"; this will only
> create a new reference, but not a link. If you want both, then you
> currently have to use the workflow you described. However, having a
> feature, that allows both, would be easy to implement, if needed.
Could you give examples of when one would want a link without a ref, or
a ref without a link?
Thanks again,
Alan
next prev parent reply other threads:[~2013-09-23 6:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 20:17 [dev] New version of org-index.el --- A personal index for org and beyond Marc Ihm
2013-08-02 12:04 ` Suvayu Ali
2013-09-21 13:09 ` Alan Schmitt
2013-09-21 21:12 ` Marc-Oliver Ihm
2013-09-23 6:58 ` Alan Schmitt [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-08 21:00 [dev] New version of org-index.el --- a " Marc Ihm
2014-12-09 18:58 ` Alan Schmitt
2014-12-09 20:02 ` Alan Schmitt
2014-12-10 21:26 ` Marc Ihm
2014-12-11 7:37 ` Alan Schmitt
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=m2li2ogh2i.fsf@polytechnique.org \
--to=alan.schmitt@polytechnique.org \
--cc=emacs-orgmode@gnu.org \
--cc=marc@ihm.name \
/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).