org-heading-checkbox.el
Description: application/emacs-lisp
Last night I have been playing with a minor mode to enable a checkbox in
a heading, or rather to fake a checkbox. To be honest, it was a 10
minute job. Took me way moare time to figure out avialable key
combination to use (which I
Kévin Le Gouguec writes:
> 'headline-data sounds like a reasonable default too, although I think it
> still has some wrinkles[2].
>
> [2] Typing "* headline RET" starts an indented line; further RETs keep
> point indented until I type in something, after which RET finally
> snaps back to
Hi Juan,
this sounds very interesting to me, as I, too, mostly write in Org
and, sometimes write documents in multiple languages, usually with
different varieties of either Latin or Cyrillic.
I have some suggestions:
Apart from the export, one of my biggest gripes is
flyspell. Specifically, the
Hello Bastien,
On Monday, 3 May 2021 at 10:27, Bastien wrote:
> Hi Jeremie,
>
> I pushed a fix for this (though a little bit before I read your public
> message here) - let me know if it needs to be enhanced.
It's good enough for me. Many thanks again
Best regards,
--
Jeremie Juste
Hi Steven,
"Steven Bagley" writes:
> Yes, that works for the example I quoted. The source of the original
> "::" is org-mac-link, not my typing. Maybe that could insert a
> different character sequence to avoid any confusion.
can you propose a patch for this?
--
Bastien
Hi Aleksandar,
Thank you very much for your interesting comments. I think your idea of
applying org-babel to (multi) language support is tremendously
suggestive and, of course, more org-centric. I suppose it could be
applied also to languages within the paragraph by inline blocks... I
really
Hi Palak,
Palak Mathur writes:
> Any reason why we can’t move all ob-* files out into this new repo?
Yes, that's because Org Babel is a core documented feature of Org that
is not usable without these ob-*.el files.
We want to move out files that are of less importance and for which we
would
> On May 3, 2021, at 2:44 PM, Timothy wrote:
>
>
> Palak Mathur writes:
>
>> Any reason why we can’t move all ob-* files out into this new repo?
>
> I trust Bastien will correct me if I'm wrong, but my understanding is
> this isn't a new repo for "miscellaneous Org stuff" more
>
Hi Gustavo,
Gustavo Barros writes:
> since some time I've been facing a small annoyance in the agenda, as
> when I move point in my weekly agenda to a day which is not the first
> one display and then hit "f" (`org-agenda-later') the agenda buffer is
> scrolled up, hiding the top of the
Hi Greg,
I just checked and it induces a syntax error, which I did not know,
but turns out to be quite useful because it means that an untangled or
incorrectly tangled file will fail to run beyond that point. Best!
Tom
On Sun, May 2, 2021 at 9:11 PM Greg Minshall wrote:
>
> Tom, that is quite
Hi Bastien,
On Mon, 03 May 2021 at 17:31, Bastien wrote:
Hi Gustavo,
Gustavo Barros writes:
since some time I've been facing a small annoyance in the agenda, as
when I move point in my weekly agenda to a day which is not the first
one display and then hit "f" (`org-agenda-later') the
[Not directly related to the OP, but might be useful to know.]
On Mon, May 03 2021, Aleksandar Dimitrov wrote:
> this sounds very interesting to me, as I, too, mostly write in Org
> and, sometimes write documents in multiple languages, usually with
> different varieties of either Latin or
> On May 3, 2021, at 1:07 PM, Bastien wrote:
>
> Thanks for your reply.
>
> Timothy writes:
>
>> For the future, I'd think Julia actually warrants 1st class inclusion in
>> Org, and I've instigated an effort to write an ob-julia that works well.
>> More on this once it reaches a usable
Palak Mathur writes:
> Any reason why we can’t move all ob-* files out into this new repo?
I trust Bastien will correct me if I'm wrong, but my understanding is
this isn't a new repo for "miscellaneous Org stuff" more
"community-developed non-core Org stuff that isn't actively maintained".
Timothy writes:
> "community-developed non-core Org stuff that isn't actively maintained".
Yes, and: "In search for maintainers."
> The idea here being to move ob-* for rarely used languages to this repo
> to lessen the maintenance load.
Yes, that's it, thanks for stating it more directly
Le 03 May 2021, Bastien a écrit :
> I suggest a criterium for keeping ob*.el files in Org could be that
> the extension is known by Emacs _or_ that the supported language is
> well-established.
I happen to be an active user of ob-lilypond. Lilypond is certainly
peripheral to the world of
Hi Mingkai,
Mingkai Dong writes:
> * ox-html.el (org-html-headline, org-html-format-headline-default-function):
> delete the space after the section number span format and add it back in
> org-html-format-headline-default-function.
It looks good, thanks.
Can you show the exact difference by
Hi Bastien,
At the end of the mail is the output of `diff old.html new.html`, most
differences are caused by time and randomly generated ids.
The only exception is the Table-of-Content entries, which now has two
spaces before each section title. I find that the org-html--format-toc-headline
Hello,
"Bruce D'Arcus" writes:
> So if I want to add to that mini-init file the config so that the
> basic processor is correctly setup, what am I doing wrong here?
>
> (setq org-cite-activate-processor 'basic
> org-cite-follow-processor 'basic
> org-cite-export-processor 'basic)
Hi Ihor,
Ihor Radchenko writes:
> William Xu writes:
>
>> Now I try to test it extensively. Even with all your changes, I find
>> when I use org-agenda-todo to change the todo-state inside the agenda
>> buffer, the new state isn't always prettified.
>>
>> Do you see the same behaviour?
>
>
Bastien writes:
> Bastien writes:
>
>> The files previously stored in the contrib/ directory of Org's repo
>> now lives here: https://git.sr.ht/~bzg/org-contrib
>
> Let's announce this change on https://updates.orgmode.org.
For good! (Sorry for the noise.)
--
Bastien
Bastien writes:
> Kévin Le Gouguec writes:
>
>> Great! One last snag that I can see: when inserting properties or
>> clocking in, the :LOGBOOK:, :PROPERTIES: and :END: lines are indented,
>> but the /first/ :property: or CLOCK: line remains at column 0.
>
> Er. Can you try this (hopefully
Arthur,
Could you just use unicode checkbox symbols instead of TODO and DONE?
https://kdr2.com/tech/emacs/1405-orgmode-checkbox-unicode.html
That ought to be just a string, and need no patch.
On Mon, May 03, 2021 at 09:00:40AM +0200, Arthur Miller wrote:
>
> Last night I have been playing
Hello,
Eric S Fraga writes:
> I've had a short play with this. Looks nice!
Thank you!
> A few points:
>
> 1. if the BiBTeX entry has, for instance, \& to escape the & for use
>with LaTeX, org translates the \ to $\backslash$ and then the &
>causes a problem compiling the resulting
Hi Ihor,
Ihor Radchenko writes:
> This is another update about the status of the patch.
Thank you *very much* for this work and sorry for the slow reply.
I urge everyone to test this change, as I'd like to include it in
Org 9.5 if it's ready.
I will test this myself this week and report.
Hi Timothy,
Timothy writes:
> I haven't responded to this concern, because I haven't been able to
> conceive of a single situation where loading the normal-mode for the
> exported file could be desirable.
Well, I could not come up with it either.
Applied in master with commit ec6d1df9b,
Hi all,
Less code is less bug and less maintainance. So I'm considering
moving these files to the new (unmaintained) org-contrib repo at
https://git.sr.ht/~bzg/org-contrib:
- ob-abc.el --- Org Babel Functions for ABC
- ob-asymptote.el --- Babel Functions for Asymptote
- ob-coq.el --- Babel
Timothy writes:
> Bastien writes:
>> For now you can use statistics cookies in headline:
>> https://orgmode.org/manual/Checkboxes.html
>>
>> What would perhaps make sense would be to support [ ]/[X] on top of
>> the already supported [0%]/[100%] and [0/n]/[n/n].
>
> I've always used
> * TODO
Hello,
Bastien writes:
> Hi Steven,
>
> "Steven Bagley" writes:
>
>> In emacs -Q:
>>
>> 1. M-x org-mode
>> 2. insert the following line in the buffer (created by
>> org-mac-grab-link)
>>
>> - [[https://rgoswami.me/posts/org-note-workflow/][An Orgmode Note
>> Workflow :: Rohit Goswami
This is only tangentally related, but this feels like a relevant place
to mention this and I don't think it deserves its own thread.
I think it's also worth considering deleting ob-julia.el from
org-contrib. Not to put to fine a point on things, but it's currently
dysfunctional. Trying to
Nicolas Goaziou writes:
> This sounds reasonable.
I'm glad to hear that!
>> +(defun org-md-latex-environment [...]
> Nitpick: I would use `format', also the final newline character is
> useless, since it will be removed later during the export process.
Actually, since writing this patch I'm
Russell Adams writes:
> Arthur,
>
> Could you just use unicode checkbox symbols instead of TODO and DONE?
>
> https://kdr2.com/tech/emacs/1405-orgmode-checkbox-unicode.html
>
> That ought to be just a string, and need no patch.
No, I am sorry, that is completely off.
I have done this minor
Yes, that works for the example I quoted. The source of the original "::" is
org-mac-link, not my typing. Maybe that could insert a different character
sequence to avoid any confusion.
--Steve
On Mon, May 3, 2021, at 10:30, Nicolas Goaziou wrote:
> "Steven Bagley" writes:
>
> > I am aware of
Bastien writes:
> Hi Arthur,
>
> Arthur Miller writes:
>
>> Last night I have been playing with a minor mode to enable a checkbox in
>> a heading, or rather to fake a checkbox.
>
> Interesting, thanks.
>
> For now you can use statistics cookies in headline:
>
Hello,
Timothy writes:
> I anticipate that this change may be somewhat contentions because ox-md
> explicitly follows only the original Markdown spec from 2003, however
> I've thought this over and come to the conclusion that this change is
> still in keeping with that, and beneficial.
>
>
I am aware of the meaning of "::". Is this a design decision or an
implementation constraint? My intuition, obviously wrong here, is that link,
being a special kind of object, should have priority over what amounts to a
formatting command.
Thanks.
--Steve
On Mon, May 3, 2021, at 08:59,
Aleks, et al.,
> Apart from the export, one of my biggest gripes is
> flyspell. Specifically, the fact that you have to choose one language to
> spell check the entire document with. That is insufficient in my case.
in case it's relevant:
i also switch between languages. but, for me (maybe i'm
FYI, I implemented support for the org-cite syntax and the core styles
that I think will likely end up in citeproc-org, on the `org-cite`
branch, represented by this PR.
https://github.com/bdarcus/bibtex-actions/pull/113
So if you run the 'bibtex-actions-insert-citations' command and select
one
Hi Mingkai,
thanks a lot for the analysis and the diff, it helps a lot.
I pushed this change:
https://code.orgmode.org/bzg/org-mode/commit/dfdd5cd0
Keeping the headline numbering consistent with the TOC numbering seems
the right thing to do here.
Thanks!
--
Bastien
Thanks for your reply.
Timothy writes:
> For the future, I'd think Julia actually warrants 1st class inclusion in
> Org, and I've instigated an effort to write an ob-julia that works well.
> More on this once it reaches a usable state.
Great, I suggest we delete ob-julia.el from org-contrib
"Steven Bagley" writes:
> I am aware of the meaning of "::". Is this a design decision or an
> implementation constraint? My intuition, obviously wrong here, is that
> link, being a special kind of object, should have priority over what
> amounts to a formatting command.
- ... :: is also a
* ox-html.el (org-html-headline, org-html-format-headline-default-function):
delete the space after the section number span format and add it back in
org-html-format-headline-default-function.
The requirement is well described in the reddit post
Hi Bastien,
On Mon, 03 May 2021 at 19:26, Bastien wrote:
well, clearly my mind is dull right now - I pushed another better fix,
but please report any better solution if you have one.
Thank you.
No, not really, I just happened to spot an offending case of the
previous commit.
Bastien writes:
> Could it slow down agenda generation for some configurations?
Yes, it can. Specifically, fontifying tags can be costly. For
illustration, below if profiler report for a very large agenda buffer
(1468 entries):
19820 95% - org-agenda
...
4401 21% -
On Mon, May 3, 2021 at 12:42 PM Nicolas Goaziou wrote:
> Anyway, I suggest to let it nil, and select it at the document level
> instead, with
>
> #+cite_export: basic bibstyle citestyle
What is the significance of the last two items?
In a CSL implementation like citeproc-el, both are defined
Hi,
h...@protonmail.com writes:
> In https://orgmode.org/manual/Deadlines-and-Scheduling.html#
> Deadlines-and-Scheduling
>
> It says:
> "If you want to delay the display of this task in the agenda, use
> ‘SCHEDULED: <2004-12-25 Sat -2d>’: the task is still scheduled on the
> 25th but will
I can replicate this, it looks like a bug to me.
Looks to me that there's something wrong with the way it is handling
single quoted strings, since the output is only what is within the
double quoted strings. I will take a stab at fixing this.
On 5/3/21 6:22 PM, learn orchids wrote:
I am
Timothy writes:
> Eric S Fraga writes:
>
>> Is the verse package loaded automatically already? I did not see any
>> change in the patch to that aspect and when I export a simple test, the
>> package is not loaded.
>
> Wouldn't it be nice if there was something in-between loading the
>
Tom,
>I just checked and it induces a syntax error, which I did not know,
> but turns out to be quite useful because it means that an untangled or
> incorrectly tangled file will fail to run beyond that point. Best!
:) cheers.
Hi Gustavo,
well, clearly my mind is dull right now - I pushed another better fix,
but please report any better solution if you have one.
Thanks!
--
Bastien
Arthur Miller writes:
> ... Example can be seen in attached screenshot from
> my init file where I use org headings to form a list of packages to
> install, and checkboxes to indicate if a package configuration is used
> or not.
Depending on details of your workflow, you might also use
Bastien writes:
> Hi all,
>
> Less code is less bug and less maintainance. So I'm considering
> moving these files to the new (unmaintained) org-contrib repo at
> https://git.sr.ht/~bzg/org-contrib:
>
> - ob-abc.el --- Org Babel Functions for ABC
> - ob-asymptote.el --- Babel Functions for
Timothy writes:
> Actually, since writing this patch I'm not sure that $$-surrounding
> \begin{}...\end{} environments is also a good idea. I'm inclined to
> leave this out of the patch.
Sounds good.
> I do rather like the `rx' macro, however I'm not sure that
> (rx bol "\\(") is really an
I like Aleksandar's solution quite a bit because it also works inline
e.g. as src_org[:lang de]{Meine deutsch ist zher schlect!}. In
principle this means that you could leverage the org-babel and org-src
buffer system to get flyspell results in that language in line as well
(though I don't think
Hi Nicolas,
So, I've now fixed the handling of already-$-delaminated fragments, and
removed the $$ from around environments.
Sorry to complicate things, but, looking at what the HTML fallback
actually is, I've had some further thoughts. The HTML backend will
either leave the content as-is, run
I am using Org mode version 9.4.5 (9.4.5-73-g4c7696-elpaplus and I
have the following code snippet. Values in the 'sql' column of the
second row is truncated. Am I missing something?
#+begin_src sqlite :db /tmp/rip.db :colnames yes
drop table if exists testtable;
create table testtable(id
Tim Cross writes:
> +1 on this and the list of proposed languages.
Thanks for the feedback.
> Do any of these ob-* files have FSF copyright i.e. author assigned
> copyright to FSF. Just wondering, given the contrib package will live in
> non-gnu repo, if this is something we need to be
Tim Cross writes:
> Jean Louis writes:
>
>> If I set `org-adapt-indent' to 'headline-data, I get that same
>> behavior that after pressing ENTER on headline line, position becomes
>> indentend. So it does not make it right.
>>
>> My favour was the behaviour how it was before introduction of
>>
Hi Kevin,
thanks for checking.
Kévin Le Gouguec writes:
> A fews more moles to whack, maybe:
>
> - RET after an ":END:" starts an indented line,
> - "* headline RET text TAB" indents "text" (and subsequent RETs are then
> indented).
Fixed, thanks.
> Sorry for just dumping all these nits at
Hello,
The commit message instruction on the website
https://orgmode.org/contribute.html
The following instructions might help make commit message more precise
for newbies:
- Sentences should start with an uppercase letter (after the column) and end
with a full stop
- The sentence on the first
Hi Jeremie,
I pushed a fix for this (though a little bit before I read your public
message here) - let me know if it needs to be enhanced.
Thanks!
--
Bastien
Hi Arthur,
Arthur Miller writes:
> Last night I have been playing with a minor mode to enable a checkbox in
> a heading, or rather to fake a checkbox.
Interesting, thanks.
For now you can use statistics cookies in headline:
https://orgmode.org/manual/Checkboxes.html
What would perhaps make
Bastien writes:
> For now you can use statistics cookies in headline:
> https://orgmode.org/manual/Checkboxes.html
>
> What would perhaps make sense would be to support [ ]/[X] on top of
> the already supported [0%]/[100%] and [0/n]/[n/n].
I've always used
* TODO heading [/]
as a substitute
Hello,
I must apologize again for the delay. I'll be more responsive from now
on.
@Jack, I have applied the patch at the bottom of the mail. It is not
your latest patch but it works as well and is able to handle R errors.
> https://orgmode.org/list/87ft7t9wqk@gmail.com/
I have also added
Hi Kevin,
Kévin Le Gouguec writes:
> Great! One last snag that I can see: when inserting properties or
> clocking in, the :LOGBOOK:, :PROPERTIES: and :END: lines are indented,
> but the /first/ :property: or CLOCK: line remains at column 0.
Er. Can you try this (hopefully last) patch and
Bastien writes:
> By merging `org-speed-commands-default' and `org-speed-commands-user'
> into a single `org-speed-commands' option, we make this possible, but
> this change will ignore people's `org-speed-commands-user' config, so
> this is a breaking change.
I've done so with commit d48276b8
Bastien writes:
> The files previously stored in the contrib/ directory of Org's repo
> now lives here: https://git.sr.ht/~bzg/org-contrib
Let's announce this change on https://updates.orgmode.org.
--
Bastien
Hi Nick,
Nick Savage writes:
> I was trying to track down the source of a bug encountered when I was
> submitting my last patch about org-columns. I'm going to walk you
> through my thought process and summarize at the end. As part of my
> experimenting, I did the following:
>
> 1. emacs -Q
>
* Tim Cross [2021-05-03 01:39]:
> This is exactly what headline-data does. I suspect what your running
> into is electric-indent-mode and you need to turn it off to get the
> behaviour you want. So set org-adapt-indentation to hedline-data and
> turn off electric-indent-mode and you will get the
Hi Bastien,
On Mon, May 3, 2021 at 12:05 AM Bastien wrote:
>
> Tim Visher writes:
>
> > At the recommendation of Tim Cross I've prepared a patch to worg to
> > include the elisp that I recently sent to the list that I've been
> > using to create TODO items based on the currently selected macOS
Hi Tim,
Tim Visher writes:
> Here's a quick patch that fixes that up:
Applied, thanks. If you want to contribute more to Worg, please
send me the username you want in private and I'll create an account
for you on code.orgmode.org.
Thanks!
--
Bastien
Eric S Fraga writes:
> On Monday, 3 May 2021 at 15:00, Bastien wrote:
>> Applied with commit 479a3da22 in master, thanks.
>
> Thank you Bastien. However, as soon as I looked, I realised that my
> commit message missed out the "doc/" part of the file name for the
> manual. Can you fix that (if
Amin Bandali writes:
> Bastien writes:
>
>> Various discussions convinced me that `org-adapt-indentation' should
>> be nil by default.
>>
>> With `electric-indent-mode' being activated by default in Emacs, the
>> current behavior is that RET after a headline moves the point below
>> the
Bastien writes:
> Kévin Le Gouguec writes:
>
>> A fews more moles to whack, maybe:
>>
>> - RET after an ":END:" starts an indented line,
>> - "* headline RET text TAB" indents "text" (and subsequent RETs are then
>> indented).
>
> Fixed, thanks.
Great! One last snag that I can see: when
On Mon, May 3, 2021 at 8:58 AM Bastien wrote:
> Tim Visher writes:
>
> > Here's a quick patch that fixes that up:
>
> Applied, thanks. If you want to contribute more to Worg, please
> send me the username you want in private and I'll create an account
> for you on code.orgmode.org.
>
Thanks
On Monday, 3 May 2021 at 15:00, Bastien wrote:
> Applied with commit 479a3da22 in master, thanks.
Thank you Bastien. However, as soon as I looked, I realised that my
commit message missed out the "doc/" part of the file name for the
manual. Can you fix that (if necessary)?
Thanks again,
eric
On Thursday, 29 Apr 2021 at 10:51, John Kitchin wrote:
> I don't know if it is in the manual. It would be great to have it in
> https://orgmode.org/manual/Environment-of-a-Code-Block.html.
Attached is a patch for this. Thank you.
--
: Eric S Fraga via Emacs 28.0.50, Org
Hi Eric,
Eric S Fraga writes:
> On Thursday, 29 Apr 2021 at 10:51, John Kitchin wrote:
>> I don't know if it is in the manual. It would be great to have it in
>> https://orgmode.org/manual/Environment-of-a-Code-Block.html.
>
> Attached is a patch for this. Thank you.
Applied with commit
On Monday, 3 May 2021 at 15:43, Bastien wrote:
> Such small mistakes are okay, don't worry. It's better to leave them
> than to edit commit messages that have already been pushed to the
> public.
Okay, thank you. I'll try to be more careful next time!
--
: Eric S Fraga via Emacs 28.0.50, Org
Hello all,
I've had a short play with this. Looks nice!
A few points:
1. if the BiBTeX entry has, for instance, \& to escape the & for use
with LaTeX, org translates the \ to $\backslash$ and then the &
causes a problem compiling the resulting LaTeX.
2. the suppressed author case does
Hi Eric,
On Mon, May 3, 2021 at 9:47 AM Eric S Fraga wrote:
> 2. the suppressed author case does not seem to work.
He removed the suppress author variant on the individual cited items,
so I think the same effect he means to achieve with the "year" style.
Bruce
The files previously stored in the contrib/ directory of Org's repo
now lives here: https://git.sr.ht/~bzg/org-contrib
If you install Org from git to load packages from the contrib/ dir,
please update your configuration accordingly.
The new org-contrib.git repo is mostly for archival purpose.
Hello all,
I was trying to track down the source of a bug encountered when I was
submitting my last patch about org-columns. I'm going to walk you
through my thought process and summarize at the end. As part of my
experimenting, I did the following:
1. emacs -Q
2. open a new buffer at
Kyle Meyer writes:
...
> I think that'd be the cleanest way, yes. You could change
...
Thanks Kyle. Learned a bit more of Elisp.
Regards.. Pankaj
84 matches
Mail list logo
