Hi Kyle!
Thanks for the quick reaction.
> Am 05.05.2020 um 06:15 schrieb Kyle Meyer :
>
> As of 34b71a0ca (Add a dispatcher command for inserting dynamic
> blocks, 2018-12-23), the binding was removed and the command is
> available via org-dynamic-block-insert-dblock.
> ---
> doc/orgcard.tex |
This looks great (your elisp-fu is impressive) and definitely fulfills
making it look markdown-ish. Thanks! Will plug it in tonight and take it
for a pain.
I am assuming though, from the lack of answers back, that there appears to
be no way to have org-mode grok markdown code blocks (triple
Hi Daryl,
I am assuming though, from the lack of answers back, that there appears to
> be no way to have org-mode grok markdown code blocks (triple backticks)
> when it parses as a substitute for `#+BEGIN_SRC` ?
>
I am no expert in the Org internals, but a quick search shows the strings
> I am assuming though, from the lack of answers back, that there appears to
> be no way to have org-mode grok markdown code blocks (triple backticks)
> when it parses as a substitute for `#+BEGIN_SRC` ?
#+BEGIN_SRC is a part of org syntax, "```" is not.
You will need to modify the org-mode
> On May 5, 2020, at 1:46 AM, Ihor Radchenko wrote:
>
>> I am assuming though, from the lack of answers back, that there appears to
>> be no way to have org-mode grok markdown code blocks (triple backticks)
>> when it parses as a substitute for `#+BEGIN_SRC` ?
>
> #+BEGIN_SRC is a part of org
This looks impressive, and is *similar* to the effect I am going for, but
what I am looking at is intercepting the `org-insert-link` functionality
(or replacing it) with the ability to insert a link from the global
filter-and-select interface via ivy for `org-refile`. So, in other words,
global
> This looks impressive, and is *similar* to the effect I am going for, but
> what I am looking at is intercepting the `org-insert-link` functionality
> (or replacing it) with the ability to insert a link from the global
> filter-and-select interface via ivy for `org-refile`. So, in other words,
Note, the empty string or a nil template do not cause the error.
Hello,
"Mark E. Shoulson" writes:
> The "org-ellipsis" variable is specifically marked as (potentially) a
> safe local variable, so obviously someone intended for it possibly to be
> used that, and believed that it might be useful to someone as a local
> variable.
>
> However, there is no setup
Hello,
Ferdinand Pieper writes:
> Subject: [PATCH] org-protocol: Allow slashes after sub-protocol
Thank you.
Please add the function modified in the commit message. Also, if you
haven't signed FSF papers for copyright, you need to insert TINYCHANGE.
> This change lets org-protocol handle
Hello,
John Ciolfi writes:
> I just started using 9.2.6 and like the change for
> org-insert-structure-template to use key C-c C-, instead of the various
>
> Could you add this to the menu in org.el:
>
> ("Editing"
> ["Emphasis..." org-emphasize t]
> ["Add Source Example"
Hello,
Michaël Cadilhac writes:
> Is this the expected behavior?
>
> 1. Create an empty org file
> 2. Insert
> * Test
> * Test 2
> 3. With the cursor at Test, hit C-x n s to narrow the view to the Test
> subtree
> 4. Hit C-c C-s to schedule the line at any date.
>
> As a result, the SCHEDULED
Please see attached patch.
Regards.
On Mon, May 4, 2020 at 11:50 PM Nicolas Goaziou
wrote:
> Roland Coeurjoly writes:
>
> > I am confused about the last point:
> > Use a let-binding instead of setq.
> >
> > If I use:
> >
> > (let* compile (string= (cdr (assq :compile params)) "yes"))
>
> I
org-capture-place-plain-text throws an error for templates which
meet the following criteria:
- entry type is 'plain
- the template has a non-nil :unnarrowed option
- the template string is not empty and does not explicitly
include "%?"
Seems to be thrown in this section of
I have sent the form.
Thank you.
On Mon, May 4, 2020 at 11:52 PM Nicolas Goaziou
wrote:
> Roland Coeurjoly writes:
>
> > I have read the page about signing FSF papers, but I am unclear about how
> > to proceed.
> > Could you give some pointers?
>
> Certainly. See
>
>
Hello,
Roland Coeurjoly writes:
> Please see attached patch.
Great!
It seems that this is a patch that needs to be applied on top of the
previous one. Could you merge them into a single patch and send it
again?
Please let me know when the FSF registers you.
Regards,
--
Nicolas Goaziou
Sorry about that. This attached patch should be good.
On Tue, May 5, 2020 at 11:31 PM Nicolas Goaziou
wrote:
> Hello,
>
> Roland Coeurjoly writes:
>
> > Please see attached patch.
>
> Great!
>
> It seems that this is a patch that needs to be applied on top of the
> previous one. Could you
Pushed with fixes for the orgcard issues Axel noted and dropping the
notmuch message ID prefix that I unintentionally included in two commit
messages.
Range-diff:
1: 6f990dbc4 ! 1: 861ffb313 manual: Remove stale information about dynamic
block bindings
@@ Commit message
for
Axel Kielhorn writes:
>> diff --git a/doc/orgcard.tex b/doc/orgcard.tex
>> index fa233b620..121a86442 100644
>> --- a/doc/orgcard.tex
>> +++ b/doc/orgcard.tex
>> @@ -513,7 +513,7 @@ \section{Properties and Column View}
>> \key{special commands in property lines}{C-c C-c}
>> \key{next/previous
19 matches
Mail list logo
