emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Niels Giesen <niels.giesen@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: scope of properties in a narrowed buffer, links in certain environments etc.
Date: Wed, 17 Oct 2007 11:12:50 +0200	[thread overview]
Message-ID: <119436a171cb4a98fd350441ed8ff8a1@science.uva.nl> (raw)
In-Reply-To: <4714B4F8.7050506@gmail.com>


On Oct 16, 2007, at 14:56, Niels Giesen wrote:

>
> Column view on a narrowed subtree does take into account the file-wide 
> #+COLUMNS directive,  but *not* the :COLUMNS: property of a parent 
> tree outside of the narrowing.
> Actually, this issue seems to be larger: `org-set-property' does scan 
> the whole file for properties, but prop_ALL from a parent tree outside 
> of the narrowing does not have any effect on the values shown.

Fixed, thanks.

>
> In column view links are not propertised as links, so the full text 
> shows.

This cannot be changed, because columns are a display property already, 
and links
also need a display property.

>  Also, C-c C-o does not work here to follow a link in a line (or 
> rather: column).

I guess this could be made to work.

>
> Whilst on the subject of links, in the agenda buffer, for some reason 
> C-c C-o has trouble when a link is not on the end of a line. The 
> following in org-agenda-open-link patch fixes this:
> (however, it will still just follow the /first/ link on the line)

Fixed, thanks.

- Carsten

      reply	other threads:[~2007-10-17  9:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4714a56f.1901360a.7cc7.ffffddb6SMTPIN_ADDED@mx.google.com>
2007-10-16 12:56 ` scope of properties in a narrowed buffer, links in certain environments etc Niels Giesen
2007-10-17  9:12   ` Carsten Dominik [this message]

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=119436a171cb4a98fd350441ed8ff8a1@science.uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=niels.giesen@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 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).