Hello,
this is a long thread so I did not read everything, just want to mention
that in org-dp.el I did something similar using
- tempo templates (for a programmer who wants to insert an
org-dp-create call in his emacs-lisp program) and
- a universal (org) prompt function for a user who wants t
Rasmus writes:
> Hi Eric,
>
>
>> It incorporates Rasmus' org-tempo.el file, with modifications, and
>> Thomas' suggestion to re-instate `org-try-structure-completion', and,
>> erm, stardiviner's request to honor
>> `org-babel-uppercase-example-markers'.
>>
>> Remaining issues:
>>
>> 1. The "org-i
Hi Eric,
> It incorporates Rasmus' org-tempo.el file, with modifications, and
> Thomas' suggestion to re-instate `org-try-structure-completion', and,
> erm, stardiviner's request to honor
> `org-babel-uppercase-example-markers'.
>
> Remaining issues:
>
> 1. The "org-include" tempo template doesn'
Ok, I see, Just I have to replace all uppercased babels and example blocks
to lowercase to keep same.
I have a lot of org files. Huge for me.
I can take with the lower-case tag.
[stardiviner] GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter: @numbchild
"numbch...@gmail.com" writes:
> Yeah, I misunderstand your code. Anyway, It should be like this:
>
> #+BEGIN_SRC python
> ...
> #+END_SRC
>
> #+BEGIN_EXAMPLE
> ...
> #+END_EXAMPLE
>
> etc
If you look back up this (admittedly very long) thread, you'll see the
general consensus is to move to lower
Yeah, I misunderstand your code. Anyway, It should be like this:
#+BEGIN_SRC python
...
#+END_SRC
#+BEGIN_EXAMPLE
...
#+END_EXAMPLE
etc
[stardiviner] GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter: @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3
"numbch...@gmail.com" writes:
> I think the function `org-insert-structure-template' also should respect the
> `org-babel-uppercase-example-markers'.
> Besides, your new diff does not have a condition on
> `org-babel-uppercase-example-markers', you just use `upcase-initials` by
> default. Then
I think the function `org-insert-structure-template' also should respect
the `org-babel-uppercase-example-markers'.
Besides, your new diff does not have a condition on
`org-babel-uppercase-example-markers', you just use `upcase-initials` by
default. Then the new `tempo` snippets will be uppercase,
"Thomas S. Dye" writes:
> Eric Abrahamsen writes:
>
>> Rasmus writes:
>>
>>> Hi Eric,
>>>
>>> Eric Abrahamsen writes:
>>>
> Also, Eric, it seems that org-structure-template-alist only supports a
> single letter for short-hands (the car of an entry in
> org-structure-template-alist i
+1 I added a snippet for ` GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter: @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433
Blog: http://stardiviner.github.io/
On Sun, Nov 12, 2017 at 12:35 PM, Matt Lundin wrote:
> Carsten Domini
Carsten Dominik writes:
> I have always come down on the side of NOT breaking backward
> compatibility unless we really HAVE TO in order to make progress. The
> reason for this bias is because most Org users are not reading this
> maling list and just want the system to function and to continue t
Eric Abrahamsen writes:
> Rasmus writes:
>
>> Hi Eric,
>>
>> Eric Abrahamsen writes:
>>
Also, Eric, it seems that org-structure-template-alist only supports a
single letter for short-hands (the car of an entry in
org-structure-template-alist is a char). I used to have blocks lik
I agree. I hope this feature too.
+1
On 11/10/2017 05:31 PM, Rasmus wrote:
> Hi Eric,
>
> Eric Abrahamsen writes:
>
>>> Also, Eric, it seems that org-structure-template-alist only supports a
>>> single letter for short-hands (the car of an entry in
>>> org-structure-template-alist is a char).
Rasmus writes:
> Hi Eric,
>
> Eric Abrahamsen writes:
>
>>> Also, Eric, it seems that org-structure-template-alist only supports a
>>> single letter for short-hands (the car of an entry in
>>> org-structure-template-alist is a char). I used to have blocks like ">> expanding to an "abstract" spe
Hi Eric,
Eric Abrahamsen writes:
>> Also, Eric, it seems that org-structure-template-alist only supports a
>> single letter for short-hands (the car of an entry in
>> org-structure-template-alist is a char). I used to have blocks like "> expanding to an "abstract" special-block, which I guess i
One more vote in favor of not removing my own use, I added
Anyway, just an opinion. "<" macros save me tons of time with ox-latex
markup. I like them.
hjh
Sent with AquaMail for Android
http://www.aqua-mail.com
Rasmus writes:
> Rasmus writes:
>
>> Nicolas Goaziou writes:
>>
>>> Takaaki Ishikawa writes:
>>>
I also support the idea of keeping ">>> Please give importance to the backward compatibility in this case.
>>>
>>> I explained why I thought it could be removed. I also suggested
>>> solutions
Rasmus writes:
> Nicolas Goaziou writes:
>
>> Takaaki Ishikawa writes:
>>
>>> I also support the idea of keeping ">> Please give importance to the backward compatibility in this case.
>>
>> I explained why I thought it could be removed. I also suggested
>> solutions to get an equivalent feature
Nicolas Goaziou writes:
> Takaaki Ishikawa writes:
>
>> I also support the idea of keeping "> Please give importance to the backward compatibility in this case.
>
> I explained why I thought it could be removed. I also suggested
> solutions to get an equivalent feature without implementing it in
On Thu, Nov 9, 2017 at 5:31 AM, Thomas S. Dye wrote:
> Aloha Nicolas,
>
> Nicolas Goaziou writes:
>
> > Hello,
> >
> > Takaaki Ishikawa writes:
> >
> >> I also support the idea of keeping " >> Please give importance to the backward compatibility in this case.
> >
> > I explained why I thought it
Aloha Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> Takaaki Ishikawa writes:
>
>> I also support the idea of keeping "> Please give importance to the backward compatibility in this case.
>
> I explained why I thought it could be removed. I also suggested
> solutions to get an equivalent feature
Hello,
Takaaki Ishikawa writes:
> I also support the idea of keeping " Please give importance to the backward compatibility in this case.
I explained why I thought it could be removed. I also suggested
solutions to get an equivalent feature without implementing it in Org.
What is wrong with Ab
Perhaps what we can do is re-instate this functionality using the
built-in Emacs mechanisms?
I also support the idea of keeping ":
>
> Berry, Charles writes:
>
>>> On Nov 8, 2017, at 6:07 AM, Rasmus wrote:
>>>
>>> I think the template expansion a la ">> YASnippet installed for many years, and I never figured out how to use it
>>> properly. To me, it is a bit too complex a replacement.
>>
Berry, Charles writes:
>> On Nov 8, 2017, at 6:07 AM, Rasmus wrote:
>>
>> I think the template expansion a la "> YASnippet installed for many years, and I never figured out how to use it
>> properly. To me, it is a bit too complex a replacement.
>
>
> Me too. "
> I suspect that there will be c
Hello,
"Berry, Charles" writes:
>> On Nov 8, 2017, at 6:07 AM, Rasmus wrote:
>>
>> I think the template expansion a la "> YASnippet installed for many years, and I never figured out how to use it
>> properly. To me, it is a bit too complex a replacement.
>
>
> Me too. "
> I suspect that ther
> On Nov 8, 2017, at 6:07 AM, Rasmus wrote:
>
> I think the template expansion a la " YASnippet installed for many years, and I never figured out how to use it
> properly. To me, it is a bit too complex a replacement.
Me too. "
On 8 November 2017, Bastien wrote:
I'm aware of Yasnippet, but it is not in Emacs core and it can
be daunting for newcomers to install, customize and use.
The previous function was very straightforward and simple, the
cost for losing it seems to high to me. I'd rather have 10 lines
in Org (and
Bastien Guerry writes:
> Hi Nicolas,
>
> Nicolas Goaziou writes:
>
>> Bastien writes:
>>
>>> is there a simple mechanism in Emacs core to restore the same
>>> functionnality?
>>
>> Of course, it is called Abbrev mode: (info "(emacs)Abbrev
>> Concepts").
>
> Abbrev only expands on words constitu
Hi Nicolas,
Nicolas Goaziou writes:
> Bastien writes:
>
>> is there a simple mechanism in Emacs core to restore the same
>> functionnality?
>
> Of course, it is called Abbrev mode: (info "(emacs)Abbrev
> Concepts").
Abbrev only expands on words constituents, so " You may also use (info "(autot
Hi,
Thanks you, Eric, for providing this new functionality.
Nicolas Goaziou writes:
> Bastien writes:
>
>> Maybe I missed something in this thread, but what about making
>> the change backward-compatible by allowing "> be expanded? For me, I'd rather type
> I suggested the idea to remove " m
Bastien writes:
> is there a simple mechanism in Emacs core to restore the same
> functionnality?
Of course, it is called Abbrev mode: (info "(emacs)Abbrev Concepts").
You may also use (info "(autotype)Using Skeletons") for more advanced
uses.
Regards,
Hi Nicolas,
> I suggested the idea to remove " many other template systems, e.g., YASnippet, already provides this.
> I didn't want to re-implement the wheel and let, instead, various parts
> of Emacs cooperate.
is there a simple mechanism in Emacs core to restore the same
functionnality?
I'm aw
Hello,
Bastien writes:
> Maybe I missed something in this thread, but what about making
> the change backward-compatible by allowing " be expanded? For me, I'd rather type
Hi Eric,
thanks *a lot* for implementing this change!
Maybe I missed something in this thread, but what about making
the change backward-compatible by allowing "
On Mon, Nov 6, 2017 at 8:48 AM Nicolas Goaziou
wrote:
> I documented the two changes above in ORG-NEWS.
>
Thanks!
--
Kaushal Modi
Hello,
Kaushal Modi writes:
> On Sun, Nov 5, 2017 at 9:24 AM Kaushal Modi wrote:
>
>> This is a breaking change though (org-try-structure-completion doesn't
>> exist any more.. it breaks at least my config.. could be breaking more).
>>
>
> It could actually be a wider breakage as it changes th
On 11/05/17 10:06 AM, Nicolas Goaziou wrote:
> Hello,
>
> Eric Abrahamsen writes:
>
>> From 055af9e9545947b9aeccc3370c8b67a237eea5d8 Mon Sep 17 00:00:00 2001
>> From: Eric Abrahamsen
>> Date: Mon, 30 Oct 2017 10:55:29 -0700
>> Subject: [PATCH] Replace easy templates with org-insert-structure-tem
On Sun, Nov 5, 2017 at 9:24 AM Kaushal Modi wrote:
> This is a breaking change though (org-try-structure-completion doesn't
> exist any more.. it breaks at least my config.. could be breaking more).
>
It could actually be a wider breakage as it changes the structure of
org-structure-template-al
On Sun, Nov 5, 2017 at 4:07 AM Nicolas Goaziou
wrote:
> Hello,
>
> Eric Abrahamsen writes:
>
> > From 055af9e9545947b9aeccc3370c8b67a237eea5d8 Mon Sep 17 00:00:00 2001
> > From: Eric Abrahamsen
> > Date: Mon, 30 Oct 2017 10:55:29 -0700
> > Subject: [PATCH] Replace easy templates with
> org-inse
Hello,
Eric Abrahamsen writes:
> From 055af9e9545947b9aeccc3370c8b67a237eea5d8 Mon Sep 17 00:00:00 2001
> From: Eric Abrahamsen
> Date: Mon, 30 Oct 2017 10:55:29 -0700
> Subject: [PATCH] Replace easy templates with org-insert-structure-template
>
> * lisp/org.el (org-insert-structure-template):
Sorry, last patch had some documentation errors.
>From 055af9e9545947b9aeccc3370c8b67a237eea5d8 Mon Sep 17 00:00:00 2001
From: Eric Abrahamsen
Date: Mon, 30 Oct 2017 10:55:29 -0700
Subject: [PATCH] Replace easy templates with org-insert-structure-template
* lisp/org.el (org-insert-structure-temp
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> This will get there eventually! Because there's likely to be more
>> tweaking, I haven't touched the manual or the tests yet, just reworked
>> the option and function:
>
> Thank you. Some comments follow.
>
>> #+BEGIN_SRC elisp
>>
On Monday, 30 Oct 2017 at 12:05, Nicolas Goaziou wrote:
[...]
> As suggested by Rasmus once, maybe we could get away from FORTRAN touch
> and insert everything lowercase.
+1 (repeat many times)
--
: Eric S Fraga via Emacs 27.0.50, Org release_9.1.2-155-gf474c7
signature.asc
Description: PGP
Hello,
Eric Abrahamsen writes:
> This will get there eventually! Because there's likely to be more
> tweaking, I haven't touched the manual or the tests yet, just reworked
> the option and function:
Thank you. Some comments follow.
> #+BEGIN_SRC elisp
> (defcustom org-structure-template-alist
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> In that case, would you be more in favor of a keymap-plus-subkey system,
>> or a keymap-plus-prompt system?
>
> I have no strong opinion, but a keymap-plus-subkey system (subkeys
> matching current keys in `org-structure-template-
Hello,
Eric Abrahamsen writes:
> In that case, would you be more in favor of a keymap-plus-subkey system,
> or a keymap-plus-prompt system?
I have no strong opinion, but a keymap-plus-subkey system (subkeys
matching current keys in `org-structure-template-alist') with an
additional key (e.g. )
Eric Abrahamsen writes:
> Nicolas Goaziou writes:
>
>> Hello,
>>
>> Eric Abrahamsen writes:
>>
>>> Kaushal Modi writes:
>>>
On Fri, Oct 20, 2017, 5:43 PM Kaushal Modi wrote:
>>>
>>> [...]
>>>
@Eric: I believe you were sort of onboard with this suggestion, just gated
by a doubt
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> Kaushal Modi writes:
>>
>>> On Fri, Oct 20, 2017, 5:43 PM Kaushal Modi wrote:
>>
>> [...]
>>
>>> @Eric: I believe you were sort of onboard with this suggestion, just gated
>>> by a doubt if this actually can make into master.
Hello,
Eric Abrahamsen writes:
> Kaushal Modi writes:
>
>> On Fri, Oct 20, 2017, 5:43 PM Kaushal Modi wrote:
>
> [...]
>
>> @Eric: I believe you were sort of onboard with this suggestion, just gated
>> by a doubt if this actually can make into master.
>
> In principle yes, I agree it's odd t
Kaushal Modi writes:
> On Fri, Oct 20, 2017, 5:43 PM Kaushal Modi wrote:
[...]
> @Eric: I believe you were sort of onboard with this suggestion, just gated by
> a doubt if this actually can make into master.
In principle yes, I agree it's odd to have two completely different
systems for ess
On Mon, Oct 23, 2017 at 10:00 AM Carsten Dominik wrote:
> I am not sure I understand, at least with transient-region turned on.
> Typing
You're correct.
> Or do you mean to actually put "<" into a keymap?
>
I actually do that in my personal config .. Maybe binding "<" in org keymap
is the si
On Mon, Oct 23, 2017 at 12:52 PM, Kaushal Modi
wrote:
> On Fri, Oct 20, 2017, 5:43 PM Kaushal Modi wrote:
>
>> On Fri, Oct 20, 2017 at 5:15 PM Eric Abrahamsen
>> wrote:
>>
>>> The template really only inserts the block type, not anything specific
>>> like the source language or export backend.
On Fri, Oct 20, 2017, 5:43 PM Kaushal Modi wrote:
> On Fri, Oct 20, 2017 at 5:15 PM Eric Abrahamsen
> wrote:
>
>> The template really only inserts the block type, not anything specific
>> like the source language or export backend.
>
>
> Right, but based on the code you have, you can easily add
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> Kaushal Modi writes:
>
>>> I just tried it out, and it works great!
>>>
>>> I have a comment about
>>>
>>> (when (string-equal (downcase type) "example")
>>> (org-escape-code-in-region s e))
>>>
>>> I have never needed to
Hello,
Eric Abrahamsen writes:
> Kaushal Modi writes:
>> I just tried it out, and it works great!
>>
>> I have a comment about
>>
>> (when (string-equal (downcase type) "example")
>> (org-escape-code-in-region s e))
>>
>> I have never needed to escape org in example, blocks, but I *have
Kaushal Modi writes:
> On Fri, Oct 20, 2017 at 5:15 PM Eric Abrahamsen
> wrote:
>
> The template really only inserts the block type, not anything specific
> like the source language or export backend.
>
> Right, but based on the code you have, you can easily add "SRC org", "SRC
> emacs-lisp"
thx thats perfect
Z
On Sat, Oct 21, 2017 at 2:59 PM, Marco Wahl wrote:
> The following message is a courtesy copy of an article
> that has been posted to gmane.emacs.orgmode as well.
>
> Hi!
>
> Xebar Saram writes:
>
> > this looks really cool and would love to try. as a non technical user,
>
Hi!
Xebar Saram writes:
> this looks really cool and would love to try. as a non technical user, how
> does one use the patch to get the functionality? is there a way to create a
> clean function only version from the patch i can try?
You could simply pick the relevant parts from the patch and
Hi all
this looks really cool and would love to try. as a non technical user, how
does one use the patch to get the functionality? is there a way to create a
clean function only version from the patch i can try?
thx!
Z
On Sat, Oct 21, 2017 at 12:43 AM, Kaushal Modi
wrote:
> On Fri, Oct 20, 20
On Fri, Oct 20, 2017 at 5:15 PM Eric Abrahamsen
wrote:
> The template really only inserts the block type, not anything specific
> like the source language or export backend.
Right, but based on the code you have, you can easily add "SRC org", "SRC
emacs-lisp" to the default value of that list.
Kaushal Modi writes:
> Also, if the type is "src", shouldn't the point end up after "#+BEGIN_SRC"?
> Because the user will anyways need to type something there.
My original version did that. It might be nice to still do that
selectively if the user adds a SRC or EXPORT block.
> Finally, I am t
Kaushal Modi writes:
> On Fri, Oct 20, 2017 at 2:07 PM Eric Abrahamsen
> wrote:
>
> Okay, here's another version, with a new keybinding and completion. The
> completion strings are uppercase, which might not always be the right
> thing, but probably more often than not.
>
> Hi Eric,
>
> I ju
Also, if the type is "src", shouldn't the point end up after "#+BEGIN_SRC"?
Because the user will anyways need to type something there.
Finally, I am trying to understand what this does:
(if (bolp)
(progn
(skip-chars-backward " \n\t")
(forward-line))
;; snip
)
If the point is
On Fri, Oct 20, 2017 at 2:07 PM Eric Abrahamsen
wrote:
> Okay, here's another version, with a new keybinding and completion. The
> completion strings are uppercase, which might not always be the right
> thing, but probably more often than not.
>
Hi Eric,
I just tried it out, and it works great!
Carsten Dominik writes:
> Hi Eric,
>
> On Wed, Oct 18, 2017 at 4:58 PM, Eric Abrahamsen
> wrote:
>
> Carsten Dominik writes:
>
> > Dear all,
> >
> > this is great added functionality that I have missed a lot myself. Thanks
> for this! Also, I like the key binding.
>
> I do too, though
Hi Eric,
On Wed, Oct 18, 2017 at 4:58 PM, Eric Abrahamsen
wrote:
> Carsten Dominik writes:
>
> > Dear all,
> >
> > this is great added functionality that I have missed a lot myself.
> Thanks for this! Also, I like the key binding.
>
> I do too, though I also notice it conflicts with inlineta
Carsten Dominik writes:
> Dear all,
>
> this is great added functionality that I have missed a lot myself. Thanks
> for this! Also, I like the key binding.
I do too, though I also notice it conflicts with inlinetask insertion.
> One improvement I can think of it to read the block type with c
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
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"))
>>
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'
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
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.
Eric Abrahamsen writes:
[...]
> #+BEGIN_SRC org
> #+BEGIN_FOO
> This is a paragraph.
>
> #+END_FOO
>
> This is another paragraph.
> #+END_SRC
Make that:
#+BEGIN_FOO
This is a paragraph
#+END_FOO
This is another paragraph
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> How does this look?
>
> Thank you! I have some questions and remarks.
>
>> * etc/ORG-NEWS: Mention in news.
>
> This doesn't need to be added to the commit message.
>
>> +Do not be put off by having to remember the source block sy
Hello,
Eric Abrahamsen writes:
> How does this look?
Thank you! I have some questions and remarks.
> * etc/ORG-NEWS: Mention in news.
This doesn't need to be added to the commit message.
> +Do not be put off by having to remember the source block syntax. Org mode
> +offers two ways of speed
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> Nicolas Goaziou writes:
>>
>>
>> [...]
>>
>>> C-c C-x t is free, tho.
>>
>> Oops, I think that's what I meant to type. Here's the latest version of
>> the patch -- I removed the bit fooling with the location of point at the
>> en
Hello,
Eric Abrahamsen writes:
> Nicolas Goaziou writes:
>
>
> [...]
>
>> C-c C-x t is free, tho.
>
> Oops, I think that's what I meant to type. Here's the latest version of
> the patch -- I removed the bit fooling with the location of point at the
> end, as it seemed simpler was better. How's
Nicolas Goaziou writes:
[...]
> C-c C-x t is free, tho.
Oops, I think that's what I meant to type. Here's the latest version of
the patch -- I removed the bit fooling with the location of point at the
end, as it seemed simpler was better. How's this look?
Eric
>From b8636d918e9ff79cac3200033
Hello,
Eric Abrahamsen writes:
> On 09/10/17 14:44 PM, Nicolas Goaziou wrote:
>
> [...]
>
>> Some free key bindings:
>> - C-c C-x C-e
>> - C-c C-x C-g
>> - C-c C-x C-h
>> - C-c C-x C-k
>> - C-c C-x h
>> - C-c C-x j
>> - C-c C-x k
>> - C-c C-x l
>> - C-c C-x m
>> - C-c C-x n
>> - C-c C-x r
>> - C
On 09/10/17 14:44 PM, Nicolas Goaziou wrote:
[...]
> Some free key bindings:
> - C-c C-x C-e
> - C-c C-x C-g
> - C-c C-x C-h
> - C-c C-x C-k
> - C-c C-x h
> - C-c C-x j
> - C-c C-x k
> - C-c C-x l
> - C-c C-x m
> - C-c C-x n
> - C-c C-x r
> - C-c C-x s
> - C-c C-x t
> - C-c C-x u
> - C-c C-x w
>
Hello,
Eric Abrahamsen writes:
> And here's an actual patch, with docs.
Thank you! Some comments follow.
> +This function can be used to wrap existing text or Org elements in
> +a #+BEGIN_FOO/#+END_FOO block. Not bound to a key by default.
Some free key bindings:
- C-c C-x C-e
- C-c C-x C-g
Eric Abrahamsen writes:
[...]
> Here's another stab at it. Is "example" the only block that should be
> verbatim? Will using `newline-and-indent' instead of inserting literal
> newlines solve the indentation problem?
>
>
> (defun org-insert-structure-template (type)
> "Insert a block structure
Josiah Schwab writes:
> Hi Eric,
>
>> Erm, I'd be surprised if there's a single Org mode binding that
>> *doesn't* start with C-c. That convention is right out the window with
>> Org...
>
> To be clear, this is referring to C-c and then a single ASCII letter,
> not just any binding that starts wi
Hi Eric,
> Erm, I'd be surprised if there's a single Org mode binding that
> *doesn't* start with C-c. That convention is right out the window with
> Org...
To be clear, this is referring to C-c and then a single ASCII letter,
not just any binding that starts with C-c.
The manual /suggests/ glob
Josiah Schwab writes:
> Hi Eric,
>
>>> We cannot bind it to "C-c i", this is a reserved key-binding. But we can
>>> suggest users to do so in the manual. Or find another binding.
>>
>> That's fine. Incidentally, why is "C-c i" reserved? It's not bound to
>> anything here. Does it look like in te
Hi Eric,
>> We cannot bind it to "C-c i", this is a reserved key-binding. But we can
>> suggest users to do so in the manual. Or find another binding.
>
> That's fine. Incidentally, why is "C-c i" reserved? It's not bound to
> anything here. Does it look like in terminal Emacs?
The keybinding co
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> The easy template entry thing is useful as far as it goes, but for some
>> reason I find myself "marking up" existing text in Org as least as often
>> as I'm writing new text from scratch. I've always wanted a "wrap region
>> in b
Adam Porter writes:
> "...it is a good idea to make a marker point nowhere if you are sure you
> don’t need it any more. Markers that can no longer be accessed are
> eventually removed (*note Garbage Collection::)."
>
> I asked on /r/emacs about this but never got a firm answer; some thought
> t
Nicolas Goaziou writes:
> You need to clean these markers at the end of the function. Markers set
> to a position are never garbage-collected. Usually, it happens at the
> end of an `unwind-protect'.
Not that I oppose cleaning up markers after you're done with them, but
are they actually never c
Hello,
Eric Abrahamsen writes:
> The easy template entry thing is useful as far as it goes, but for some
> reason I find myself "marking up" existing text in Org as least as often
> as I'm writing new text from scratch. I've always wanted a "wrap region
> in block" command, and finally wrote one
Kaushal Modi writes:
> On Sat, Sep 2, 2017, 10:23 PM Adam Porter wrote:
>
> Hi Eric,
>
> Thanks for doing this. I've had some similar code in my config for a
> while. I'll share some of it here in case you find it useful in doing
> this. You especially might find the org-read-structure-te
On Sat, Sep 2, 2017, 10:23 PM Adam Porter wrote:
> Hi Eric,
>
> Thanks for doing this. I've had some similar code in my config for a
> while. I'll share some of it here in case you find it useful in doing
> this. You especially might find the org-read-structure-template
> function useful.
>
A
Hi Eric,
Thanks for doing this. I've had some similar code in my config for a
while. I'll share some of it here in case you find it useful in doing
this. You especially might find the org-read-structure-template
function useful.
Note that some of this uses s and hydra, which obviously isn't su
The easy template entry thing is useful as far as it goes, but for some
reason I find myself "marking up" existing text in Org as least as often
as I'm writing new text from scratch. I've always wanted a "wrap region
in block" command, and finally wrote one. Don't know why it took me so
long. Would
That is very kind of you - many thanks indeed for your assistance.
On Mon, May 8, 2017 at 4:05 PM, John Kitchin
wrote:
> I think this is basically what you are looking for.
>
> (defun org-heading-content ()
> (interactive)
> (let (bp ep)
> (setq bp (save-excursion
>(or (
I think this is basically what you are looking for.
(defun org-heading-content ()
(interactive)
(let (bp ep)
(setq bp (save-excursion
(or (and (outline-previous-heading)
(progn (org-end-of-meta-data)
(point)))
I don't know of a function. Something like this may be what you want.
not all elements have :contents-begin though
(let ((el (org-element-context)))
(buffer-substring-no-properties
(org-element-property :contents-begin el)
(org-element-property :contents-end el)))
It also a little tricky to f
Hi there
Is there a function that will give me the content of the current item? I
mean simply the text of the whole item without its heading or properties
drawer.
It seems to me likely that such a function would exist, but I haven't been
able to find it in the documentation.
Many thanks
Richard
1 - 100 of 153 matches
Mail list logo