Re: Org-Capture Window Behavior

2024-09-22 Thread Amol Vaidya
What a silly error on my part. Thank you for your time. Apologies about it being something so simple that I did not see. On Sun, Sep 22, 2024 at 12:45 PM Ihor Radchenko wrote: > Amol Vaidya writes: > > > I'm curious, then, why would what I've done in Test 2 nor corral it? > > > > (add-to-list

Re: Org-Capture Window Behavior

2024-09-22 Thread Ihor Radchenko
Amol Vaidya writes: > I'm curious, then, why would what I've done in Test 2 nor corral it? > > (add-to-list 'display-buffer-alist '("\\*CAPTURE*" > (display-buffer-same-window))) Oops. I missed that part. It does not work for very simple reason - "\\*CAPTURE*" regexp does not match buffer name

Re: Org-Capture Window Behavior

2024-09-22 Thread Amol Vaidya
I'm curious, then, why would what I've done in Test 2 nor corral it? (add-to-list 'display-buffer-alist '("\\*CAPTURE*" (display-buffer-same-window))) On Sun, Sep 22, 2024 at 12:00 PM Ihor Radchenko wrote: > Amol Vaidya writes: > > > Thank you for your clarification. Just a minor point: my con

Re: Org-Capture Window Behavior

2024-09-22 Thread Ihor Radchenko
Amol Vaidya writes: > Thank you for your clarification. Just a minor point: my concern is that > org-capture is not adhering to general display-buffer settings rather than > specifically display-buffer-alist. In my case display-buffer-alist is nil > when I run emacs -q, but according to section 2

Re: Org-Capture Window Behavior

2024-09-22 Thread Amol Vaidya
Hello, Again, I apologize for sending this email to you twice Ihor. I keep forgetting to hit reply-all. Anyway... Thank you for your clarification. Just a minor point: my concern is that org-capture is not adhering to general display-buffer settings rather than specifically display-buffer-alist.

Re: Org-Capture Window Behavior

2024-09-22 Thread Ihor Radchenko
Amol Vaidya writes: > (Apologies for replying to this twice Ihor, forgot to reply-all last time.) > > The linked video was from an emacs -q, so I have made no modifications to > display-buffer-alist, and my understanding is that emacs -q is equivalent > to an empty init file. If that's not correc

Re: Org-Capture Window Behavior

2024-09-17 Thread Amol Vaidya
(Apologies for replying to this twice Ihor, forgot to reply-all last time.) The linked video was from an emacs -q, so I have made no modifications to display-buffer-alist, and my understanding is that emacs -q is equivalent to an empty init file. If that's not correct, I'm not sure what kind of re

Re: Org-Capture Window Behavior

2024-09-17 Thread Ihor Radchenko
Amol Vaidya writes: > I have tested this with a clean installation of Emacs, where I > installed Org mode 9.7, but I am still encountering the same behavior. > > For reference, I’ve attached a screen recording that demonstrates the > issue. I’ve also verified that Org 9.7 is being used, as shown

Re: Org-Capture Window Behavior

2024-09-16 Thread Amol Vaidya
Thank you for your response. I have tested this with a clean installation of Emacs, where I installed Org mode 9.7, but I am still encountering the same behavior. For reference, I’ve attached a screen recording that demonstrates the issue. I’ve also verified that Org 9.7 is being used, as shown i

Re: Org-Capture Window Behavior

2024-09-16 Thread Ihor Radchenko
Amol Vaidya writes: > I use a widescreen monitor, and when I initiate an org-capture the frame > transforms mid-capture as follows: > > +---+---+---+---+ +---+---+ > | 1 | 2 | 3 | 4 | --> | 1 |capture| > +---+---+---+---+ +---+---+ > > I find this behavior disruptive,

Org-Capture Window Behavior

2024-09-16 Thread Amol Vaidya
Hello, I use a widescreen monitor, and when I initiate an org-capture the frame transforms mid-capture as follows: +---+---+---+---+ +---+---+ | 1 | 2 | 3 | 4 | --> | 1 |capture| +---+---+---+---+ +---+---+ I find this behavior disruptive, as I generally want to conde