Re: [O] Properties lost when closing, scheduling, etc.

[Eric S Fraga]

On Tuesday, 10 Oct 2017 at 22:01, John Goerzen wrote:
> I cannot make it misbehave with either SCHEDULED or CLOSED in my testing
> now.

Maybe try org-lint to see if there are more subtle errors in your
file(s)?

-- 
: Eric S Fraga via Emacs 27.0.50, Org release_9.1.2-98-g0b8316


signature.asc
Description: PGP signature

Re: [O] Properties lost when closing, scheduling, etc.

[John Goerzen]

On 10/10/2017 08:42 PM, Richard Lawrence wrote:
> Hi John,
>
> John Goerzen  writes:
>
>> Unfortunately, org-mode only recognizes the PROPERTIES when they
>> occur immediately after the headline.  So whenever I take an action
>> on an item like this, the properties become invisible to org-mode.   
>
> What version of Org are you running?  This sounds like old behavior
> (or maybe a problematic mix of new and old behavior). PROPERTIES
> drawer syntax changed (incompatibly) in 8.3; see
> http://orgmode.org/Changes_old.html.
Hi Richard,

Thanks for the reply!  I have 9.0.3.  (Bit embarrassed I omitted that
detail, sigh.)

So the documentation says PROPERTIES can be after a "planning line",
shich seems to be DEADLINE: or SCHEDULED: but not necessarily CLOSED:.

I attempted to validate this, both by evaulating (org-id-get) on the
spot and by using C-c l (which was what caused the problem to begin
with; it added a second PROPERTIES block, as I have
org-id-link-to-org-use-id set to 'create-if-interactive).  Now somehow I
cannot duplicate the problem.  So I don't know what the heck happened --
I know it DID happen -- but it's possible this is a PEBKAC issue anyhow.

I cannot make it misbehave with either SCHEDULED or CLOSED in my testing
now.

- John

>
> If you are running an older version, may want to try upgrading and
> then running the org-repair-property-drawers function defined on that
> page.
> Hope that helps!
>
> Best,
> Richard

Re: [O] Properties lost when closing, scheduling, etc.

[Richard Lawrence]

Hi John,

John Goerzen  writes:

Unfortunately, org-mode only recognizes the PROPERTIES when they 
occur immediately after the headline.  So whenever I take an 
action on an item like this, the properties become invisible to 
org-mode.   


What version of Org are you running?  This sounds like old 
behavior (or maybe a problematic mix of new and old behavior). 
PROPERTIES drawer syntax changed (incompatibly) in 8.3; see 
http://orgmode.org/Changes_old.html.


If you are running an older version, may want to try upgrading and 
then running the org-repair-property-drawers function defined on 
that page. 


Hope that helps!

Best,
Richard

Re: [O] Recent regression in Org master with parsing of verbatim code with spaces

[Reuben Thomas]

On 10 October 2017 at 18:29, Kaushal Modi  wrote:

> On Tue, Oct 10, 2017 at 1:08 PM Kaushal Modi 
> wrote:
>
>> I scanned through recent commits, but haven't yet figured out which
>> commit affected this. Before I end up with git bisect, does anyone know a
>> master branch commit that could have caused this?
>>
>
> Hello,
>
> I found the commit causing this change:
>
> http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=
> 8383f7e08b964e129b175ef1c0297b1f4a8ed235
>

​I haven't seen the rest of this thread, but at a guess is the problem to
do with [:space:] matching vertical space such as newline and vertical tab?
Fixing that is a bit painful, since as far as I know there's no regex for
"horizontal space"; I guess it would be a matter of enumerating a suitable
range of code points.​

-- 
https://rrt.sc3d.org

Re: [O] Clocktable Naming

[Shawn Way]

I found out that :step day trips this up.  No worries.

Shawn Way, PE

-Original Message-
From: Nicolas Goaziou [mailto:m...@nicolasgoaziou.fr] 
Sent: Tuesday, October 10, 2017 2:18 AM
To: Shawn Way 
Cc: emacs-orgmode@gnu.org
Subject: Re: Clocktable Naming

Hello,

Shawn Way  writes:

> Is there a method for automatically naming a timeclock?  For example,
>
> :name table1
>
> to be used in the #+BEGIN line?

There is a way, albeit no very user-friendly. You can use :header parameter, 
e.g.,

  #+begin: clocktable :header "#+name: foo\n#+caption: bar\n"


Regards,

--
Nicolas Goaziou

Re: [O] Recent regression in Org master with parsing of verbatim code with spaces

[Kaushal Modi]

On Tue, Oct 10, 2017 at 2:31 PM Eric S Fraga  wrote:

> Anecdotally, I am seeing some strange fontifications in some of my org
> files where my headline *s are being interpreted as starting a bold
> text.
>

I have seen that too, though I thought that was because I was setting the
NEWLINE component in the org-regexp-emphasis component to a value greater
than the default of 1. It's on my list to get back to debugging that.
-- 

Kaushal Modi

Re: [O] Recent regression in Org master with parsing of verbatim code with spaces

[Eric S Fraga]

Anecdotally, I am seeing some strange fontifications in some of my org
files where my headline *s are being interpreted as starting a bold
text.  I've not been able to create a small example yet but thought I
would mention it in case it helps.

-- 
: Eric S Fraga via Emacs 27.0.50, Org release_9.1.2-98-g0b8316


signature.asc
Description: PGP signature

Re: [O] Recent regression in Org master with parsing of verbatim code with spaces

[Kaushal Modi]

On Tue, Oct 10, 2017 at 1:08 PM Kaushal Modi  wrote:

> I scanned through recent commits, but haven't yet figured out which commit
> affected this. Before I end up with git bisect, does anyone know a master
> branch commit that could have caused this?
>

Hello,

I found the commit causing this change:

http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=8383f7e08b964e129b175ef1c0297b1f4a8ed235
-- 

Kaushal Modi

[O] Recent regression in Org master with parsing of verbatim code with spaces

[Kaushal Modi]

Hello,

I just noticed a regression in master when compared to 9.1.2.

MWE:

=
=title = "foo"​=

~title = "foo"​~
=

On master:

C-c C-e t A outputs (ignoring, author, title, toc, etc):

=
=title = "foo"​=

~title = "foo"​~
=

Also the above text does NOT get fontified as verbatim in the Org buffer.

On 9.1.2 (that's on emacs-26 branch):

C-c C-e t A outputs (ignoring, author, title, toc, etc):

=
`title = "foo"​'

`title = "foo"​'
=

Also the above text DOES get fontified as verbatim in the Org buffer.

I scanned through recent commits, but haven't yet figured out which commit
affected this. Before I end up with git bisect, does anyone know a master
branch commit that could have caused this?
-- 

Kaushal Modi

[O] Properties lost when closing, scheduling, etc.

[John Goerzen]

So I have a lot of cases where there is a :PROPERTIES: drawer.  It
contains, crucially, an ID (I use those for linking).  When I close a
task with C-c C-t and pick DONE, or when I schedule it with C-c C-s, it
will insert CLOSED: or SCHEDULED: lines ABOVE the :PROPERTIES: line.

Unfortunately, org-mode only recognizes the PROPERTIES when they occur
immediately after the headline.  So whenever I take an action on an item
like this, the properties become invisible to org-mode.  I can always
restore it by reordering the text.

How do I address this?

Thanks,

John

Re: [O] Clocktable Naming

[Dave Marquardt]

I wanted to add a #+PLOT to the clock table header, and used the
advice mechanism to do it. E.g.

(defadvice org-clock-report (after insert-plot-line
   activate)
  "Add #+PLOT: line appropriate for clock table."
  (insert 
   "#+PLOT: ind:1 deps:(4) type:2d with:histograms set:\"style fill solid\"
"))

You might be able to do something similar for your purpose.

You might also check to see if there's some sort of hook to use when
inserting clock tables.

---
On Mon, Oct 09 2017, Shawn Way wrote:

Is there a method for automatically naming a timeclock?  For example,

:name table1

to be used in the #+BEGIN line?

This would allow the clocktable to be post processed using something like perl 
or python for in depth analysis.

SHAWN WAY, P.E.

Re: [O] S5 HTML export - org9.1.1

[Rick Frankel]

As the orginal author -- who hasn't looked @ or used ox-s5 in years ;O, just
confirming the patch looks correct to me. I don't think i have commit
privilges anymore (lost that ssh key), so i appreciate your applying it.

thanks,
rick

On Sat, Oct 07, 2017 at 06:51:05PM +, Kyle Meyer wrote:
> dchechi...@gmail.com writes:
> > I have evaluated the following function found in ox-html.el
> > and indeed the S5 html works when this function is defined.
> >
> > (defun org-html-end-plain-list (type)
> >   "Insert the end of the HTML list depending on TYPE."
> >   (case type
> > (`ordered "")
> > (`unordered "")
> > (`descriptive "")))
> 
> Yes, that's the function that was removed in 8855c23c6.
> 
> > I don't know if this function should appear accordly in
> > ox-S5.el or elsewhere. As I don't use development environment
> > I don't know how a patch has to be submitted.
> >
> > Anyway thank for your help. Hope it can be useful for the
> > person who knows how to implement it and where.
> 
> I don't use ox-s5.el, but the I think the below fix should do.  I'll
> push it in a few days if no one objects.
> 
> -- >8 --
> Subject: [PATCH] ox-s5: Don't use org-html-end-plain-list
> 
> * contrib/lisp/ox-s5.el (org-s5-plain-list): Adjust for the removal of
> org-html-end-plain-list.
> 
> The function org-html-end-plain-list was deleted in
> 8855c23c6 (ox-html: Plain list supports arbitrary attributes,
> 2017-02-13).
> 
> Reported-by: 
> 
> ---
>  contrib/lisp/ox-s5.el | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/contrib/lisp/ox-s5.el b/contrib/lisp/ox-s5.el
> index 8f9501058..0496aae19 100644
> --- a/contrib/lisp/ox-s5.el
> +++ b/contrib/lisp/ox-s5.el
> @@ -292,7 +292,8 @@ (defun org-s5-plain-list (plain-list contents info)
>   "<%s class='org-%s%s'>" tag tag
>   (if (org-export-get-node-property :INCREMENTAL plain-list t)
>   " incremental" ""))
> -contents (org-html-end-plain-list type
> +contents
> + (format "" tag
>  
>  (defun org-s5-inner-template (contents info)
>"Return body of document string after HTML conversion.

[O] TODO keywords are not being exported by the markdown exporter

[Ganesh Krishnan]

TODO status is not being exported by the markdown exporter. I first noticed
this when I contacted the package author for the ox-gfm exporter regarding
missing TODO keywords in my exported documents. He responded saying that
this is an upstream problem with the org-mode markdown exporter. I don't
know what the formal mechanism for filing a bug is, but wanted to report
the bug.

Thanks,
Ganesh

[O] Bug: org-encrypt-entry fails [9.1.2 (9.1.2-elpa @ /Users/dmm/.emacs.d/elpa/org-20171004/)]

[David Maslen]

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.


Hello,

I've used org-encrypt in the past, but with emacs25.3 on macos and the latest
melpa package it's no longer working.

The EPA package commands work, so I believe I have gpg configured
correctly.

For example;
m-x epa-encrypt-region using a password of 'test' works on the following;
-BEGIN PGP MESSAGE-

jA0EBwMCYfMM8STtN1Pe0jkBvSH5XRx9n0cvZXiPz7XpDA/1FUSypQ+y/TBwqjok
ZuzP/aNr8kS2+Aap09sxfurwASK7jNuDQEU=
=Gd3s
-END PGP MESSAGE-

However selecting an org heading such as;

* Test encryption :crypt:
test this

Then running 'm-x org-encrypt-entry' fails.

My intent is to use a symetric password, as I can with epa.




Emacs  : GNU Emacs 25.3.1 (x86_64-apple-darwin16.7.0, NS appkit-1504.83 Version 
10.12.6 (Build 16G29))
 of 2017-09-28
Package: Org mode version 9.1.2 (9.1.2-elpa @ 
/Users/dmm/.emacs.d/elpa/org-20171004/)

current state:
==
(setq
 org-journal-file-format "%Y%m%d.org"
 org-journal-mode-hook '(#[nil "\301\302\303\304$\207"
   [org-journal-encrypt-on org-add-hook
org-journal-encryption-hook nil t]
   5]
 (lambda nil
  (org-add-hook org-journal-encrypt-on
   (quote org-journal-encryption-hook) nil t)
  )
 )
 org-tab-first-hook '(org-babel-hide-result-toggle-maybe 
org-babel-header-arg-expand)
 org-speed-command-hook '(org-speed-command-activate 
org-babel-speed-command-activate)
 org-download-screenshot-method "screencapture -i %s"
 org-trello-mode-on-hook '(orgtrello-controller-mode-on-hook-fn
   #[nil
 "\304\305\300!\203.\202\f.   
!\210\306\n\307\310#\210\306\n\311\312#\210\306\n\313\314#\210\306\n\315\316#\210\317\320!\"\207"
 [org-trello-current-prefix-keybinding
  
  org-trello-default-prefix-keybinding
  
  org-trello-mode-map
  
  orgtrello-log-no-log
  
  
orgtrello-setup-install-local-prefix-mode-keybinding
  
  boundp
  
  define-key
  
  [remap org-end-of-line]
  
  orgtrello-buffer-end-of-line
  
  [remap org-return]
  
  orgtrello-buffer-org-return
  
  [remap org-ctrl-c-ret]
  
  orgtrello-buffer-org-ctrl-c-ret
  
  [remap org-archive-subtree]
  
  org-trello-archive-card orgtrello-log-msg 
orgtrello-setup-startup-message]
 4]
   )
 org-download-method 'attach
 org-occur-hook '(org-first-headline-recenter)
 org-trello-mode-off-hook '(orgtrello-controller-mode-off-hook-fn
#[nil
  "\304\305\300!\203.\202\f.  
!\210\306\n\307\310#\210\306\n\311\310#\210\306\n\312\310#\210\306\n\313\310#\210\314\315\"\207"
  [org-trello-current-prefix-keybinding
   
   org-trello-default-prefix-keybinding
   
   org-trello-mode-map
   
   orgtrello-log-no-log
   
   
orgtrello-setup-remove-local-prefix-mode-keybinding
   
   boundp
   
   define-key
   
   [remap org-end-of-line]
   
   nil
   
   [remap org-return]
   
   [remap org-ctrl-c-ret]
   
   [remap org-archive-subtree]
 

Re: [O] Is it possible for a TODO item not to be an outline item?

[Florian Beck]

On 08.10.2017 13:40, Angel de Vicente wrote:

So basically I would like to have that TODO item but somehow without
creating a new section. Is it possible?


Use

---
bla bla bla
# TODO: fix installation
bla bla bla
---

and

M-x org-occur-in-agenda-files (which is bound to C-a /).


Florian

Re: [O] org-toggle-latex-fragment

[Eric S Fraga]

On Monday,  9 Oct 2017 at 19:07, Joseph Vidal-Rosset wrote:
> I have to work on my configuration to solve this problem, and your emails
> put me on the right way. Many thanks !

You're welcome.  I'm glad I could help, even if only indirectly!

-- 
: Eric S Fraga via Emacs 27.0.50, Org release_9.1.1-78-gfbf47c


signature.asc
Description: PGP signature

Re: [O] Edit whole session with org-edit-src-edit

[Nicolas Goaziou]

Hello,

"Yury G. Kudryashov"  writes:

> I propose the following feature:
>
> 1. When the temporary buffer is created,
>
>- the whole session (or all the code with that will go to one file
>  when tangling) is written to the buffer;
>- all the code except for the current block is marked as read-only.
>
> 2. When writing the temporary buffer back to the main file, drop the
>  read-only regions.

This is an interesting idea. However that could slow down src block
editing so it would need to be explicitly required by the user (e.g.,
with an optional argument).

Also, it should be necessary to mark somehow the read-only parts or it
could be confusing. Maybe with some glyph in the margin.

> Unfortunately, I'm new to (e)lisp, so I'm not sure whether I'll manage
> to implement these features myself.

You can only know if you try. You will find help on this mailing list
whenever you hit a road block.

Regards,

-- 
Nicolas Goaziou

Re: [O] Clocktable Naming

[Nicolas Goaziou]

Hello,

Shawn Way  writes:

> Is there a method for automatically naming a timeclock?  For example,
>
> :name table1
>
> to be used in the #+BEGIN line?

There is a way, albeit no very user-friendly. You can use :header
parameter, e.g.,

  #+begin: clocktable :header "#+name: foo\n#+caption: bar\n"


Regards,

-- 
Nicolas Goaziou

Re: [O] Fontification for the inner bloc of two nested bloc

[Nicolas Goaziou]

Hello,

Pierre-André Cornillon  writes:

> Dear orgmode users/gurus,
>
> I have a question about fontification of inner src bloc.
>
> I have two nested blocks: one special (outer bloc) and one src (inner
> bloc) like this
>
> #+begin_bloc20171001122500
> #+begin_src R
>   blip <- runif(2)
>   test <- rnorm(2)
> #+end_src
>
> #+end_bloc20171001122500
>
> and I want to have the native fontification property for the inner one.
>
> I have already (setq org-src-fontify-natively t) in my .emacs and it
> works like a charm for src blocks alone (not nested) but for nested
> ones it breaks.
>
> Is nested blocks are allowed and if so, is that possible to have that
> fontification property ?

Nested blocks are allowed, but the fontification system has a few
shortcomings, including this one. Ultimately, this part of Org needs to
be rewritten using the parser.

Anyway The bug probably lies in `org-fontify-meta-lines-and-blocks-1'.
Do you want to investigate?

Regards,

-- 
Nicolas Goaziou

Re: [O] org-open-at-point fails on internal links

[Scott Otterson]

This morning, I updated my packages (Options -> Manage Emacs Packages -> U
->X) and now, internal links work perfectly.

For the record, the updated packages were:

dash-20171009.105
flycheck-20171009-1145
helm-20171009.221
kaolin-theme-20171009.1130
org-20171009
org-plus-contrib-20171009
org-ref-20171009.2019
python mode-20171005.1620


I'll let you know if the error returns.

Scott




On Mon, Oct 9, 2017 at 8:38 PM, Kyle Meyer  wrote:

> [Forwarding because the list was dropped earlier in the thread but I
>  didn't notice.  Scott, please don't drop the list in your replies.]
>
>
>
> -- Forwarded message --
> From: Kyle Meyer 
> To: Scott Otterson , Nicolas Goaziou <
> m...@nicolasgoaziou.fr>
> Cc:
> Bcc:
> Date: Mon, 09 Oct 2017 14:32:00 -0400
> Subject: Re: org-open-at-point fails on internal links
> Scott Otterson  writes:
>
> >   org-backward-paragraph()
> >   org-inside-LaTeX-fragment-p()
> >   org-footnote-in-valid-context-p()
> >   org-footnote-at-reference-p()
> >   ad-Advice-org-open-at-point
>
> [...]
>
> > org-mouse.el  (line 907) adds code to org-mode-hook, and that code adds
> > advice to org-open-at-point, and that advice calls
> > org-footnote-at-reference-p
>
> Thanks for digging further.  Indeed org-mouse.el's advice would result
> in the org-footnote-at-reference-p path being executed.
>
> After loading org-mouse and using your example, I'm still not able to
> trigger the error.  Could you debug org-backward-paragraph to find out
> where the error is occurring?  You can do that by calling C-u C-M-x on
> org-backward-paragraph or by evaluating
>
> (edebug-instrument-function 'org-backward-paragraph)
>
> --
> Kyle
>
>