> I wouldn't dismiss plain text insertion too easily, either. It also
> includes external tools. What happens if an external tool automatically
> insert notes?
>
> The feature you are requesting could make sense if notes had a clear
> syntax. This would bring some interesting features, too (e.g.,
> Probably, it is easier if you just use seq-every-p instead of
> mapcar on (number-sequence max-pos min-pos -1). The result of
> seq-every-p will be inverse of the currently used expression.
Oh yeah, that's much nicer. I also made the predicate check
right-to-left, which just causes it to check
how do I create next, previous, and up navigation links when exporting
to html, like in the org mode manual:
https://orgmode.org/manual/HTML-specific-export-settings.html
Thanks.
--Chris Ryan
Did this look okay? I've had to rebase this once again due to some
conflicts in the ORG-NEWS.
Find the latest patch attached.
Best regards
Terje
On Tue, Jun 9, 2020 at 8:53 AM Terje Larsen wrote:
>
> Thank you Bastien,
>
> I didn't get what the updated patch with shorter lines meant, the only
>
After taking another look at my patch, I realized that I was not quite
converting dictionaries to proper alists.
Attached is a tweak to do this properly. The printing of dictionaries is
not quite as pretty, in particular it's not a table anymore:
#+begin_src python
return {"a": 1, "b": 2}
#+end
Hi Chuck,
"Berry, Charles" writes:
> This problem has been bugging people for years and previous attempts to solve
> it have always run up against creating more problems in the process of
> solving this one.
>
> If you do decide to dig into solving this, please be sure that remote
> sessions
Hi Kyle,
Thanks for the comments, I'm attaching an updated patch.
Kyle Meyer writes:
> ModuleNotFoundError wasn't added until Python 3.6, so I think it'd be
> better to use its parent class, ImportError.
I did not know this, thanks for the tip.
> Should handling of Series also be added?
Yes,
Nicolas Goaziou writes:
> Ihor Radchenko writes:
>
>> I feel that my understand of "note" in context of org is different from
>> yours. Is there a formal definition of "note" in org?
>
> As I stated in my first post a few hours ago:
>
>Notes are mostly free-form; there is no syntax describin
> Again, on a given document, you can only guess what is the "last note".
> This is not reliable enough to extend the syntax.
I feel that my understand of "note" in context of org is different from
yours. Is there a formal definition of "note" in org?
If no, there is indeed no reliable way to cap
Ihor Radchenko writes:
> I feel that my understand of "note" in context of org is different from
> yours. Is there a formal definition of "note" in org?
As I stated in my first post a few hours ago:
Notes are mostly free-form; there is no syntax describing them.
> However, we can formalise
Ihor Radchenko writes:
> I was mainly referring to org-add-note. The last note taken with
> org-add-note can be found quite reliably.
>
> I am using the following code saving the last note into :SUMMARY:
> property upon exiting the note buffer. Though it may be an overkill, not
> sure how easy wo
> Notes are free-form; there is no syntax describing them. Org cannot tell
> what is a "note". As a consequence, pointing to "the last note taken" is
> not reliable, syntax wise.
> Of course, under some assumptions (e.g., notes setup is fixed, you never
> write notes by hand, ...), you could guess
Hello,
Ihor Radchenko writes:
> Over the years of using Org I often have a need to add a short note
> about how to proceed with some task:
>
> * REVIEW check again, subscribe | sindresorhus/awesome: 😎 Awesome lists
> about all kinds of interesting topics :BOOKMARK:
> :PROPERTIES:
> :CREATED
13 matches
Mail list logo
