[O] org-link-minor-mode.el broken by recent org maint

[Samuel Wales]

org-link-minor-mode broken by recent maint.  both links and tses.

anybody else?

cannot bisect but these seem suspicious by name:

439fcfb * Fix link fontification
2d29269 * Fix link fontification

-- 
The Kafka Pandemic: 

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
.

Re: [O] No operator defined for property header-args

[Kevin Foley]

You're right, I thought because a refresh was needed for #+PROPERTY: it was
also needed for property blocks.  Thanks for your help.

Thanks,
Kevin Foley

On Wed, Jun 7, 2017 at 12:20 PM, Nicolas Goaziou 
wrote:

> Hello,
>
> Kevin Foley  writes:
>
> > Ah okay it's my misunderstanding then.  I'm trying to refresh the local
> > setup to apply a different set of header args to that tree.
> >
> > After some research it looks like I should just be calling
> > org-mode-restart.  Does that seem correct?
>
> I don't think you need to refresh anything for node properties. I.e.,
> the new value will be used during next evaluation.
>
>
> Regards,
>
> --
> Nicolas Goaziou
>

Re: [O] Custom keymaps on org blocks

[Grant Rettke]

On Wed, Jun 7, 2017 at 8:50 AM, John Kitchin  wrote:
> On the other hand, there are times when I am working on a document that has
> a lot of short code blocks, e.g. for lecture notes or blog posts, where it
> is sufficiently tedious to me to switch in and out of the special edit mode

These bindings make source block navigation and editing really fast and fun!

(define-key org-mode-map (kbd "s-j") #'org-babel-next-src-block)
(define-key org-mode-map (kbd "s-k") #'org-babel-previous-src-block)
(define-key org-mode-map (kbd "s-l") #'org-edit-src-code)
(define-key org-src-mode-map (kbd "s-l") #'org-edit-src-exit)

Here the 'l' key binding is the most important. It makes for fast
entry and exit of the source block.

For my mind the default bindings "C-c '" interrupts my mental flow. It
is like hearing the sound of a cash register drawer sliding out, doing
some work there and then getting shoved back in every single time.
Ouch.

On the other hand, "s-l" both to enter and exit the source blocks, is
like hearing a gentle breath of air to cool a cup of tea that is a
tiny bit too warm, doing your work and then another gentle breath when
you leave the block.

That is the best way I can describe how much difference the two
bindings make. It is really a "feels" thing, and it feels a lot
better.

Seriously, these bindings might make you fall in love with source
block editing all the time.

Re: [O] Custom keymaps on org blocks

[Grant Rettke]

On Wed, Jun 7, 2017 at 7:49 AM, John Kitchin  wrote:
> Grant Rettke writes:
>
>> You want Polymode: https://github.com/vspinu/polymode
>
> I have never been able to get polymode to work. Do have an incantation
> that works?

I forgot that I set it up for R markdown files. But it did work on my
machine after manually installing the `polymode' package.

https://github.com/grettke/home/blob/master/.emacs.el#L1992-L2005

>> It is confusing alternating between the Org major a mode and the
>> source block major mode as you scroll through documents. One second
>> you are an author for humans and the other an author for the computer.
>> That is how literate programming is defined in theory, but in practice
>> I don't do it like that because it is mentally jarring.
>
> Interesting perspective. I find switching to special edit mode jarring,
> particularly when it is just for the key bindings, e.g. lispy mode, or
> getting python indentation to work.

We are both surprised!

Re: [O] Minor addition to Speed Keys info node

[Nicolas Goaziou]

Kaushal Modi  writes:

> Thanks! I just pushed to the maint branch for the very first time (using
> magit on Termux on Nexus 6p!); also merged that to master. (That also
> merged your last commit on maint into master. Hope that is fine.)

Congratulations, and thank you.

> For future, should I refrain from doing the merges?

Why would you? It is a good habit to merge maint into master after
a patch. I didn't do it for my own commit because I'm about to commit
something else and wanted to reduce a bit the number of merge commits.

Regards,

Re: [O] Minor addition to Speed Keys info node

[Kaushal Modi]

On Wed, Jun 7, 2017 at 5:34 PM Nicolas Goaziou 
wrote:

> > +By default, Org has Speed Keys disabled.  To activate Speed Keys, set
> the
> > +variable @code{org-use-speed-commands} to a non-nil value.
>
> I overlooked this one: non-@code{nil}
>

Fixed :)


>
> I think you can push this, or we are going to nitpick over it until the
> end of time ;)
>

Thanks! I just pushed to the maint branch for the very first time (using
magit on Termux on Nexus 6p!); also merged that to master. (That also
merged your last commit on maint into master. Hope that is fine.)

For future, should I refrain from doing the merges?
-- 

Kaushal Modi

Re: [O] Minor addition to Speed Keys info node

[Nicolas Goaziou]

Kaushal Modi  writes:

> On Wed, Jun 7, 2017 at 4:44 PM Kaushal Modi  wrote:
>
>> Did you mean that I need to move those tags closer to where those vars are
>> actually referenced in that node?
>>
>
> Seems like that was the intention.

Correct.

>Also as I am referring to the org-speed-command-help function for the
>first time in the manual at the appropriate place, I have added an
>findex for that too.

OK.

> +By default, Org has Speed Keys disabled.  To activate Speed Keys, set the
> +variable @code{org-use-speed-commands} to a non-nil value.

I overlooked this one: non-@code{nil}

I think you can push this, or we are going to nitpick over it until the
end of time ;)

Regards,

Re: [O] Minor addition to Speed Keys info node

[Kaushal Modi]

On Wed, Jun 7, 2017 at 4:44 PM Kaushal Modi  wrote:

> Did you mean that I need to move those tags closer to where those vars are
> actually referenced in that node?
>

Seems like that was the intention. Also as I am referring to the
org-speed-command-help function for the first time in the manual at the
appropriate place, I have added an findex for that too.

Revised patch for maint:

>From d15b72a0c8983eb2007c2393c3d76ba74eada109 Mon Sep 17 00:00:00 2001
From: Kaushal Modi 
Date: Wed, 7 Jun 2017 11:34:39 -0400
Subject: [PATCH] Mention org-speed-command-help in Speed Keys info node

* doc/org.texi (Speed keys): Mention org-speed-command-help.
---
 doc/org.texi | 21 -
 1 file changed, 12 insertions(+), 9 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index 11c4ac4c72..2ac142fc2b 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -17018,8 +17018,6 @@ More templates can added by customizing the variable
 @node Speed keys
 @section Speed keys
 @cindex speed keys
-@vindex org-use-speed-commands
-@vindex org-speed-commands-user

 Single keystrokes can execute custom commands in an Org file when the
cursor
 is on a headline.  Without the extra burden of a meta or modifier key,
Speed
@@ -17028,14 +17026,19 @@ navigation, Speed Keys may come in handy on small
mobile devices that do not
 have full keyboards.  Speed Keys may also work on TTY devices known for
their
 problems when entering Emacs keychords.

-By default, Org has Speed Keys disabled.  To activate Speed Keys, configure
-the variable @code{org-use-speed-commands}.  To trigger a Speed Key, the
-cursor must be at the beginning of an Org headline, before any of the
stars.
+@vindex org-use-speed-commands
+By default, Org has Speed Keys disabled.  To activate Speed Keys, set the
+variable @code{org-use-speed-commands} to a non-nil value.  To trigger a
+Speed Key, the cursor must be at the beginning of an Org headline, before
any
+of the stars.

-Org comes with a pre-defined list of Speed Keys; @kbd{?} shows currently
-active Speed Keys.  To add or modify Speed Keys, customize the variable,
-@code{org-speed-commands-user}.  For more details, see the variable's
-docstring.
+@vindex org-speed-commands-user
+@findex org-speed-command-help
+Org comes with a pre-defined list of Speed Keys.  To add or modify Speed
+Keys, customize the variable, @code{org-speed-commands-user}.  For more
+details, see the variable's docstring.  With Speed Keys activated, @kbd{M-x
+org-speed-command-help}, or @kbd{?} when cursor is at the beginning of an
Org
+headline, shows currently active Speed Keys, including the user-defined
ones.


 @node Code evaluation security
-- 
2.13.0


-- 

Kaushal Modi

Re: [O] Minor addition to Speed Keys info node

[Kaushal Modi]

On Wed, Jun 7, 2017 at 4:21 PM Nicolas Goaziou 
wrote:

> @vindex org-use-speed-commands
> > +By default, Org has Speed Keys disabled.  To activate Speed Keys, set
> the
> > +variable @code{org-use-speed-commands} to a non-nil value.  To trigger a
> > +Speed Key, the cursor must be at the beginning of an Org headline,
> before
> > any
> > +of the stars.
>
> @vindex org-speed-commands-user
> > +Org comes with a pre-defined list of Speed Keys.  To add or modify Speed
> > +Keys, customize the variable, @code{org-speed-commands-user}.  For more
> > +details, see the variable's docstring.  With Speed Keys activated,
> @kbd{M-x
> > +org-speed-command-help}, or @kbd{?} when cursor is at the beginning of
> an
> > Org
> > +headline, shows currently active Speed Keys, including the user-defined
> > ones.
>
> Barring the two additions above, it looks good. Thank you.
>

I see that the vindex tags are already there:
http://orgmode.org/cgit.cgi/org-mode.git/tree/doc/org.texi?id=8305c9381efaf3ad5f95ee96bb15209f3d687707#n17021


[image: image.png]
Or I didn't understand where I need to add those.. Did you mean that I need
to move those tags closer to where those vars are actually referenced in
that node?

-- 

Kaushal Modi

Re: [O] Minor addition to Speed Keys info node

[Nicolas Goaziou]

Kaushal Modi  writes:

> One minor iteration.. I think below reads with a better flow.. WDYT?

[...]

@vindex org-use-speed-commands
> +By default, Org has Speed Keys disabled.  To activate Speed Keys, set the
> +variable @code{org-use-speed-commands} to a non-nil value.  To trigger a
> +Speed Key, the cursor must be at the beginning of an Org headline, before
> any
> +of the stars.

@vindex org-speed-commands-user
> +Org comes with a pre-defined list of Speed Keys.  To add or modify Speed
> +Keys, customize the variable, @code{org-speed-commands-user}.  For more
> +details, see the variable's docstring.  With Speed Keys activated, @kbd{M-x
> +org-speed-command-help}, or @kbd{?} when cursor is at the beginning of an
> Org
> +headline, shows currently active Speed Keys, including the user-defined
> ones.

Barring the two additions above, it looks good. Thank you.

Regards,

Re: [O] order of evaluation upon export: macros are evaluated too soon

[Nicolas Goaziou]

Hello,

"Charles C. Berry"  writes:

> Maybe implement somethng like this:
>
> #+BEGIN_SRC emacs-lisp
>(defun n-noexport (x y)
>  (let ((tags (nth 5 (org-heading-components
>(unless (and tags
>  (string-match ":noexport:" tags))
>   (org-macro--counter-increment x y
> #+END_SRC
>
> #+MACRO: n2 (eval (n-noexport "$1" "$2"))
>
> * heading 1
>
> {{{n2()}}}
>
>
> * heading 2:noexport:notever:
>
> {{{n2()}}}
>
> * heading 3
> {{{n2()}}}
>

What about simply removing macros in :noexport: trees from
a pre-processing-hook?

Regards,

-- 
Nicolas Goaziou

Re: [O] order of evaluation upon export: macros are evaluated too soon

[Charles C. Berry]

On Wed, 7 Jun 2017, Eric S Fraga wrote:


Hello all,

I have a document with this (ECM) structure:

#+begin_src org
 ,#+macro: item I{{{n(i)}}}@@latex:}%@@
 ,#+options: toc:nil num:nil

 ,* {{{item()}}} Some topic
 ,* {{{item()}}} Another topic  :noexport:
 ,* {{{item()}}} A final one
#+end_src

I would like the exported headings to be numbered Q1, Q2, ... but only
the exported ones.



Maybe implement somethng like this:


#+BEGIN_SRC emacs-lisp
  (defun n-noexport (x y)
(let ((tags (nth 5 (org-heading-components
  (unless (and tags
   (string-match ":noexport:" tags))
(org-macro--counter-increment x y
#+END_SRC

#+MACRO: n2 (eval (n-noexport "$1" "$2"))


* heading 1

{{{n2()}}}


* heading 2:noexport:notever:

{{{n2()}}}

* heading 3
{{{n2()}}}


HTH,

Chuck

Re: [O] Minor addition to Speed Keys info node

[Kaushal Modi]

One minor iteration.. I think below reads with a better flow.. WDYT?

@kbd{M-x org-speed-command-help}, or @kbd{?} when cursor is at the
beginning of an Org headline, shows currently ..

Here's the full patch:

>From 5886b6f7fe82858ae49b55d409d1baf20942dae8 Mon Sep 17 00:00:00 2001
From: Kaushal Modi 
Date: Wed, 7 Jun 2017 11:34:39 -0400
Subject: [PATCH] Mention org-speed-command-help in Speed Keys info node

* doc/org.texi (Speed keys): Mention org-speed-command-help.
---
 doc/org.texi | 18 ++
 1 file changed, 10 insertions(+), 8 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index 11c4ac4c72..04485b12e0 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -17028,14 +17028,16 @@ navigation, Speed Keys may come in handy on small
mobile devices that do not
 have full keyboards.  Speed Keys may also work on TTY devices known for
their
 problems when entering Emacs keychords.

-By default, Org has Speed Keys disabled.  To activate Speed Keys, configure
-the variable @code{org-use-speed-commands}.  To trigger a Speed Key, the
-cursor must be at the beginning of an Org headline, before any of the
stars.
-
-Org comes with a pre-defined list of Speed Keys; @kbd{?} shows currently
-active Speed Keys.  To add or modify Speed Keys, customize the variable,
-@code{org-speed-commands-user}.  For more details, see the variable's
-docstring.
+By default, Org has Speed Keys disabled.  To activate Speed Keys, set the
+variable @code{org-use-speed-commands} to a non-nil value.  To trigger a
+Speed Key, the cursor must be at the beginning of an Org headline, before
any
+of the stars.
+
+Org comes with a pre-defined list of Speed Keys.  To add or modify Speed
+Keys, customize the variable, @code{org-speed-commands-user}.  For more
+details, see the variable's docstring.  With Speed Keys activated, @kbd{M-x
+org-speed-command-help}, or @kbd{?} when cursor is at the beginning of an
Org
+headline, shows currently active Speed Keys, including the user-defined
ones.


 @node Code evaluation security
-- 
2.13.0




On Wed, Jun 7, 2017 at 12:32 PM Kaushal Modi  wrote:

> On Wed, Jun 7, 2017 at 12:21 PM Nicolas Goaziou 
> wrote:
>
>> @kbd{?}---when cursor is at the beginning of an Org headline---shows
>> currently active Speed Keys,...
>>
>> > Org +headline) shows currently active Speed Keys, including the
>> > user-defined ones.
>>
>> Otherwise, LGTM.
>>
>
> Thanks. I was unaware of the --- syntax.
>
> Here's the updated patch:
>
> From 1a767fb97b680b9fef5d0fd301c9fcf951b705e3 Mon Sep 17 00:00:00 2001
> From: Kaushal Modi 
> Date: Wed, 7 Jun 2017 11:34:39 -0400
> Subject: [PATCH] Mention org-speed-command-help in Speed Keys info node
>
> * doc/org.texi (Speed keys): Mention org-speed-command-help.
> ---
>  doc/org.texi | 19 +++
>  1 file changed, 11 insertions(+), 8 deletions(-)
>
> diff --git a/doc/org.texi b/doc/org.texi
> index 11c4ac4c72..50a96333f2 100644
> --- a/doc/org.texi
> +++ b/doc/org.texi
> @@ -17028,14 +17028,17 @@ navigation, Speed Keys may come in handy on
> small mobile devices that do not
>  have full keyboards.  Speed Keys may also work on TTY devices known for
> their
>  problems when entering Emacs keychords.
>
> -By default, Org has Speed Keys disabled.  To activate Speed Keys,
> configure
> -the variable @code{org-use-speed-commands}.  To trigger a Speed Key, the
> -cursor must be at the beginning of an Org headline, before any of the
> stars.
> -
> -Org comes with a pre-defined list of Speed Keys; @kbd{?} shows currently
> -active Speed Keys.  To add or modify Speed Keys, customize the variable,
> -@code{org-speed-commands-user}.  For more details, see the variable's
> -docstring.
> +By default, Org has Speed Keys disabled.  To activate Speed Keys, set the
> +variable @code{org-use-speed-commands} to a non-nil value.  To trigger a
> +Speed Key, the cursor must be at the beginning of an Org headline, before
> any
> +of the stars.
> +
> +Org comes with a pre-defined list of Speed Keys.  To add or modify Speed
> +Keys, customize the variable, @code{org-speed-commands-user}.  For more
> +details, see the variable's docstring.  With Speed Keys activated,
> @kbd{M-x
> +org-speed-command-help} or @kbd{?}---when cursor is at the beginning of an
> +Org headline---shows currently active Speed Keys, including the
> user-defined
> +ones.
>
>
>  @node Code evaluation security
> --
> 2.13.0
>
>
> --
>
> Kaushal Modi
>
-- 

Kaushal Modi

Re: [O] Minor addition to Speed Keys info node

[Kaushal Modi]

On Wed, Jun 7, 2017 at 12:21 PM Nicolas Goaziou 
wrote:

> @kbd{?}---when cursor is at the beginning of an Org headline---shows
> currently active Speed Keys,...
>
> > Org +headline) shows currently active Speed Keys, including the
> > user-defined ones.
>
> Otherwise, LGTM.
>

Thanks. I was unaware of the --- syntax.

Here's the updated patch:

>From 1a767fb97b680b9fef5d0fd301c9fcf951b705e3 Mon Sep 17 00:00:00 2001
From: Kaushal Modi 
Date: Wed, 7 Jun 2017 11:34:39 -0400
Subject: [PATCH] Mention org-speed-command-help in Speed Keys info node

* doc/org.texi (Speed keys): Mention org-speed-command-help.
---
 doc/org.texi | 19 +++
 1 file changed, 11 insertions(+), 8 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index 11c4ac4c72..50a96333f2 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -17028,14 +17028,17 @@ navigation, Speed Keys may come in handy on small
mobile devices that do not
 have full keyboards.  Speed Keys may also work on TTY devices known for
their
 problems when entering Emacs keychords.

-By default, Org has Speed Keys disabled.  To activate Speed Keys, configure
-the variable @code{org-use-speed-commands}.  To trigger a Speed Key, the
-cursor must be at the beginning of an Org headline, before any of the
stars.
-
-Org comes with a pre-defined list of Speed Keys; @kbd{?} shows currently
-active Speed Keys.  To add or modify Speed Keys, customize the variable,
-@code{org-speed-commands-user}.  For more details, see the variable's
-docstring.
+By default, Org has Speed Keys disabled.  To activate Speed Keys, set the
+variable @code{org-use-speed-commands} to a non-nil value.  To trigger a
+Speed Key, the cursor must be at the beginning of an Org headline, before
any
+of the stars.
+
+Org comes with a pre-defined list of Speed Keys.  To add or modify Speed
+Keys, customize the variable, @code{org-speed-commands-user}.  For more
+details, see the variable's docstring.  With Speed Keys activated, @kbd{M-x
+org-speed-command-help} or @kbd{?}---when cursor is at the beginning of an
+Org headline---shows currently active Speed Keys, including the
user-defined
+ones.


 @node Code evaluation security
-- 
2.13.0


-- 

Kaushal Modi

Re: [O] Minor addition to Speed Keys info node

[Nicolas Goaziou]

Hello,

Kaushal Modi  writes:

> +Org comes with a pre-defined list of Speed Keys.  To add or modify Speed
> +Keys, customize the variable, @code{org-speed-commands-user}.  For more
> +details, see the variable's docstring.  With Speed Keys activated, @kbd{M-x
> +org-speed-command-help} or @kbd{?} (when cursor is at the beginning of an

@kbd{?}---when cursor is at the beginning of an Org headline---shows
currently active Speed Keys,...

> Org +headline) shows currently active Speed Keys, including the
> user-defined ones.

Otherwise, LGTM.

Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] No operator defined for property header-args

[Nicolas Goaziou]

Hello,

Kevin Foley  writes:

> Ah okay it's my misunderstanding then.  I'm trying to refresh the local
> setup to apply a different set of header args to that tree.
>
> After some research it looks like I should just be calling
> org-mode-restart.  Does that seem correct?

I don't think you need to refresh anything for node properties. I.e.,
the new value will be used during next evaluation.


Regards,

-- 
Nicolas Goaziou

[O] order of evaluation upon export: macros are evaluated too soon

[Eric S Fraga]

Hello all,

I have a document with this (ECM) structure:

#+begin_src org
  ,#+macro: item I{{{n(i)}}}@@latex:}%@@
  ,#+options: toc:nil num:nil

  ,* {{{item()}}} Some topic
  ,* {{{item()}}} Another topic  :noexport:
  ,* {{{item()}}} A final one
#+end_src

I would like the exported headings to be numbered Q1, Q2, ... but only
the exported ones.  At the moment, the item macro is expanded on every
occurrence in the file, regardless of export settings.  So, if I export
to ASCII, I get:

: I1 Some topic
: =
: 
: 
: I3 A final one
: ==

whereas I want I2 for the second heading.  Example of use case: agenda
of meeting where certain commonly appearing entries may be excluded;
bank of questions for tutorials etc. with sub-selection; all kinds of
enumerations with different tag selections; ...

I used to do this with LaTeX counters but I thought I would use the new
counter capability in org.  Unfortunately, it doesn't do the job for me.

Any suggestions please?

thanks,
eric

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50, Org release_9.0.7-531-g530113


signature.asc
Description: PGP signature

Re: [O] Minor addition to Speed Keys info node

[Kaushal Modi]

The patch is rebased off the maint branch.

On Wed, Jun 7, 2017 at 11:39 AM Kaushal Modi  wrote:

> Hello,
>
> Here is a patch with some info added to make Speed Keys more accessible to
> users (inspired by [1]).
>
-- 

Kaushal Modi

[O] Minor addition to Speed Keys info node

[Kaushal Modi]

Hello,

Here is a patch with some info added to make Speed Keys more accessible to
users (inspired by [1]).

>From 43ff4c3da12a8ce0333c65372ab8ba51964e7a2a Mon Sep 17 00:00:00 2001
From: Kaushal Modi 
Date: Wed, 7 Jun 2017 11:34:39 -0400
Subject: [PATCH] Mention org-speed-command-help in Speed Keys info node

* doc/org.texi (Speed keys): Mention org-speed-command-help.
---
 doc/org.texi | 18 ++
 1 file changed, 10 insertions(+), 8 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index 11c4ac4c72..75bb9c79a2 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -17028,14 +17028,16 @@ navigation, Speed Keys may come in handy on small
mobile devices that do not
 have full keyboards.  Speed Keys may also work on TTY devices known for
their
 problems when entering Emacs keychords.

-By default, Org has Speed Keys disabled.  To activate Speed Keys, configure
-the variable @code{org-use-speed-commands}.  To trigger a Speed Key, the
-cursor must be at the beginning of an Org headline, before any of the
stars.
-
-Org comes with a pre-defined list of Speed Keys; @kbd{?} shows currently
-active Speed Keys.  To add or modify Speed Keys, customize the variable,
-@code{org-speed-commands-user}.  For more details, see the variable's
-docstring.
+By default, Org has Speed Keys disabled.  To activate Speed Keys, set the
+variable @code{org-use-speed-commands} to a non-nil value.  To trigger a
+Speed Key, the cursor must be at the beginning of an Org headline, before
any
+of the stars.
+
+Org comes with a pre-defined list of Speed Keys.  To add or modify Speed
+Keys, customize the variable, @code{org-speed-commands-user}.  For more
+details, see the variable's docstring.  With Speed Keys activated, @kbd{M-x
+org-speed-command-help} or @kbd{?} (when cursor is at the beginning of an
Org
+headline) shows currently active Speed Keys, including the user-defined
ones.


 @node Code evaluation security
-- 
2.13.0

[1]: https://emacs.stackexchange.com/q/33310/115
-- 

Kaushal Modi

Re: [O] No operator defined for property header-args

[Kevin Foley]

Ah okay it's my misunderstanding then.  I'm trying to refresh the local
setup to apply a different set of header args to that tree.

After some research it looks like I should just be calling
org-mode-restart.  Does that seem correct?

Thanks,
Kevin


On Tue, Jun 6, 2017 at 8:13 AM Nicolas Goaziou 
wrote:

> Hello,
>
> Kevin Foley  writes:
>
> > I've attached an ECM and below is my attempt at the backtrace.  Let me
> know
> > if I missed something.
> >
> > * org-at-property-p()
> > * #[0 "\301 \204 \302\303!\210\304\305!\306 \210\307\310 \311#8\204
> > \302\312 \"\210\313 !\207" [org-columns-current-fmt-compiled
> > org-at-property-p user-error "Not at a property"
> match-string-no-properties
> > 2 org-columns-get-format-and-top-level 3 assoc-string t "No operator
> > defined for property %s" org-columns-compute] 6
> > ("/home/kevin/.emacs.d/lib/org/lisp/org.elc"
> > . 550375) nil]()
> > * apply(#[0 "\301 \204 \302\303!\210\304\305!\306 \210\307\310 \311#8\204
> > \302\312 \"\210\313 !\207" [org-columns-current-fmt-compiled
> > org-at-property-p user-error "Not at a property"
> match-string-no-properties
> > 2 org-columns-get-format-and-top-level 3 assoc-string t "No operator
> > defined for property %s" org-columns-compute] 6
> > ("/home/kevin/.emacs.d/lib/org/lisp/org.elc"
> > . 550375) nil] nil)
> > * org-compute-property-at-point()
> >   funcall-interactively(org-compute-property-at-point)
> >   call-interactively(org-compute-property-at-point)
> >   org-property-action()
> >   funcall-interactively(org-property-action)
> >   call-interactively(org-property-action)
> >   org-ctrl-c-ctrl-c(nil)
> >   funcall-interactively(org-ctrl-c-ctrl-c nil)
> >   call-interactively(org-ctrl-c-ctrl-c nil nil)
> >   command-execute(org-ctrl-c-ctrl-c)
>
> AFAIU, when you are offered the `org-property-action' menu, you press
> "c", for `org-compute-property-at-point'.
>
> As a consequence, the error is expected since there is nothing to
> compute here. What did you expect instead?
>
> Regards,
>
> --
> Nicolas Goaziou
>
-- 
Thanks,
Kevin Foley

Re: [O] insert cell inside an org-mode table?

[John Kitchin]

I don't totally understand what you want to do. You can insert a row or
column into a table.

org-table-insert-column
org-table-insert-row

Are you trying to do something different than that?

John

---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu


On Wed, Jun 7, 2017 at 6:31 AM, Sharon Kimble 
wrote:

>
> I maintain my 'DrugFacts' website in mediawiki. I write my article in
> org-mode, export to mediawiki, correct the citations, then cut and paste
> into my mediawiki page. And it all works very well.
>
> But the front-page is a right swine! Here is the first two rows of my
> mediawiki front-page -
>
> --8<---cut here---start->8---
> {| 
> | '''Illegal'''
> | '''Category's'''
> | '''Legal'''
> | '''Prescription only'''
> | '''Substitute'''
> | '''Others'''
> |-
> |* [[Amphetamines]]
> |* [[:Category:Anaesthetics|Anaesthetics]]
> |* [[Alcohol]]
> |* [[Alprazolam]]
> |* [[Buprenorphine]]
> |* [[Flumazenil]]
> |-
> --8<---cut here---end--->8---
>
> And because writing mediawiki tables leads to brain damage, and a desire
> to consume 6 pints of beer as the world is going to end in ten minutes,
> according to Douglas Adams and Ford Prefect, I'm intending to create the
> table in org-mode and then export to mediawiki, correct as necessary,
> and upload. Which brings me to my question.
>
> Is it possible to insert a cell *inside* an org-mode table please, and
> auto-shuffle other rows/columns about to fit? According to the 'Table'
> menu in emacs, there isn't a way of doing it, and neither does the
> org-mode manual say that it can be done. But perhaps other people have
> found a way of doing it please?
>
> Hopefully thanks
> Sharon.
> --
> A taste of linux = http://www.sharons.org.uk
> TGmeds = http://www.tgmeds.org.uk
> DrugFacts = https://www.drugfacts.org.uk
> Debian 9.0, fluxbox 1.3.5-2, emacs 25.1.1, org-mode 9.0.7
>

Re: [O] Custom keymaps on org blocks

[John Kitchin]

I can see that. There are plenty of cases that certainly would not work,
e.g. in a Python block it would be a mistake to run a command that sends
the buffer to the interpreter! In the example I provided, you can see I
also had to "preserve" a few org-bindings so you could still do C-c ' to
get to the special edit. If you didn't know what was happening, it might
also appear that certain org-bindings you were used to had stopped working,
e.g. I have a lightning fast muscle memory to export a buffer, but it
doesn't work when in a src block with this modification (unless of course
it is "preserved" in the keymap). Whether this matters is up to the user,
since they get to choose how the keymap is defined. I would expect it
defaults to the org-mode-keymap.

On the other hand, there are times when I am working on a document that has
a lot of short code blocks, e.g. for lecture notes or blog posts, where it
is sufficiently tedious to me to switch in and out of the special edit mode
that I wanted to try this solution out, and it became clear you can't
really try it out without modifying the core org code that does the
font-locking on a block.

I don't think we have to go so far as to say we make multiple major mode
keybindings available, so much as context specific keybindings available
where there is value in it. We already have this in org-speed keys for
example, and even these can be context specific to do different things on
headings (even different things on headings with specific properties) and
blocks (
http://kitchingroup.cheme.cmu.edu/blog/2016/12/22/Context-specific-org-mode-speed-keys/
).

If there was a change to org to enable this, I wouldn't expect the core to
change behavior for anyone, it would just make it possible for users to
change this if they wanted to. The same way they can customize the face of
a code block for different languages.



John

---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu


On Wed, Jun 7, 2017 at 7:21 AM, Nicolas Goaziou 
wrote:

> Hello,
>
> John Kitchin  writes:
>
> > For once in a while uses this works, but this isn't really a solution
> > for key-bindings that are composable, e.g. in lispy. There you can use
> > single key-presses to navigate, rearrange, insert code, etc...
> >
> > Also it adds three chords to every key-binding out of the box, it would
> > be fewer keys to just go to special edit mode unless you make a simpler
> > key definition!
>
> Sure, but I have the feeling that it isn't Org job to allow keybindings
> for multiple major modes in the same buffer. Note that we already did
> this with links, but I think that specific part of link revamp may have
> gone too far.
>
> Also, it could be troublesome because some interactive functions may
> depend on a mode specific variables, which are not initialized while in
> Org mode.
>
> As far as Org is concerned, C-c ', i.e., `org-edit-special' is the way
> to go, IMO.
>
> WDYT?
>
> Regards,
>
> --
> Nicolas Goaziou0x80A93738
>

Re: [O] Custom keymaps on org blocks

[Nicolas Goaziou]

Hello,

John Kitchin  writes:

> For once in a while uses this works, but this isn't really a solution
> for key-bindings that are composable, e.g. in lispy. There you can use
> single key-presses to navigate, rearrange, insert code, etc...
>
> Also it adds three chords to every key-binding out of the box, it would
> be fewer keys to just go to special edit mode unless you make a simpler
> key definition!

Sure, but I have the feeling that it isn't Org job to allow keybindings
for multiple major modes in the same buffer. Note that we already did
this with links, but I think that specific part of link revamp may have
gone too far.

Also, it could be troublesome because some interactive functions may
depend on a mode specific variables, which are not initialized while in
Org mode.

As far as Org is concerned, C-c ', i.e., `org-edit-special' is the way
to go, IMO.

WDYT?

Regards,

-- 
Nicolas Goaziou0x80A93738

Re: [O] Custom keymaps on org blocks

[John Kitchin]

Nicolas Goaziou writes:

> Hello,
>
> John Kitchin  writes:
>
>> Is there any interest in having custom keymaps on org blocks?
>>
>> The idea I had is to have the option to make the major-mode keymaps be
>> active on the src blocks.
>
> There is already `org-babel-do-key-sequence-in-edit-buffer', i.e., C-c
> C-v C-x.

For once in a while uses this works, but this isn't really a solution
for key-bindings that are composable, e.g. in lispy. There you can use
single key-presses to navigate, rearrange, insert code, etc...

Also it adds three chords to every key-binding out of the box, it would
be fewer keys to just go to special edit mode unless you make a simpler
key definition!

>
> Regards,


--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu

Re: [O] Custom keymaps on org blocks

[John Kitchin]

Grant Rettke writes:

> On Mon, Jun 5, 2017 at 4:53 PM, John Kitchin  wrote:
>> Is there any interest in having custom keymaps on org blocks?
>>
>> The idea I had is to have the option to make the major-mode keymaps be
>> active on the src blocks.
>
> You want Polymode: https://github.com/vspinu/polymode

I have never been able to get polymode to work. Do have an incantation
that works?

>
>> I have tried this, and seems ok, and I wondered if anyone had an opinion
>> for or against this idea.
>
> It is confusing alternating between the Org major a mode and the
> source block major mode as you scroll through documents. One second
> you are an author for humans and the other an author for the computer.
> That is how literate programming is defined in theory, but in practice
> I don't do it like that because it is mentally jarring.

Interesting perspective. I find switching to special edit mode jarring,
particularly when it is just for the key bindings, e.g. lispy mode, or
getting python indentation to work.

>
> I spell check my Org-Mode Literate Documents. But the spell checker
> does not check source blocks. That is up to the major mode for that
> source block, not for the containing literate document. When you think
> about it, probably every Org-Mode literate programming has it set up
> this way, otherwise the spell checker would go crazy on typical source
> code. That is revealing. The source blocks are very different "things"
> than the containing document.
>
> For me the source block is another cognitive workspace that I enter
> consciously. I am digging deeper into the document itself. For me the
> source block is a window into that world of the source block. In the
> top level document I write literature about things, including the
> various source blocks. Then I jump into editing the source block
> itself.
>
> John you once had a discussion (or answered a (my?) question) about
> making source blocks not-editable. That is how I would like it to work
> all the time. That is why I don't fontify source blocks natively and
> that is why I wouldn't enjoy what you describe.

That is ok, the hack I made is totally optional. If you don't define an
alternative map for a block, it just gets the orgmode map. You can even
just locally redefine a few key bindings on the org-mode map that are
only valid in the block.


--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu

[O] insert cell inside an org-mode table?

[Sharon Kimble]

I maintain my 'DrugFacts' website in mediawiki. I write my article in
org-mode, export to mediawiki, correct the citations, then cut and paste
into my mediawiki page. And it all works very well.

But the front-page is a right swine! Here is the first two rows of my mediawiki 
front-page -

--8<---cut here---start->8---
{| 
| '''Illegal'''
| '''Category's'''
| '''Legal'''
| '''Prescription only'''
| '''Substitute'''
| '''Others'''
|-
|* [[Amphetamines]]
|* [[:Category:Anaesthetics|Anaesthetics]]
|* [[Alcohol]]
|* [[Alprazolam]]
|* [[Buprenorphine]]
|* [[Flumazenil]]
|-
--8<---cut here---end--->8---

And because writing mediawiki tables leads to brain damage, and a desire
to consume 6 pints of beer as the world is going to end in ten minutes,
according to Douglas Adams and Ford Prefect, I'm intending to create the
table in org-mode and then export to mediawiki, correct as necessary,
and upload. Which brings me to my question.

Is it possible to insert a cell *inside* an org-mode table please, and
auto-shuffle other rows/columns about to fit? According to the 'Table'
menu in emacs, there isn't a way of doing it, and neither does the
org-mode manual say that it can be done. But perhaps other people have
found a way of doing it please?

Hopefully thanks
Sharon.
-- 
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
DrugFacts = https://www.drugfacts.org.uk  
Debian 9.0, fluxbox 1.3.5-2, emacs 25.1.1, org-mode 9.0.7


signature.asc
Description: PGP signature

Re: [O] Bug: Beamer example (info node 12.8.6) fails to compile [9.0.7 (9.0.7-elpa @ /Users/gtomas/.emacs.d/elpa/org-20170515/)]

[Nicolas Goaziou]

Hello,

Gil Tomás  writes:

> When copying the example provided in org-mode info node 12.8.6 to an org
> buffer, and then seeking to compile it into a pdf with the beamer
> exporter (C-c C-e l O), the following error message is printed into the
> minibuffer:
>
> apply: Wrong type argument: listp, #("Carsten Dominik" 0 15 (:parent
> (#0)))

This is a commonly reported error message. I guess it should go into the
FAQ. It means you have a mixed installation. You need to re-install Org
properly.

Regards,

-- 
Nicolas Goaziou

Re: [O] Moving and resetting attachments

[Florian Lindner]

Am 02.06.2017 um 11:19 schrieb Eric Abrahamsen:> Florian Lindner 
 writes:
>
>> Am 01.06.2017 um 06:39 schrieb Eric Abrahamsen:
>>> Florian Lindner  writes:
>>>
 Hello,

 two questions about moving attachments to org files:

 C-c C-a a attaches a file and stores it under ./data/ID/...

 Using C-c C-a s I can set another directory a attachment directory.
 Can I make org-mode move the content of the previous
 directory to the new directory?

 Can I "reset" the attachment directory, i.e. like C-c C-a s but
 :ATTACH_DIR: is deleted and the contents of the previous
 directory are moved to ./data/ID?
>
>> I hacked together some lines of lisp that should achieve that. It's my first 
>> non-trivial (from my point of trivialness)
>> piece of code. I'm open for any suggestions:
>>
[...]
>
> Looks like a good start! My first comment is, this should definitely be
> written as a patch to `org-attach-set-directory'. It's useful
> functionality, and fits well into the whole system -- so long as you
> give users a chance to say no, I don't see why it shouldn't be part of
> the library.
>
> Various comments:
>
> 1. Use the prefix arg to differentiate between setting and unsetting a
>directory. Ie, no prefix arg means set (and an empty string for
>directory name aborts),
>prefix arg means unset. The `org-attach' dispatch mechanism will pass
>the prefix arg through to this function.
> 2. Definitely use `read-directory-name'!
> 3. This is a good use of `copy-directory' with the COPY-CONTENTS flag,
>but I'd still recommend using `directory-files' and then looping over
>all the files with a `map-y-or-n-p'. That will give users a chance to
>selectively choose files to move. This is a matter of taste. If you
>stick with `copy-directory', at least ask the user first.
> 4. I think you're right not to delete the directory afterwards. Best not
>to assume too much.
> 5. The "else" branch of an `if' statement has an implicit `progn', you
>don't need to add it.
> 6. Convention is to not put closing parentheses on their own line. Just
>pile them up at the end of the last form.
> 7. Personally I'd rework things so you only call `org-attach-dir' once.
>How to handle this depends a bit on when when-let was introduced into
>Emacs, and whether Org is okay to support it. Probably safest to use
>when-let*. so:
>
> (when-let* ((attach-dir (org-attach-dir))
> (target (read-directory-name "Move attachments to: ")))
>
> That way everything will bail if there's no attach dir.

Ok, my new version is here. It should be able to replace 
org-attach-set-directory

(defun flo/org-attach-move (prefix)
  "If PREFIX arg, reset attach directory, else set target directory."
  (interactive "p") ; Correct check for boolean prefix?

  (let ((old-attach-dir (org-attach-dir))
(new-attach-dir (if (eq prefix 1)
(let ((dir (org-entry-get nil "ATTACH_DIR")))
  (setq dir (read-directory-name "Attachment 
directory: " dir))
  (org-entry-put nil "ATTACH_DIR" dir)
  (org-attach-dir t)) ; Changes semantics
  (org-entry-delete nil "ATTACH_DIR")
  (org-attach-dir t

(message "old-attach-dir = %s" old-attach-dir)
(message "new-attach-dir = %s" new-attach-dir)
(unless (or (string= old-attach-dir new-attach-dir)
(not old-attach-dir))
  (when (y-or-n-p "Copy over attachments from old directory? ")
(copy-directory old-attach-dir new-attach-dir t nil t))
  (when (y-or-n-p (concat "Delete " old-attach-dir))
(shell-command (format "rm -fr %s" old-attach-dir))


Some questions about the code

* Is that the correct way to deal with a boolean prefix arg? I'm not interested 
in the value of the prefix arg, only if
it's given or not.

* The code changes the semantics of org-attach-set-directory, because it 
creates the newly set attach dir. IMHO this
makes more sense.

* It deletes only the first part of the dir, e.g. data/83/1234567, it only 
deletes the 1234567 dir, even if 83 is empty
afterwards. But I think that's ok.

> 1. Use the prefix arg to differentiate between setting and unsetting a
>directory. Ie, no prefix arg means set (and an empty string for
>directory name aborts),
>prefix arg means unset. The `org-attach' dispatch mechanism will pass
>the prefix arg through to this function.

Tried to take that into account.

> 3. This is a good use of `copy-directory' with the COPY-CONTENTS flag,
>but I'd still recommend using `directory-files' and then looping over
>all the files with a `map-y-or-n-p'. That will give users a chance to
>selectively choose files to move. This is a matter of taste. If you
>stick with `copy-directory', at least ask the user first.
> 

[O] Exporting to html and opening external browser doesn't work

[Miriam Mayer]

Emacs-version: 25.2.1 (x86_64-unknown-linux-gnu (I'm using Arch Linux) GTK+ version 3.22.10) as of 2017-04-22

Org-mode-version: 8.2.10

 

I created a file with C-x C-f and named it 'test.org' to get into org-mode.

Exporting to html and opening in a browser via C-c C-e h o doesn't work. The standard browser isn't opened. The html code is however exported into another buffer within emacs.

[O] Bug: Beamer example (info node 12.8.6) fails to compile [9.0.7 (9.0.7-elpa @ /Users/gtomas/.emacs.d/elpa/org-20170515/)]

[Gil Tomás]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 http://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org mailing list.


When copying the example provided in org-mode info node 12.8.6 to an org
buffer, and then seeking to compile it into a pdf with the beamer
exporter (C-c C-e l O), the following error message is printed into the
minibuffer:

apply: Wrong type argument: listp, #("Carsten Dominik" 0 15 (:parent (#0)))

Emacs  : GNU Emacs 25.1.1 (x86_64-apple-darwin16.4.0, NS appkit-1504.81
Version 10.12.3 (Build 16D32))
 of 2017-03-22
Package: Org mode version 9.0.7 (9.0.7-elpa @
/Users/gtomas/.emacs.d/elpa/org-20170515/)

current state:
==
(setq
 org-hide-leading-stars t
 org-export-babel-evaluate nil
 org-tab-first-hook '(org-babel-hide-result-toggle-maybe
org-babel-header-arg-expand)
 org-shiftleft-final-hook '(windmove-left)
 org-latex-classes '(("beamer" "\\documentclass[presentation]{beamer}"
  ("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
  ("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
 ("article" "\\documentclass[11pt]{article}"
("\\section{%s}" . "\\section*{%s}")
  ("\\subsection{%s}" . "\\subsection*{%s}")
  ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
  ("\\paragraph{%s}" . "\\paragraph*{%s}")
  ("\\subparagraph{%s}" . "\\subparagraph*{%s}"))
 ("report" "\\documentclass[11pt]{report}"
("\\part{%s}" . "\\part*{%s}")
  ("\\chapter{%s}" . "\\chapter*{%s}") ("\\section{%s}"
. "\\section*{%s}")
  ("\\subsection{%s}" . "\\subsection*{%s}")
  ("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
 ("book" "\\documentclass[11pt]{book}" ("\\part{%s}" .
"\\part*{%s}")
  ("\\chapter{%s}" . "\\chapter*{%s}") ("\\section{%s}"
. "\\section*{%s}")
  ("\\subsection{%s}" . "\\subsection*{%s}")
  ("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
 )
 org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
 org-occur-hook '(org-first-headline-recenter)
 org-src-tab-acts-natively t
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-html-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"]
 org-log-done 'time
 org-src-window-setup 'current-window
 org-latex-format-inlinetask-function
'org-latex-format-inlinetask-default-function
 org-confirm-shell-link-function 'yes-or-no-p
 org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
 org-special-ctrl-a/e t
 org-agenda-skip-scheduled-if-done t
 org-support-shift-select t
 org-latex-format-headline-function
'org-latex-format-headline-default-function
 org-default-notes-file "~/Dropbox/org/gtb.org"
 org-todo-keyword-faces '(("TODO" :background "tomato" :foreground "bisque"
:weight bold)
  ("STARTED" :background "ForestGreen" :foreground
"bisque" :weight bold)
  ("WAITING" :background "DarkOrange" :foreground
"bisque" :weight bold)
  ("DONE" :background "RoyalBlue" :foreground
"bisque" :weight bold)
  ("CANCELLED" :background "grey50" :foreground
"bisque" :weight bold))
 org-startup-indented t
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-latex-format-drawer-function #[514 "\207" [] 3 "\n\n(fn _ CONTENTS)"]
 org-odt-format-headline-function 'org-odt-format-headline-default-function
 org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
 org-tags-column -66
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-babel-pre-tangle-hook '(save-buffer)
 org-mode-hook '(my-org-mode-hook (lambda nil (org-bullets-mode 1))
turn-on-org-cdlatex flyspell-mode
 company-mode rainbow-delimiters-mode smartparens-mode
er/add-org-mode-expansions
 #[0 "\300\301\302\303\304$\207"
   [add-hook change-major-mode-hook org-show-block-all
append local] 5]
 #[0 "\300\301\302\303\304$\207"
   [add-hook change-major-mode-hook
org-babel-show-result-all append local] 5]
 org-babel-result-hide-spec org-babel-hide-all-hashes
zotelo-minor-mode
 #[nil "\300\301!\207" [run-hooks prelude-org-mode-hook] 2])
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-use-speed-commands t
 org-ascii-format-drawer-function #[771 " \207" [] 4 "\n\n(fn NAME CONTENTS
WIDTH)"]
 org-odt-format-inlinetask-function
'org-odt-format-inlinetask-default-function
 org-cycle-hook '(org-cycle-hide-archived-subtrees