HI,
I have pushed some refinements to the feature branch, which should be now
ready for more general testing. I plan to attend the meetup next Wednesday
to make a short presentation and demonstration of what I have achieved.
If someone feels adventurous enough, feedback will always be welcome ;-)
Whoops, I forgot to include in my diff the small test I added. I've
attached the full diff here.
--
Best,
Kristoffer
diff --git a/lisp/org-capture.el b/lisp/org-capture.el
index 6d395406cf..f418e9fba9 100644
--- a/lisp/org-capture.el
+++ b/lisp/org-capture.el
@@ -205,24 +205,36 @@
(
On Thu, May 08 2025, Ihor Radchenko wrote:
> Kristoffer Balintona writes:
>
>> Currently, `org-find-olp' assumes that it is being passed a file path +
>> an outline path, but when the olp function returns nil, only a file path
>> is returned, so `org-find-olp' ends up returning nil when
>> `org-c
Hello,
With the ox-html option `:html-divs', the value is list of lists that
look like this:
'((preamble "div" "preamble")
(content "div" "content")
(postamble "div" "postamble"))
It is to long to be set as an OPTION. But a KEYWORD only accept string
if I understand correctly ?
Do
This is the first patch for the feature request: [FR] Allow emojis in
tags (was: emojis in tags?)
(https://list.orgmode.org/orgmode/87wn4pdarh.fsf@localhost/)
It's my first diff. I'm trying to get an understanding of code as well
as the process at the same time, and don't want to get things
compli
Christian Moe writes:
** TO_BE_SENT Invoice CL161
:PROPERTIES:
:Date: [2025-03-02 Sun]
:No: CL161
:Amount: 10
:END:
Ah OK, now I understand. I like this version better, it's a little bit cleaner
- as you point out.
Thanks again, happy that I learned something co
Ihor Radchenko writes:
> Maybe. Or not. Depends on preferences. Some users do not like keeping
> selection. If you want this feature, you can add support of
> `org-edit-keep-region' to `org-comment-dwim'.
That's a simpler and more elegant solution.
I cobbled this together and it works for me:
Raoul Comninos writes:
> However, to re-invoke `org-comment-dwim` one has to then reselect the
> text. Is this by design?
This is a standard behavior of Emacs's `comment-dwim'. Org mode follows
that default.
> It would be helpful if selection remains as in this sample code, which
> could be bet
jman writes:
> Christian Moe writes:
>> An alternative to defining a STATUS property at all would be to define the
>> statuses as local TODO keywords, which gives you a quick way to look up
>> all unsent or unpaid invoices via the agenda view without having to
>> write match syntax.
>
> I've tri
In Org one can use Org Source blocks to illustrate Org Syntax, as
follows:
#+begin_src org
* Test
** Test 2
#+end_src
If one invokes `org-comment-dwim` on the source code, the text is
commented out, as follows:
#+begin_src org
# * Test
# ** COMMENT Test 2
#+end_src
A second invocation adds th
PJ Proudhon writes:
In, your my/org-cycle-status function, if you just set t as the last argument of your
org-table-put call, e.g. "
(org-table-put (org-table-current-line) (org-table-current-column) next t)", the columns will
automatically be realigned
after a value is inserted
Thank you f
Christian Moe writes:
For this particular use case, though, have you considered a different
approach, using entries and column view? That is:
Wow, this is really a great solution. I didn't know I could play with properties to build a table
template!
It's just a little bit verbose, but the r
Hi Ihor,
> > Not really. I am proposing to tag each package and option, which is much
> > more easier and efficient to find and discover packages and options, and
> > even
> > individual choices, and maybe tag also other things like keybindings,
> > installation methods, etc.
>
> It is alre
jman writes:
> --8<---cut here---start->8---
> #+PROPERTY: INVOICE_STATUS "TO_BE_SENT SENT TO_BE_PAID PAID"
>
> | Invoice Date | Invoice # | Amount | Status |
> |--+---++|
> | [2025-03-02 Sun] | CL161 |
14 matches
Mail list logo
