Christopher Miles writes:
> I think this is possible through read last note text in logbook, then display
> it
> in headline through text-property overlay.
>
> That's what I did in this package
> [[https://github.com/stardiviner/org-link-beautify]]
>
> Should not be that hard to implement it.
I think this is possible through read last note text in logbook, then display it
in headline through text-property overlay.
That's what I did in this package
[[https://github.com/stardiviner/org-link-beautify]]
Should not be that hard to implement it.
Ihor Radchenko writes:
> Over the years
Nicolas Goaziou writes:
> Hello,
>
> Ihor Radchenko writes:
>
>> I did not know this and I cannot find any reference about such behaviour
>> in manual (info:org#Markup for Rich Contents).
>
> You can find it looking for "line break" in the index. It points there:
> (info "(org) Paragraphs").
>
Hello,
Ihor Radchenko writes:
> I did not know this and I cannot find any reference about such behaviour
> in manual (info:org#Markup for Rich Contents).
You can find it looking for "line break" in the index. It points there:
(info "(org) Paragraphs").
>>> However, it is unused it unordered
>> You are right. I missed that \\ is also a newline for LaTeX export.
>
> It is a line break in any export back-end.
I did not know this and I cannot find any reference about such behaviour
in manual (info:org#Markup for Rich Contents).
>> However, it is unused it unordered lists. We might
Hello,
Ihor Radchenko writes:
> You are right. I missed that \\ is also a newline for LaTeX export.
It is a line break in any export back-end.
> Another possibility is re-purposing counter definition from ordered
> lists. Currently the "\\[@[0-9]+\\]" is used to force item number in
> ordered
Ihor Radchenko writes:
>> Everyone has their own workflows, but I think the way you are approaching
>> this problem is "wrong".
>
> I think I need to elaborate on the use-cases more then.
>
> I am well aware about the concept of NEXT actions, GTD, projects, and
> using categories to bring task
> Everyone has their own workflows, but I think the way you are approaching
> this problem is "wrong".
I think I need to elaborate on the use-cases more then.
I am well aware about the concept of NEXT actions, GTD, projects, and
using categories to bring task context in agenda. However, the
On Sat, Aug 29, 2020 at 6:42 AM Ihor Radchenko wrote:
>
> 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:
> However, writing an item
> with a line break at the end of its first line is not necessarily
> a note.
You are right. I missed that \\ is also a newline for LaTeX export.
Another possibility is re-purposing counter definition from ordered
lists. Currently the "\\[@[0-9]+\\]" is used to force
Hello,
Ihor Radchenko writes:
> I may miss something, but it does not look [for me] any more specific
> in comparison with headline format:
>
> - headline :: "^\*+ .+$"
> - first line of note :: "^[ \t]*-.+$"
I do see a big difference, tho. Starting a line with an asterisk
followed by a
>> - \\
>>
>
> This is not specific enough to be considered as syntax. The risk of
> false positive is too high. This is the reason why notes were never
> considered as syntactically meaningful so far.
I may miss something, but it does not look [for me] any more specific
in comparison with
Hello,
Ihor Radchenko writes:
> Instead of linking to the function, we can define the format used by
> `org-add-note' as a formal format for notes. Currently `org-add-note'
> uses the following format:
>
> - \\
>
This is not specific enough to be considered as syntax. The risk of
false
> Make it easier perhaps -- once the tool has been changed to the new
> syntax. But you might break current usage. And not everyone using such
> tools has coding skills to make those tools work again.
> Prof. Kitchin kindly gifted me with some code for a flash card learning
> system. That code
Am 31.08.20 um 04:26 schrieb Ihor Radchenko:
> I would not call defining syntax for notes "a syntax change". Rather
> addition to syntax. Since there was no formal definition of notes in the
> past, introducing formal syntax for notes should not break any existing
> tool. If anything, it should
> 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
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
> 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
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
> 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
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:
>
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: [2020-03-15 Sun 18:59]
:Source:
23 matches
Mail list logo
