From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: org-capture windows
Date: Mon, 15 Nov 2021 23:54:18 +0700 [thread overview]
Message-ID: <smu3bs$mdu$1@ciao.gmane.io> (raw)
In-Reply-To: <87fsrxeo6d.fsf@ucl.ac.uk>
On 15/11/2021 16:57, Eric S Fraga wrote:
>
> I agree completely. One of my bug-bears is org-capture which I often
> use during meetings to take notes or create TODO items. Typically, the
> org capture window covers my Teams buffer (I use exwm as my window
> manager...) which is rather annoying.
It seems, your workflow is inconsistent with original org-capture idea.
It was created at the time when screens were smaller and video meetings
were not usual activity. It is only my guess however. Some event
requiring capture interrupts current activity. It should be postponed
till capture completion, so all other windows are removed to not
distract you. As soon as capture finished you can resume the earlier
activity, so previous window layout and positions in buffers are restored.
It is not bad approach per se but it is designed for frames with one or
two buffers and incompatible with Emacs as window manager approach. I do
not mind that such behavior should not be mandatory.
I have another example when current behavior is confusing. Browser and
an Emacs frame are placed side by side. A group of related pages should
be captured. Initial buffer and position is arbitrary. During capture of
first page I jump to particular heading to cross-reference new note with
some older topic. It is necessary to add a bit more to the same topic
for a next web page but on capture completion buffer position is reset
to previous value despite I was going to continue capture process.
Another problem is capture started through org-protocol without explicit
template when template selection for previous capture was already
active. Such kind of multi-tasking should not be a problem but it is
since template key should be typed into minibuffer. I do not know what
can be a proper solution. Maybe it can be a special mode with custom
keymap for *Org Select* windows, so several such buffers may co-exist
with no conflict due to minibuffer.
> I did play with display-buffer-alist but it seemed to not be able to
> take control of some of org's windows. Everything else I do in Emacs is
> nicely managed through that alist.
A couple of months ago `display-buffer-alist' was overridden by
`org-no-popups'. Currently you can put "\\*Org
Select\\*\\|CAPTURE-.*\.org" buffers to e.g. side window. Unfortunately
other windows are still wiped till capture completion.
next prev parent reply other threads:[~2021-11-15 16:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 7:50 Bug: org-no-popups disregards display-buffer-fallback-action [9.4.6 (9.4.6-13-g4be129-elpaplus @ /home/jeeger/.emacs.d/elpa/org-plus-contrib-20210920/)] Jan Seeger via General discussions about Org-mode.
2021-11-10 10:20 ` Ihor Radchenko
2021-11-13 17:34 ` dal-blazej
2021-11-14 6:08 ` Ihor Radchenko
2021-11-14 12:13 ` Eric S Fraga
2021-11-14 12:40 ` Ihor Radchenko
2021-11-14 19:37 ` Eric S Fraga
2021-11-14 23:03 ` dal-blazej
2021-11-15 9:57 ` Eric S Fraga
2021-11-15 16:54 ` Max Nikulin [this message]
2021-11-15 18:29 ` org-capture windows Eric S Fraga
2021-11-15 19:40 ` Bug: org-no-popups disregards display-buffer-fallback-action [9.4.6 (9.4.6-13-g4be129-elpaplus @ /home/jeeger/.emacs.d/elpa/org-plus-contrib-20210920/)] Daniel Kraus
2024-04-12 17:59 ` Ihor Radchenko
2024-01-24 14:01 ` Ihor Radchenko
2024-01-25 3:10 ` Christopher M. Miles
2021-11-15 7:41 ` Jan Seeger via General discussions about Org-mode.
2021-11-13 13:15 ` Bug: org-no-popups disregards display-buffer-fallback-action 9.4.6 Max Nikulin
2021-11-15 7:42 ` Jan Seeger via General discussions about Org-mode.
2021-11-15 7:49 ` Jan Seeger via General discussions about Org-mode.
2021-11-17 14:49 ` Max Nikulin
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='smu3bs$mdu$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--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).