emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ken Mankoff <mankoff@gmail.com>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Keep buffer visible w/ capture template
Date: Wed, 13 Jan 2016 15:04:35 -0500	[thread overview]
Message-ID: <m2oacpz1nw.fsf@client-104-39-128-31.eduroam.psu.edu> (raw)
In-Reply-To: <m2k2nd8htc.fsf@client-104-39-128-31.eduroam.psu.edu>


On 2016-01-13 at 13:17, Ken Mankoff <mankoff@gmail.com> wrote:
> On 2016-01-13 at 13:08, Kaushal Modi <kaushal.modi@gmail.com> wrote:
>>> I'd like to keep the active buffer visible while capturing.
>
>I think the issue is that the template requests a timestamp or a
>SCHEDULED field (or as you describe, you may add those manually). The
>email usually has the date/time information visible, but the calendar
>hides it, making it difficult to fill out the template. That is my
>issue. The current window flow is
>
> 1) View email 2) Invoke capture. See email + *Org Select* buffer 3)
> Select template. See *Capture* buffer and calendar buffer.
>
> I'd like to still see the email in step (3).

I've found two solutions to this.

1) (setq calendar-setup (quote calendar-only)) makes the calendar appear in a new frame. However, their are weird side effects and the mini-buffer used to enter the date/time is in another frame, and not the one where the capture was invoked.

OR

2)

(defun kdm/position-calendar-buffer (buffer alist)
  (display-buffer-at-bottom buffer alist))

(add-to-list 'display-buffer-alist (cons "\\*Calendar\\*" (cons #'kdm/position-calendar-buffer nil)))

Splits the window in 3, so I have 1) capture template 2) original text and 3) calendar.


  -k.

  reply	other threads:[~2016-01-13 20:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13 17:50 Keep buffer visible w/ capture template Ken Mankoff
2016-01-13 18:08 ` Kaushal Modi
2016-01-13 18:17   ` Ken Mankoff
2016-01-13 20:04     ` Ken Mankoff [this message]
2016-01-13 20:13       ` Kaushal Modi

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=m2oacpz1nw.fsf@client-104-39-128-31.eduroam.psu.edu \
    --to=mankoff@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kaushal.modi@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).