On 17 Jul 2024, Ihor Radchenko wrote:
The notion of "URL", and especially "URL at point" in Org mode
needs to
be special. Consider something like
[[https://orgmode.org][this is a very long and /convoluted/
description of this url; all the text here is clickable as a
link]].
Org mode will con
On 16 Jul 2024, Ihor Radchenko wrote:
Assume we have this line in an Org Mode buffer (note there are
three trailing spaces after the final "m" -- hopefully the MTAs
and MUAs will leave those spaces there):
https://example.com
Let's say the initial "h" is at position 22205, the position
In Org Mode buffers, `bounds-of-thing-at-point-provider-alist'
names a Org-Mode-specific URL provider:
((url . org--bounds-of-link-at-point))
That handler is defined in org.el:
(defun org--bounds-of-link-at-point ()
"`bounds-of-thing-at-point' provider function."
(let ((context (org-el
On 02 Nov 2023, Suhail Singh wrote:
Karl Fogel writes:
My original announcement post from a year ago [2] is a good
place to get a quick
overview of how oref.el works.
...
[2]
https://lists.gnu.org/archive/html/emacs-humanities/2022-10/msg9.html
From [2]:
Thus, in "
On 01 Nov 2023, Ihor Radchenko wrote:
Bastien writes:
Karl Fogel writes:
Hi, everyone. Small fix attached -- it just makes a warning
go
away.
Applied against the main branch, thanks!
Unfortunately, fixing this warning breaks org-table logic and
tests.
See previous discussion in
Ihor Radchenko writes:
Maske writes:
I propose links to arbitrary points in different files.
Furthermore, I think it would be a very nice new feature,
probably more opinions than mine should be heard.
See:
-
https://list.orgmode.org/orgmode/118435e8-0b20-46fd-af6a-88de8e19f...@app.fastmail
Hi, everyone. Small fix attached -- it just makes a warning go
away.
Best regards,
-Karl
>From a1a939191af1a195f260037510d407e7483ba05f Mon Sep 17 00:00:00 2001
From: Karl Fogel
Date: Mon, 30 Oct 2023 10:33:29 -0500
Subject: [PATCH] lisp/org-table.el: fix warning about `eq' usage
*
On 25 Feb 2023, Max Nikulin wrote:
On 25/02/2023 07:13, Karl Fogel wrote:
Okay, today I did some research and found that every "C-c
C-" binding is used in Org Mode except for "C-c
C-g". While
that one is technically reserved for the mode's use
No, there is an explic
`org-fold-hide-subtree'
is amazingly useful, we probably won't decide to bind it by
default in Org Mode. So I should just continue to bind it to a
custom key myself and continue to live a glorious life all alone
in my private keymap splendour.
Best regards,
-Karl
I wrote:
On 23 F
On 23 Feb 2023, Max Nikulin wrote:
On 23/02/2023 00:01, Karl Fogel wrote:
(when (not (keymap-lookup nil "C-"))
(keymap-local-set "C-" 'org-fold-hide-subtree))
So FWIW C- is not bound in Org Mode buffers for me, in
Emacs
30.x (i.e., recent development build
On 22 Feb 2023, Max Nikulin wrote:
On 22/02/2023 14:29, Karl Fogel wrote:
I put it on "C-" because that's normally unbound in Org
Mode,
and because so many of the Org Mode cycling commands involve
modified tab already.
Perhaps C- is not
Hey everyone, is there a reason we don't bind
`org-fold-hide-subtree' by default in Org Mode?
I bind it to C- and now find this to be one of the most
useful keybindings in Org Mode. I suspect my workflow is pretty
typical.
The use case is simple:
When reading material within a certain head
On 23 Apr 2022, Ihor Radchenko wrote:
Applied.
The patch is now on main as 67efaa739.
Thanks, Ihor!
Best regards,
-Karl
On 15 Apr 2022, Robert Pluim wrote:
On Fri, 15 Apr 2022 17:33:33 +0800, Ihor Radchenko
said:
Ihor> - Org mode no longer uses ChangeLog entries to
document changes.
Ihor> - Instead, special commit messages are used, as
described in the
Ihor> - `CONTRIBUTE' file in th
On 07 Apr 2022, Ihor Radchenko wrote:
Karl Fogel writes:
Unfortunately, the 'CONTRIBUTE' file at the top level of the
Org
Mode source tree gives incomplete guidance on commit messages
(it
just says to follow what Emacs does, so I did that). I didn't
realize that
https://o
ling list post).
A revised patch is attached. Now it's so simple that I think the
commit message doesn't need to point to the mailing list
discussion anyway. Review welcome.
Best regards,
-Karl
>From 2cef1fdbe2b2aa40a2bb081eab4b2e2808000670 Mon Sep 17 00:00:00 2001
From: Ka
On 04 Apr 2022, Ihor Radchenko wrote:
From bb229b4f8f78ae52962d7bc90c8b1d4993af8263 Mon Sep 17
00:00:00 2001
From: Karl Fogel
Date: Thu, 31 Mar 2022 19:02:38 -0500
Subject: [PATCH] Mark function obsolete & fix spelling of its
name
This commit message is a bit confusing. I would mention
On 19 Dec 2021, Ihor Radchenko wrote:
Karl Fogel writes:
Should we just remove `org-truely-invisible-p'? Or at least
correct the spelling of its name ("truely" should be "truly")?
I feel slightly reluctant about removal. If nothing, this
function can
be a remind
On 05 Dec 2021, Daniel Fleischer wrote:
You're right; I'll think of a way to present the git repo link,
i.e. the
code earlier and more prominently for those who just want to jump
and
examine the code.
+1, and thanks!
On 04 Dec 2021, Daniel Fleischer wrote:
The "Contribute" page at
https://orgmode.org/worg/org-contribute.html does not mention
git://git.sv.gnu.org/emacs/org-mode.git . Actually, now that I
look around, the "Maintenance" page at
https://orgmode.org/worg/org-maintenance.html doesn't mention
the
The "Contribute" page at
https://orgmode.org/worg/org-contribute.html does not mention
git://git.sv.gnu.org/emacs/org-mode.git . Actually, now that I
look around, the "Maintenance" page at
https://orgmode.org/worg/org-maintenance.html doesn't mention the
repository address either. It does me
The function `org-truely-invisible-p' is defined in
'lisp/org-macs.el', but it is not used anywhere anymore in Org
Mode, nor is it used anywhere in GNU Emacs (I checked on both
'emacs-28' branch and 'master' branch).
The last (and possibly only?) call to that function was removed
from `org-be
On 05 Dec 2019, Adam Porter wrote:
>Karl Fogel writes:
>> Unless you meant make a new interactive function to display a vertical
>> hierarchy and base it on the existing Org Mode functions you informed
>> me of the existence of? But I don't think there's a way to
On 03 Dec 2019, Adam Porter wrote:
>You might consider adjusting your fontification settings. The
>single-line outline path can be quite readable with the right faces (see
>attached example).
That's a useful hint generally, thank you. However, for most of the Org Mode
files I work with, the hea
On 03 Dec 2019, Adam Porter wrote:
>This seems to duplicate functionality from org-get-outline-path. As
>well, org-eldoc displays in the minibuffer the outline path for the
>heading at point.
Thank you, Adam -- I didn't know about those. I had searched for something
like that before implementin
On 03 Dec 2019, Adam Porter wrote:
>This seems to duplicate functionality from org-get-outline-path. As
>well, org-eldoc displays in the minibuffer the outline path for the
>heading at point.
By the way, when I run `M-x eldoc-mode' in a Org Mode buffer, I get this
message:
"There is no ElDoc
Hi. I've been using this for a while and find it very handy.
If people like this and want it in Org Mode, I'll do the rest of the work to
package it up as a patch, with ChangeLog entry, NEWS, etc, and post it here for
review before committing.
To try it out, just evaluate both functions and th
On 02 Dec 2019, Marco Wahl wrote:
>Karl Fogel writes:
>> Since `widen' itself is already available via C-x n w, it might be
>> better to save a special flag value like that for some special
>> behavior that we (or someone else) might think of in the future. I'm
&
On 02 Dec 2019, Marco Wahl wrote:
>What about numeric prefix arg 0 to reveal the whole buffer (aka
>'widen')? I think this would be a logical completion to the feature.
Since `widen' itself is already available via C-x n w, it might be better to
save a special flag value like that for some speci
On 01 Dec 2019, Marco Wahl wrote:
>I guess it's a good idea to write to Bastien explicitly.
I will do so.
>Thanks for asking about the version. AFAICT there is a feature freeze
>right now for version 9.3. This means you would commit to the 'next'
>branch which shall be the next master branch af
On 01 Dec 2019, Marco Wahl wrote:
>+1
>
>I think your enhancement is great and worth a news entry. What about
>pushing your code if nobody objects within one week?
Thanks, Marco; I'm glad you like it. I'll wait a week and then push (unless
there's discussion, in which case we'll see what the ou
>From bbeca3c5444646685085c134b10f4883812068a0 Mon Sep 17 00:00:00 2001
From: Karl Fogel
Date: Sat, 30 Nov 2019 01:33:15 -0600
Subject: [PATCH] Use prefix arg to narrow to a specific subtree
* lisp/org.el (org-narrow-to-subtree): Take a prefix arg and use
it to choose which subtree to narrow
On 18 Sep 2019, Marco Wahl wrote:
>Karl Fogel writes:
>> Hi. It appears that commit d07d8ff4163 in Org Mode causes
>> square-brace-enclosed links to display incorrectly.
>>
>> The buggy behavior is simple to describe: if you write a link like this
>>
>>
Hi. It appears that commit d07d8ff4163 in Org Mode causes
square-brace-enclosed links to display incorrectly.
The buggy behavior is simple to describe: if you write a link like this
[[URL][LINK-TEXT]]
then URL will be displayed instead of LINK-TEXT (and LINK-TEXT goes unused: URL
is still a
On 25 Apr 2019, Nicolas Goaziou wrote:
>Hello,
>
>Karl Fogel writes:
>
>> My proposal is for each raw prefix arg (each `C-u' prefix) to expand
>> the narrowing level outward/upward by one. So in the above situation:
>
>I suggest to use a numeric argument for th
Hi. This is a feature proposal -- if the consensus is that it would be
welcomed, I'm happy to code it. I just didn't want to take the time to write
it if there's no chance for it to be accepted upstream (since I don't want to
be maintaining my own personal branch of Org Mode).
It would be use
Matt Lundin writes:
>Here's a working implementation, using org-agenda-add-custom-command and
>the built-in mechanism for skipping non-deadline entries (you can get
>rid of ots-org-entry-skip-non-deadline). I also added some justification
>(the -22) to accommodate my rather long timestamp strings.
Sigh, sorry. I messed up one important background fact in my original post, by
mistakenly presenting these as the example Org Mode entries I was working with:
> * STARTED <2016-05-23> Org Mode scheduling test KIWI.
> DEADLINE: <2016-05-23>
>
> * TODO <2016-05-25> Org Mode scheduling te
I'm using the DEADLINE keyword with TODO entries, and I'd like the DEADLINE
date to be displayed as a datestamp next to each TODO item, when I list
deadlined todo items. In other words, I don't want to have to duplicate the
DEADLINE timestamp as a timestamp on the TODO line itself in my Org Mod
Nicolas Goaziou writes:
>Karl Fogel writes:
>
>> The attached patch improves the interactive success message from
>> `org-remove-file'. Comments / suggestions welcome, of course; I've
>> tried to follow http://orgmode.org/worg/org-contribute.html here.
The attached patch improves the interactive success message from
`org-remove-file'. Comments / suggestions welcome, of course; I've
tried to follow http://orgmode.org/worg/org-contribute.html here.
Best,
-Karl
>From 846d66a15c73a336c110f5238307242f9192e8c3 Mon Sep 17 00:00:00 20
David Maus writes:
>I pushed the fix with some small cleanup of the commit
>message. Somehow the patchtracker included the mailbody in the commit
>message.
Thank you!
FWIW, I used 'git format-patch' to generate the patch; not sure if that
had anything to do with the resulting patchtracker behavi
on Sep 17 00:00:00 2001
From: Karl Fogel
Date: Wed, 29 Feb 2012 13:42:35 -0600
Subject: [PATCH] Fix bug whereby a date-only line caused an error when
generating an agenda
* lisp/org-agenda.el (org-agenda-highlight-todo): Handle the case of a heading
that has a date but no todo keyword.
This is a
duce. This
makes sense, given the code. I have a tentative patch, which is
attached. What's the typical way to submit such things for review?
>From 8a4c65479b2f62cbffe32735c4afac5dd6a1ecae Mon Sep 17 00:00:00 2001
From: Karl Fogel
Date: Wed, 29 Feb 2012 13:06:06 -0600
Subject: [PATC
[please keep me CC'd, as I'm a digest subscriber on this list]
Suddenly "C-c a a" (`org-agenda-list') has started giving me this error:
args-out-of-range #(" ots:" 0 14 (org-category ...
Backtrace attached. This is with today's bleeding edge Org Mode code,
pulled from git://orgmode.
45 matches
Mail list logo
