-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nicolas Goaziou writes:
> Hello,
>
> Ihor Radchenko writes:
>
>>> Thanks Ihor, I indeed found related code in Org Mode source. I implemented a
>>> similar functionality in my patch.
>>
>> Oh. I somehow missed your first message...
>>
>> Now,
> The problem is that there doesn't seem to be any hook available for me
> to add a prop during the agenda creation process. Am I missing
> something? Or do I just need to modify `org-agenda-get-scheduled` directly?
The closest to what you want is org-agenda-prefix-format, where you can
add
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ihor Radchenko writes:
>> I try to record into under headline. For example, I use "org-contacts.el"
>> which
>> record people personalized info. I want to see all properties drawer under a
>> headline when I press [Tab] (org-cycle) to expand it.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nicolas Goaziou writes:
> Hello,
>
> stardiviner writes:
>
>> I try to record into under headline. For example, I use "org-contacts.el"
>> which
>> record people personalized info. I want to see all properties drawer under a
>> headline when I
Hi all,
First time on the mailing list. Been using org-mode for about half a year.
I'm trying to add a custom display to the agenda view, similar to
org-habit. I'm want to pull information from a task's `:LOGBOOK:` drawer
and display some stats next to the item in the agenda view.
I've
> Stefan Nobis hat am 13. April 2020 10:33 geschrieben:
>
>
> Nicolas Goaziou writes:
>
> > Alphanumeric suffix provides 62 combinations, which should hopefully
> > be enough for any citation back-end out there (I'm looking at you
> > biblatex). It's not terribly readable, tho, as you point
> Yes, this `integrate' value is not great, IMO. However, plain lists have
> much more in common with headlines than with drawers.
>
> I still think basic cycling should not include drawers whatsoever. This
> is even more true for properties drawers.
I tend to agree about the properties drawers.
I quickly looked through the code. It seems that you do not consider
attachments, which are normally stored in a folder named after the
entry's ID property. Deleting those ID is terrible idea.
Best,
Ihor
Marc-Oliver Ihm writes:
> Hi,
>
> as I use the excellent package org-id in a somewhat
Nicolas Goaziou writes:
> I still think basic cycling should not include drawers whatsoever. This
> is even more true for properties drawers.
>
> Note that you can already display drawers with `org-cycle', using three
> prefix arguments.
>
I agree. I use drawers precisely because they contain
i wonder if as a companion to such [perhaps hook-based user]
functionality, org-ellipsis could appear e.g. only if there is text
content.
Hi Bastien,
I've been keeping an eye out for you! :) Glad to hear you're well, and
I'm looking forward to your return.
Adam
Marc-Oliver Ihm writes:
> as I use the excellent package org-id in a somewhat non-standard way,
> I tend to produce IDs, that are not referenced from anywhere. Org-id
> handles this great and does not suffer in performance, but eventually
> I want to remove those unreferenced IDs. Therefore I
Hello,
Ihor Radchenko writes:
>> Thanks Ihor, I indeed found related code in Org Mode source. I implemented a
>> similar functionality in my patch.
>
> Oh. I somehow missed your first message...
>
> Now, actually adding something to the discussion.
>
> FYI, there is
> Thanks Ihor, I indeed found related code in Org Mode source. I implemented a
> similar functionality in my patch.
Oh. I somehow missed your first message...
Now, actually adding something to the discussion.
FYI, there is org-cycle-include-plain-lists variable. If it is set to
'integrate,
Hi,
as I use the excellent package org-id in a somewhat non-standard way, I tend to
produce IDs, that are not referenced from anywhere. Org-id handles this great
and does not suffer in performance, but eventually I want to remove those
unreferenced IDs.
Therefore I have written a small
Stig Brautaset writes:
> ...
> PS: Can we pretend this whole thread didn't happen? :-)
>
What thread?
--
Nick:-)
"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler
Jorge P. de Morais Neto writes:
> Em [2020-04-12 dom 22:35:09+], Kyle Meyer escreveu:
>
>> Thanks for sending this. My personal preference would be more focused
>> reports. (And of course patches would be even better.)
>
> Regarding patches, I feel I am too inexperienced at this moment to
Hello Nicolas,
On 2020-04-13 11:19, Nicolas Goaziou writes:
> This is a feature. With a few exception, keyword value is not parsed,
> i.e., Org does not need to understand what happens in there.
Thank you for the explanation.
>> Alternatively, should I suggest org-ref uses an approach similar
On Mon, Apr 13, 2020 at 8:05 AM Gustav Wikström wrote:
> I'm curious. So take this for what it is; I.e. curiosity. What /exactly/ is
> meant with a citation here? Is it a new general concept in Org mode, or is it
> something more narrow, as an extension for some specific third party
>
Hi,
I'm curious. So take this for what it is; I.e. curiosity. What /exactly/ is
meant with a citation here? Is it a new general concept in Org mode, or is it
something more narrow, as an extension for some specific third party software?
Would I be able to use it without that third party
Em [2020-04-12 dom 22:35:09+], Kyle Meyer escreveu:
> Thanks for sending this. My personal preference would be more focused
> reports. (And of course patches would be even better.)
Regarding patches, I feel I am too inexperienced at this moment to
efficiently write good patches. It is
Joost Kremers writes:
> I don't think it's necessary to use a dash (or any other character)
> in longer cite commands, though. =citeintext= isn't that much more
> difficult to read than =cite-intext=. (Biblatex does just fine
> without dashes, and there's always camelCase if you're so inclined.)
Important work! Stay safe.
Christian
Bastien writes:
> Dear all,
>
> my day job is to work for the open data public agency in France.
>
> I have been drown under a massive workload in the last four weeks,
> due to the COVID-19 crisis.
>
> I am slowly freeing more time and I'll be back at
Sorry, my last message was unreadable. (and possibly sent twice, once from a
wrong account... don't know if this will come through)
> Stefan Nobis hat am 13. April 2020 10:33 geschrieben:
>
>
> Nicolas Goaziou writes:
>
> > Alphanumeric suffix provides 62 combinations, which should
> > Stefan Nobis hat am 13. April 2020 10:33 geschrieben:
> >
> >
> > Nicolas Goaziou writes:
> >
> > > Alphanumeric suffix provides 62 combinations, which should hopefully
> > > be enough for any citation back-end out there (I'm looking at you
> > > biblatex). It's not terribly readable,
On Mon, Apr 13 2020, Nicolas Goaziou wrote:
denis.maier.li...@mailbox.org writes:
What about allowing something more verbose? Perhaps
"cite-intext:" or "cite:intext:"?
[...]
The simple syntax is great for most cases, but if you want to
support
some of those not so common biblatex commands,
> Nicolas Goaziou hat am 13. April 2020 00:19
> geschrieben:
>
>
> Hello,
>
> denis.maier.li...@mailbox.org writes:
>
> > Just one question concerning typed citations. citeX is good and
> > concise, but why limit this to only one character?
>
> Because… it is good and concise? ;)
>
> >
On Mon, Apr 13, 2020 at 4:34 AM Stefan Nobis wrote:
> [Placing bibliography with "#+bibliography: here"]
> > It is smart, but I'm not sure I like using the same keyword for two
> > different things. OTOH, I don't have a better idea.
>
> I personally also dislike one keyword for completely
On Sun, Apr 12, 2020 at 6:19 PM Nicolas Goaziou wrote:
> denis.maier.li...@mailbox.org writes:
>
> > Just one question concerning typed citations. citeX is good and
> > concise, but why limit this to only one character?
>
> Because… it is good and concise? ;)
>
> > What about allowing something
Nicolas Goaziou writes:
> Stig Brautaset writes:
>
>> Doh! Thanks for that. I tried working around this behaviour ~:lines
>> "1-"~, to skip the included file's #+title line, but that didn't seem to
>> work either. E.g. like this:
>>
>> : #+include: first-post.org :lines "1-"
>
> Doesn't "1-"
Hello,
Alan Schmitt writes:
> If you consider the following line in an org file
>
> #+begin_src org
> #+FOO: http://alan.petitepomme.net/
> #+end_src
>
>
> then calling ~org-element-context~ returns
>
> #+begin_src emacs-lisp
> (keyword
> (:key "FOO"
> :value "http://alan.petitepomme.net/;
>
> I try to record into under headline. For example, I use "org-contacts.el"
> which
> record people personalized info. I want to see all properties drawer under a
> headline when I press [Tab] (org-cycle) to expand it. It's more intuitive.
I recall seeing something similar in stackoverflow.
Here
Nicolas Goaziou writes:
> Alphanumeric suffix provides 62 combinations, which should hopefully
> be enough for any citation back-end out there (I'm looking at you
> biblatex). It's not terribly readable, tho, as you point out.
I second that. Some of the many BibLaTeX commands are due to
Hello,
If you consider the following line in an org file
#+begin_src org
#+FOO: http://alan.petitepomme.net/
#+end_src
then calling ~org-element-context~ returns
#+begin_src emacs-lisp
(keyword
(:key "FOO"
:value "http://alan.petitepomme.net/;
:begin 1
:end 38
:post-blank 1
Hello,
stardiviner writes:
> I try to record into under headline. For example, I use "org-contacts.el"
> which
> record people personalized info. I want to see all properties drawer under a
> headline when I press [Tab] (org-cycle) to expand it. It's more intuitive.
>
> I agree your opinion. I
35 matches
Mail list logo
