Hi Óscar,
* Óscar Fuentes [2018-07-26; 13:57]:
> For the record: executing gpg2 from the command line is revealing:
>
> gpg: WARNING: message was not integrity protected
> gpg: Hint: If this message was created before the year 2003 it is
> likely that this message is legitimate. This is beca
In a nutshell, I propose that ", /, = and ~ be assigned to the syntax class
"paired delimiter", which is $. (This would allow electric-pair-mode to work
with them.)
The definition of org-mode as a derived mode contains the following lines:
(modify-syntax-entry ?@ "w")
(modify-syntax-entry ?
Hi Kaushal,
> How about adding this to your emacs config:
>
> …
> Make sure that that always evaluates before you do Org exports, and then
> simply use this in your Org files:
Thanks for the tips! I hadn’t thought of adding the functions to my Emacs
config, but that would work perfectly. On th
Hi,
I'm still an elisp beginner, so please bear with me.
I would like to be able to fully export org-mode files which make use of
the :export: tag.
Easist solution would be to remove the :export: tag, but usually I want
it's effect. But from time to time I need the full text exported.
I tried:
Similary, how about this for your first question:
In your emacs config:
(defun my/org-macro-hsapi-code (link anchor desc)
(let* ((link-1 (if (org-string-nw-p anchor)
(concat link "#" anchor)
link))
(desc-1 (or (org-string-nw-p desc) link-1)))
Hello Diego,
I can try to answer your second question.
On Thu, Jul 26, 2018 at 10:35 AM Diego Zamboni wrote:
>
> 2. Related to my workaround above, I am wondering if there's a way to
> refer to a source block as the macro definition. At the moment I just
> joined my whole elisp block into a sin
Hi,
I have two somewhat related questions:
1. Is there a way for macros to check how many arguments were passed, and
change its output depending on this? At the moment I found a solution using
an =(eval...)= macro, which checks the values of $1, $2, etc. and produces
the appropriate string. It wo
For the record: executing gpg2 from the command line is revealing:
gpg: WARNING: message was not integrity protected
gpg: Hint: If this message was created before the year 2003 it is
likely that this message is legitimate. This is because back
then integrity protection was not widely us
Jarmo Hurri writes:
> Greetings.
>
> I started doing some Schemeing in org,
Welcome to the club!
> and bumped into a couple of
> documentation issues I wanted to check / report.
>
> In short, I wonder whether
> 1. geiser should be listed as a scheme requirement in worg
> 2. ob-scheme.el should
