emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Peter Westlake" <peter.westlake@pobox.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Org-mode version 6.30; Links in categories break layout
Date: Thu, 03 Sep 2009 14:29:27 +0100	[thread overview]
Message-ID: <1251984567.29809.1333027499@webmail.messagingengine.com> (raw)
In-Reply-To: <EEE7EE8C-F9F1-4BEA-A775-BDD885934AC2@gmail.com>


On Thu, 03 Sep 2009 14:12 +0200, "Carsten Dominik"
<carsten.dominik@gmail.com> wrote:
>
> On Sep 3, 2009, at 1:12 PM, Peter Westlake wrote:
>
> > On Thu, 03 Sep 2009 08:50 +0200, "Carsten Dominik"
> > <carsten.dominik@gmail.com> wrote:
> >> Hi Peter,
> >>
> >> links in categories are not supported......
> >
> > The thing is, they ever so nearly *are* supported: they are
> > fontified as links, and they work if you click on them or type C-c
> > o. The only thing that isn't quite right is this small cosmetic
> >    matter of the missing spaces.
> >
> > Having a link as a category is very useful, because categories have
> > meaning and the link can take you to it. Most of mine are links to
> > bug reports or feature requests, for instance.
>
> But TAB on the entry will get you there as well, right?

TAB in the agenda takes me to the entry, TAB in the entry opens it up,
and all of those things work properly. Click, ENTER, or C-c o in the
category column of the agenda will follow the link if the category text
contains one. All of that works properly too.

To clarify, my second paragraph there was just saying how useful links
are in categories. It isn't part of the bug report. That's just about
missing spaces.

You said that links aren't supported in categories, but for a feature
that isn't supported, they work very well! In what sense are they not
supported?

I use categories like this:

,----
| * PROJECT Implement BUG-1234, allow users to upload files
|   :PROPERTIES:
|   :CATEGORY: [[http://example.com/bugtracker/1234][BUG-1234]]
|   :ORDERED: t
|   :END:
| ** DONE Design uploader UI
| ** TODO Implement authentication
| ** TODO Write a form for directory navigation
| ...etc...
`----

Then the global TODO list (C-c a t) shows this as:

,----
| BUG-1234:TODO Implement authentication
`----

Where "BUG-1234" is a link that takes me to the bug tracker URL. Except
that the layout is a bit wrong:

,----
| plaintext:  TODO Item with a plain text category
| BUG-1234:TODO Implement authentication
| plaintext:  TODO Item with a plain text category
`----

There should be some spaces after the colon on the second line,
"BUG-1234:   TODO", so it lines up with the other entries.

Regards,

Peter.

> - Carsten
>
> >
> > Peter.
> >
> >> - Carsten
> >>
> >> On Sep 2, 2009, at 7:46 PM, Peter Westlake wrote:
> >>
> >>>
> >>> Remember to cover the basics, that is, what you expected to happen
> >>> and what in fact did happen.  You don't know hoe to make a good
> >>> report? See
> >>>
> >>>    http://orgmode.org/manual/Feedback.html#Feedback
> >>>
> >>> Your bug report will be posted to the Org-mode mailing list.
> >>> ------------------------------------------------------------------
> >>> ------
> >>>
> >>> Here's a plain-text view of my agenda that shows the problem:
> >>>
> >>> meta:       TODO Report invisible scheduled items
> >>> [[foo][test]]:TODO Get layout right when category is a link
> >>>
> >>> Because the link is displayed as "test" in the link face, it
> >>> is only four characters long, so it should have seven spaces
> >>> after it.
> >>>
> >>> (Aside: I wondered if this might be simple enough for me to fix it
> >>> myself. Turns out not :-)
> >>>
> >>> Peter.
> >>>
> >>> Emacs  : GNU Emacs 23.1.50.1 (i486-pc-linux-gnu, GTK+ Version
> >>> 2.12.12)of 2009-07-30 on elegiac, modified by Debian Package: Org-
> >>>         mode version 6.30
> >>>
> >>>
> >>> _______________________________________________
> >>> Emacs-orgmode mailing list Remember: use `Reply All' to send
> >>> replies to the list. Emacs-orgmode@gnu.org
> >>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
> >>
>

  reply	other threads:[~2009-09-03 13:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02 17:46 Org-mode version 6.30; Links in categories break layout Peter Westlake
2009-09-03  6:50 ` Carsten Dominik
2009-09-03 11:12   ` Peter Westlake
2009-09-03 12:12     ` Carsten Dominik
2009-09-03 13:29       ` Peter Westlake [this message]
2009-09-03 13:56         ` Carsten Dominik
2009-09-03 15:41           ` Sebastian Rose
2009-09-03 16:23           ` Peter Westlake
2009-09-04  7:19             ` Carsten Dominik
2009-09-04 10:44               ` Peter Westlake
2009-09-23 12:12                 ` Peter Westlake
2009-09-28 20:10                   ` Carsten Dominik
2009-09-29 13:24                     ` Peter Westlake

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=1251984567.29809.1333027499@webmail.messagingengine.com \
    --to=peter.westlake@pobox.com \
    --cc=carsten.dominik@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).