emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Column view bugs
Date: Sat, 13 Oct 2007 14:50:15 +0100	[thread overview]
Message-ID: <874pgvktt4.fsf@bzg.ath.cx> (raw)
In-Reply-To: <6befca6f021e58dcdaab748fe501edec@science.uva.nl> (Carsten Dominik's message of "Sat, 13 Oct 2007 11:28:56 +0200")

Carsten Dominik <dominik@science.uva.nl> writes:

>> M-f M-b jump around in a confusing way in column view. Maybe just make
>> them like C-f and C-b?
>
> Good idea.
>
> Question back: TAB does still cycle visibility in column view,
> even though this looks like a table and one might expect
> that tab moves to the next field.  Any thoughts on this?

I'm not expecting TAB to jump from field to field here, but maybe others
would. A possible trade-off: do the normal cycling when at the beginning
of the line, jump among fields otherwise?

>> Is having the column view print practical? What about export?
>
> Yes, clearly important missing features.  What should we have?
>
> One interesting possibility would be a dynamic block that
> captures the column view as an Org-mode table.  

That would definitely be nice!

> The problem here is, where to create it.  Globally for the entire
> buffer with a #+COLUMNS line is probably the best?

Yes.

While we are at this, what would people think of a new {%} summary type
for column view?

  {%}  Progress status, [100%] if all children are in a DONE state.

-- 
Bastien

  reply	other threads:[~2007-10-13 12:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-13  6:44 Column view bugs Scott Jaderholm
2007-10-13  9:28 ` Carsten Dominik
2007-10-13 13:50   ` Bastien [this message]
2007-10-14 19:54     ` Vagn Johansen
2007-10-16  0:03       ` Bastien
2007-10-16 16:41         ` Vagn Johansen
2007-10-18 20:43           ` Vagn Johansen
2007-10-15 21:46   ` Daniel J. Sinder
2007-10-13 16:13 ` 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:
  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=874pgvktt4.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --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).