Re: [Q] startup hook: How do I detect if the current buffer has been opened programmatically?

`find-file-hook` seems not to have false negatives, at least. Using `(window-live-p (get-buffer-window (current-buffer) 'visible))` has false negatives for me (i.e., it returns nil for some interactive buffers). Thanks, everyone. On Tue, Apr 9, 2024 at 11:06 PM Karthik Chikmagalur <

[Q] startup hook: How do I detect if the current buffer has been opened programmatically?

Org-mode occasionally opens files automatically, for instance, when inserting or opening ID links, or during certain searches. I need to determine if a buffer was opened programmatically or manually by the user within the startup hooks. This distinction is important because, e.g., I want to

Re: How do I link to a specific line in an org-babel block?

Thanks, that works great. Can these work with ID links, too? (`[[id:9bbb6468-2907-4e74-a4d1-2e391e33e0fe::...]]`) On Sun, Mar 17, 2024 at 4:47 PM Ihor Radchenko wrote: > Rudi C writes: > > > How do I link to a specific line in an org-babel block? > > a.org: > >

How do I link to a specific line in an org-babel block?

How do I link to a specific line in an org-babel block? I tried using [[file:.../my.org::search-term]] , but this only works for jumping to a heading, not an arbitrary line. (It does work for non-org files.) PS: Please use Reply to All.

Re: Forcing tab-width to be 8 makes using Python source blocks very difficult

Thanks, I don't have any problems now, so we can consider this closed. On Sat, Mar 16, 2024 at 2:32 PM Ihor Radchenko wrote: > Rudi C writes: > > > ... runs `evil-shift-right`, which > > indents the selected region by the `evil-shift-width` amount. > > `evil-shift-wid

Re: Principled Handling of Breaking Changes

e needed time for reading this anyway. Thanks. On Sat, Mar 16, 2024 at 1:48 PM Ihor Radchenko wrote: > Rudi C writes: > > > The recent upgrades to Org mode have been a source of great frustration > for > > me. Many of the configurations I had previously set up stopped workin

Re: Forcing tab-width to be 8 makes using Python source blocks very difficult

which again, I have no idea about: ``` 1. hi 2. hi 3. hi ``` So I don't see the effects of `tab-width` anywhere except in `evil-shift-width`, as far as I can see currently. On Sat, Mar 16, 2024 at 1:11 PM Ihor Radchenko wrote: > Rudi C writes: > > > Recently, a breaki

Principled Handling of Breaking Changes

The recent upgrades to Org mode have been a source of great frustration for me. Many of the configurations I had previously set up stopped working as intended, and it took me several days to properly identify the issues, debug them, and find suitable workarounds. I believe that Org mode would

Forcing tab-width to be 8 makes using Python source blocks very difficult

Recently, a breaking change has been introduced in Org mode that sets the default tab-width to 8 spaces ( https://list.orgmode.org/orgmode/8734y5d2gs.fsf@localhost/). This change has made using Python source blocks in Org mode challenging, as operations like `evil-org->` rely on `tab-width`, and

Re: [FR] Add a way to mark an item in a checklist as failed

I also use the partial tick for partial completion of tasks, so I cannot abuse it for marking failed tasks. :wry_smile: On Mon, Feb 26, 2024 at 11:25 PM Sławomir Grochowski < slawomir.grochow...@gmail.com> wrote: > Hi Rudy, > > Rudi C writes: > > > The use case

[FR] Add a way to mark an item in a checklist as failed

I think currently there is no way to mark an item in a checklist as failed? I would like to have such an ability ... Something like: - [F] task x or: - [0] task x The use case is that I use checklists to remember and track doing some important stuff at the start of the day; all the items are

Re: org-mode: example blocks are no longer syntax highlighted in emacs

Thanks! On Sun, Feb 25, 2024 at 1:30 PM Ihor Radchenko wrote: > Rudi C writes: > > > After upgrading to emacs 29.2 and org 9.7, my example blocks are no > longer > > syntax highlighted in emacs. They used to be syntax highlighted when I > > specified the

Re: org-mode: example blocks are no longer syntax highlighted in emacs

rg-remove-flyspell-overlays-in beg (match-end 0)) (add-text-properties beg (match-end 0) '(font-lock-fontified t face font-lock-comment-face))) (t ;; Just any other in-buffer setting, but not indented (org-remove-flyspell-overlays-in (match-beginning 0) (match-end 0)) (remove-text-properties (match

org-mode: example blocks are no longer syntax highlighted in emacs

After upgrading to emacs 29.2 and org 9.7, my example blocks are no longer syntax highlighted in emacs. They used to be syntax highlighted when I specified the block's language. Any ideas? I use Doom, so it might have been a third-party feature. I know org-mode officially suggests that example

Re: [BUG] babel runs bash instead of zsh when sessions are used

;..lar/notes/org ~/cellar/notes/org ~/cellar/notes/org master ~/cellar/notes/org master* ~/cellar/notes/org master* ❯ ``` On Sat, Aug 22, 2020 at 8:39 AM Kyle Meyer wrote: > Rudi C writes: > > > #+BEGIN_SRC zsh :session z1 > > echo $HOME $0 > > #+END_SRC > > > &g

[BUG] babel runs bash instead of zsh when sessions are used

#+BEGIN_SRC zsh :session z1 echo $HOME $0 #+END_SRC #+RESULTS: : /Users/evar /bin/bash As compared to: #+BEGIN_SRC zsh echo $HOME $0 #+END_SRC #+RESULTS: : /Users/evar zsh