emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Robert Goldman <rpgoldman@sift.info>
To: Richard Riley <rileyrgdev@googlemail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: bug with org-agenda-export
Date: Thu, 30 Oct 2008 10:59:19 -0500	[thread overview]
Message-ID: <4909D9D7.4080108@sift.info> (raw)
In-Reply-To: <djd4hi9jn1.fsf@development.richardriley.net>

Richard Riley wrote:
> Hi Robert,
> 
> Why would you expect C-x C-w to remove/filter anything? Its simply
> write-file. Or do I misunderstand? Did you possibly redefine this
> command?

I guess I expected the agenda-writer to be WYSIWYG in its behavior, and
so apply the filters.

I can understand what's going on, but it seems counterintuitive to me:
the filter I apply interactively is implemented with overlays and not
reflected in the output, but the special command I write that to me
seems to do the same thing is not implemented with overlays, so works
with org-write-agenda.

I can see why this is done this way, and having looked at the
emacs-lisp, I can see why it might be a big pain to change it to make
org-write-agenda be wysiwyg, but I find it hard to think of the current
behavior as actually desirable.  Why would one *want* (as opposed to
tolerate) an agenda writer that shows one something different from what
one sees on the screen?

Put differently, why would I expect C-x C-w effectively to *strip* the
filters?  I have already filtered, so I don't think of it as removing or
filtering for C-x C-w to print what I see.  Again, I understand what is
really happening in the code, but to a user, it looks as if C-x C-w is
stripping a filter that's been applied.

best,
r

next prev parent reply	other threads:[~2008-10-30 15:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30 15:27 bug with org-agenda-export Robert Goldman
     [not found] ` <djd4hi9jn1.fsf@development.richardriley.net>
2008-10-30 15:59   ` Robert Goldman [this message]
2008-11-01 12:51 ` Carsten Dominik

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=4909D9D7.4080108@sift.info \
    --to=rpgoldman@sift.info \
    --cc=emacs-orgmode@gnu.org \
    --cc=rileyrgdev@googlemail.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

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).