* How about allowing indirect buffers for agenda restriction?
@ 2006-10-31 8:55 Alex Bochannek
2006-10-31 10:40 ` Carsten Dominik
0 siblings, 1 reply; 2+ messages in thread
From: Alex Bochannek @ 2006-10-31 8:55 UTC (permalink / raw)
To: emacs-orgmode
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)
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: How about allowing indirect buffers for agenda restriction?
2006-10-31 8:55 How about allowing indirect buffers for agenda restriction? Alex Bochannek
@ 2006-10-31 10:40 ` Carsten Dominik
0 siblings, 0 replies; 2+ messages in thread
From: Carsten Dominik @ 2006-10-31 10:40 UTC (permalink / raw)
To: Alex Bochannek; +Cc: emacs-orgmode
There is a better way of doing this, which I am implementing for 4.53.
Thanks.
- Carsten
On Oct 31, 2006, at 9:55, Alex Bochannek wrote:
> 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)
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>
--
Carsten Dominik
Sterrenkundig Instituut "Anton Pannekoek"
Universiteit van Amsterdam
Kruislaan 403
NL-1098SJ Amsterdam
phone: +31 20 525 7477
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-10-31 10:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-10-31 8:55 How about allowing indirect buffers for agenda restriction? Alex Bochannek
2006-10-31 10:40 ` Carsten Dominik
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).