Dear all,
this is great added functionality that I have missed a lot myself. Thanks
for this! Also, I like the key binding.
One improvement I can think of it to read the block type with completion
(but still allow any word to be used).
Carsten
On Wed, Oct 18, 2017 at 12:03 AM, Eric Abrahamsen
I submitted a bug report to emacs core, and Eli says:
> Having read all of the references and discussions you've provided, I
> see no evidence that this is an Emacs issue, as opposed to an Org
> issue. I think the Org developers should take a look at this first,
> and only if they provide clear e
Adrian Bradd writes:
> Instrumenting 'org-capture' with edebug might be of some assistance. This
> should at least allow you to step through org-capture and see where emacs is
> hanging.
>
> HTH
>
> On 13 October 2017 at 12:51, Aaron Bieber wrote:
>
> Hola,
>
> I am trying to trac
Sorry for the repeat. Forgot to copy the list the first time.
Instrumenting 'org-capture' with edebug might be of some assistance. This
should at least allow you to step through org-capture and see where emacs
is hanging.
HTH
On 13 October 2017 at 12:51, Aaron Bieber wrote:
> Hola,
>
>
Eric Abrahamsen writes:
> Nicolas Goaziou writes:
>
>> Eric Abrahamsen writes:
>>
>>> I'm still not quite seeing this. This chunk should take care of it:
>>>
>>> (goto-char e)
>>> (if (bolp)
>>> (progn
>>> (skip-chars-backward " \n\t")
>>> (forward-line))
>>> (end-
Nicolas Goaziou writes:
> Eric Abrahamsen writes:
>
>> I'm still not quite seeing this. This chunk should take care of it:
>>
>> (goto-char e)
>> (if (bolp)
>> (progn
>>(skip-chars-backward " \n\t")
>>(forward-line))
>> (end-of-line)
>> (insert "\n"))
>>
> On Oct 17, 2017, at 10:22 AM, Kaushal Modi wrote:
>
> On Tue, Oct 17, 2017 at 12:31 PM Berry, Charles wrote:
> The copy buffer that org-export-as sets up will contain this src block
> *after* the babel process runs.
>
> As you can see the headers are stripped off of it.
Actually, I was wr
Eric Abrahamsen writes:
> I'm still not quite seeing this. This chunk should take care of it:
>
> (goto-char e)
> (if (bolp)
> (progn
> (skip-chars-backward " \n\t")
> (forward-line))
> (end-of-line)
> (insert "\n"))
>
> If "e" is EOB, we do `end-of-line'
Hello,
Allen Li writes:
> That sounds like a good idea, but the current behavior appears to be
> how it was added in 2009 by Carsten. I'm only documenting the current
> behavior, not improving it.
True. Applied. Thank you.
Regards,
--
Nicolas Goaziou
On Tue, Oct 17, 2017 at 12:47 AM, Nicolas Goaziou
wrote:
> Hello,
>
> Allen Li writes:
>
>> This makes org-insert-todo-heading-respect-content use the previous
>> heading of the same level instead of the previous heading regardless
>> of level.
>>
>> Given:
>>
>>* TODO some task
>>** WAIT
On Tue, Oct 17, 2017 at 1:01 AM, Nicolas Goaziou wrote:
>
> This is not directly related to your patch, but isn't something wrong
> here?
>
> I.e., shouldn't Org Protocol be able to capture arbitrary keywords
> according to the attributes of the "org-protocol" link? What is the
> point of using
>
On Tue, Oct 17, 2017 at 12:31 PM Berry, Charles wrote:
> The copy buffer that org-export-as sets up will contain this src block
> *after* the babel process runs.
>
> As you can see the headers are stripped off of it.
>
Oh! That explains!
> So you need to do something tricky to hold onto those
Hello,
Deepak Cherian writes:
> E.g.
>
> * Heading 1 ...
> * Heading 2 :noexport:...
>
> The second ellipsis is bolded because it appears after a ':'.
FWIW, I cannot reproduce this. You may want to update Org.
Regards,
--
Nicolas Goaziou
> On Oct 17, 2017, at 5:51 AM, Kaushal Modi wrote:
>
> So it is clear that the parameters are read inside
> org-element-src-block-parser, but I don't understand why
> (org-element-property :parameters src-block) is unable to fetch the same.
>
> Hints?
> --
The copy buffer that org-export-a
Nicolas Goaziou writes:
[...]
> Then it's `forward-line', not `forward-char', because there could be
> trailing spaces at the end of the paragraph, e.g.
>
>This is a paragraph.
Okay, changed to `forward-line'.
> Also, my question still holds, what about the last paragraph in a buffer
> no
On Tue, Oct 17, 2017 at 8:51 AM Kaushal Modi wrote:
> Hello,
>
> I am using the latest Org master.
>
> I am trying to retrieving user-set parameters for a source block. While I
> am able to retrieve the :switches property for the src-block element,
> :parameters always returns as nil.
>
Here's a
E.g.
* Heading 1 ...
* Heading 2 :noexport:...
The second ellipsis is bolded because it appears after a ':'.
Deepak
Hello,
I am using the latest Org master.
I am trying to retrieving user-set parameters for a source block. While I
am able to retrieve the :switches property for the src-block element,
:parameters always returns as nil.
Here's a dummy version of the function I am using to parse source blocks in
Hello,
you will find attached a simple patch to add a new parameter to the
column view dynamic block: minlevel.
This parameter mirrors the behavior of the maxlevel parameter: only
headings below a given level will be included in the table.
I use this feature in documents where I want to keep a l
Hello,
Allen Li writes:
> * doc/org.texi (@code{capture} protocol): Fix placeholder names
> (Template expansion): Add org-protocol placeholders
>
> * lisp/org.el (org-store-link-plist): Fix docstring grammar
> (org-store-link-props): Fix docstring grammar
Thank you.
> +The following template p
Hello,
Allen Li writes:
> The current default behavior for org-refile and org-reverse-note-order
> does not treat Archive headings specially. Consider a .org file:
>
> * Some projects
> ** Some item...
> ** Archive :ARCHIVE:...
>
> Refiling an entry to "Some projects" results in:
>
> * Some pro
Hello,
Eric Abrahamsen writes:
> Nicolas Goaziou writes:
>>> +(if (bolp)
>>> + (progn
>>> + (skip-chars-backward " \n\t")
>>> + (forward-char))
>>> + (end-of-line)
>>> + (insert "\n"))
>>
>> I don't understand this part. In particular, the `forward-char' looks
>> wrong.
Hello,
Allen Li writes:
> This makes org-insert-todo-heading-respect-content use the previous
> heading of the same level instead of the previous heading regardless
> of level.
>
> Given:
>
>* TODO some task
>** WAITING other task
>
> The original code yields:
>
>* TODO some task
>
23 matches
Mail list logo
