emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alex Bochannek <alexb@juniper.net>
To: emacs-orgmode@gnu.org
Subject: How about allowing indirect buffers for agenda restriction?
Date: Tue, 31 Oct 2006 00:55:45 -0800	[thread overview]
Message-ID: <u7iyg50fi.fsf@juniper.net> (raw)

This is related to the narrowing patch I sent. Basically, I create a
indirect buffer clone, which I narrow to my Projects outline, but
still want to be able to call agenda commands that limit to the
file. Since indirect buffers have no file associated with them, I
thought the code below may be sufficient to do what I need it to. Not
well tested.

Alex.


$ diff -bu ../org-4.52/org.el org.el
--- ../org-4.52/org.el  2006-10-04 02:14:17.000000000 -0700
+++ org.el      2006-10-31 00:48:09.047839000 -0800
@@ -6883,6 +6884,8 @@
 first press `1' to indicate that the agenda should be temporarily (until the
 next use of \\[org-agenda]) restricted to the current file."
   (interactive "P")
+  (save-excursion
+    (set-buffer (or (buffer-base-buffer) (current-buffer)))
   (catch 'exit
     (let ((restrict-ok (and buffer-file-name (org-mode-p)))
          (buf (current-buffer))
@@ -6995,7 +6998,7 @@
                (org-let lprops '(org-occur match)))
               (t (error "Invalid custom agenda command type %s" type))))
          (org-run-agenda-series (cddr entry))))
-       (t (error "Invalid key"))))))
+       (t (error "Invalid key")))))))
 
 ;; FIXME: what is the meaning of WINDOW?????
 (defun org-run-agenda-series (series &optional window)

             reply	other threads:[~2006-10-31  8:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-31  8:55 Alex Bochannek [this message]
2006-10-31 10:40 ` How about allowing indirect buffers for agenda restriction? 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=u7iyg50fi.fsf@juniper.net \
    --to=alexb@juniper.net \
    --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).