Re: [O] [BUG] Radio Targets and double quotes

2015-05-28 Thread thomas

Hi Nicolas,

I have Org-mode version 8.2.10 (8.2.10-40-gc763fa-elpa @ 
/home/thomas/.emacs.d/elpa/org-20150504/)


org-export-with-smart-quotes is set to t.

The error goes away when org-export-with-smart-quotes is not true.

M-x org-reload (sorry, I do not know how C-u org-reload could work) 
reveals:


[type q key info org-export-smart-quotes-alist encoding eql apostrophe 
open "'" ...] 6], 1


Thank you.

Thomas




On 29.05.2015 01:08, Nicolas Goaziou wrote:

Hello

thomas  writes:


a radio target reference followed by another radio target in double
quotes breaks html-export.
The following minimal throws an error:

===

Keyword1 "keyword2"

<<>>

<<>>

===

Error Message:

org-export-activate-smart-quotes: Wrong number of arguments: #[(q
type) "ÆÇ\"ƒ

I cannot reproduce it. What Org version are you using?


(after that comes a number of weird symbols that I cannot even copy
into the email...)

You should use Org uncompiled (C-u org-reload) to get a better backtrace.

Regards,

--
Nicolas Goaziou





Re: [O] Recently emacs hangs on startup due to ESS

2015-05-28 Thread Cook, Malcolm
John, 

Glad you're "cooking with ESS".  Gonna hafta chalk your WTF moment up to some 
butterfly in Kamchatka.  Or was it Saskatchewan? 

BTW, since you said you use org-mode, please note, when you get next perform a 
fresh install of org-mode, regardless of the  means (package manager, git pull, 
stork brought it, whatevs), make sure  it is compiled, and in a fresh boot of 
emacs unsullied by current (and soon to be ancien regime) org-mode.  In other 
words, run  `emacs -Q` as you do, and install the new org WITHOUT  LOADING THE 
EXISTING ORG.You have been warned!

~ malcolm_c...@stowers.org


From: John Hendy 
Sent: Thursday, May 28, 2015 11:15 PM
To: Cook, Malcolm
Cc: emacs-orgmode
Subject: Re: [O] Recently emacs hangs on startup due to ESS

On Thu, May 28, 2015 at 6:34 PM, Cook, Malcolm  wrote:
> John, still recommend you try fresh ess, compiled via package manager.  Also, 
> update any packages needing updated.  Maybe speedbar?

So, I followed your nice ELPA instructions, and things worked. Then I
wondered if it was compilation related, so I did that in my manually
downloaded ESS dir and re-enabled my default load path (instead of
ELPA), and no emacs hang. Then I run make clean, no hang. Then I do
the emacs -Q method in my original email... hang. Then make again, no
hang. Then make clean. No hang.

I also played with ess-speedbar-use-p in case it's an issue with that,
but at this point I feel like I can't reproducibly cause it to hang
anymore so I don't know what in the world is going on.

Definite wtf moment for me!


Thanks for all of your input/suggestions!
John

>
> I'm dry,
>
> Best,
>
> Malcolm
>
>> -Original Message-
>> From: John Hendy [mailto:jw.he...@gmail.com]
>> Sent: Thursday, May 28, 2015 6:24 PM
>> To: Cook, Malcolm
>> Cc: emacs-orgmode
>> Subject: Re: [O] Recently emacs hangs on startup due to ESS
>>
>> On Thu, May 28, 2015 at 5:38 PM, Cook, Malcolm 
>> wrote:
>> >> On Thu, May 28, 2015 at 5:07 PM, Cook, Malcolm 
>> >> wrote:
>> >> > I would install latest ess fresh.
>> >>
>> >> I wondered about that as well, so I tried that prior to posting here.
>> >> Sorry, I should have listed my version, which is now 15.03-1.
>> >>
>> >> > What version of emacs?  The package manager is a moving target
>> >> > these
>> >> days.
>> >>
>> >> GNU Emacs 24.5.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.16.2)
>> >> (installed via Arch Linux standard package)
>> >>
>> >> > Try to use the package manager to interactively install the latest
>> >> >
>> >> >> - emacs -Q
>> >> >> following:
>> >> >>
>> http://melpa.org/?utm_source=dlvr.it&utm_medium=twitter#/getting-
>> >> star
>> >> >> ted
>> >> >> - putting this in the buffer
>> >> >
>> >> > (require 'package) ;; You might already have this line (add-to-list
>> >> > 'package-archives
>> >> >  '("melpa" . "http://melpa.org/packages/";) t) (when (<
>> >> > emacs-major-version 24)
>> >> >   ;; For important compatibility libraries like cl-lib
>> >> >   (add-to-list 'package-archives '("gnu" .
>> >> > "http://elpa.gnu.org/packages/";)))
>> >> > (package-initialize) ;; You might already have this line
>> >> >
>> >>
>> >> I could do this, though I've sort of decided to steer away from
>> >> packages and just manage things manually via my ~/.elisp/site-lisp
>> >> folder. Would this have an affect? My process was to simply download
>> >> the .zip of ESS, and unpack to ~/.elisp/site-lisp/ess (after deleting
>> >> the old version). This way, my .emacs can continue to point to
>> >> ~/.elisp/site-lisp/ess/lisp regardless of what version I have.
>> >>
>> >> If manual vs. [m]elpa would make a difference, I suppose I could give
>> >> the above a whirl.
>> >>
>> >
>> > Well, you'll get everything compiled if you use the package manager.
>> Worth it just for that!  There are other ways to get those files 
>> byte-compiled,
>> but the package manager is probably the best.
>>
>> ESS is sounding like compilation is optional, and I never have.
>> - http://ess.r-project.org/Manual/ess.html#Installation
>>
>> >
>> > Also, the package manager can help you discover when updates exist to
>> ALL your eamcs packages.  Worth learning for that.
>>
>> Definitely. I may look into that. I pretty much just use Org and R, so not 
>> super
>> worried about it, but I really don't know enough to understand what other
>> packages ship with emacs that I could/should be updating!
>>
>> >
>> > OTOH, as I said, it has been in flux lately and is still a moving target.
>> >
>> > BTW, when did you last update emacs?
>>
>> $ grep emacs /var/log/pacman.log
>>
>> [2014-06-14 20:49] [PACMAN] upgraded emacs (24.3-6 -> 24.3-7)
>> [2014-10-23 10:28] [PACMAN] upgraded emacs (24.3-7 -> 24.4-1)
>> [2015-01-19 01:36] [ALPM] upgraded emacs (24.4-1 -> 24.4-2)
>> [2015-04-20 13:14] [ALPM] upgraded emacs (24.4-2 -> 24.5-1)
>>
>> >
>> > And, does (require 'ess-site) ALL BY ITSELF generate your error?
>> >
>>
>> Yup, see the original email:
>>
>> #+begin_q

Re: [O] Recently emacs hangs on startup due to ESS

2015-05-28 Thread John Hendy
On Thu, May 28, 2015 at 6:34 PM, Cook, Malcolm  wrote:
> John, still recommend you try fresh ess, compiled via package manager.  Also, 
> update any packages needing updated.  Maybe speedbar?

So, I followed your nice ELPA instructions, and things worked. Then I
wondered if it was compilation related, so I did that in my manually
downloaded ESS dir and re-enabled my default load path (instead of
ELPA), and no emacs hang. Then I run make clean, no hang. Then I do
the emacs -Q method in my original email... hang. Then make again, no
hang. Then make clean. No hang.

I also played with ess-speedbar-use-p in case it's an issue with that,
but at this point I feel like I can't reproducibly cause it to hang
anymore so I don't know what in the world is going on.

Definite wtf moment for me!


Thanks for all of your input/suggestions!
John

>
> I'm dry,
>
> Best,
>
> Malcolm
>
>> -Original Message-
>> From: John Hendy [mailto:jw.he...@gmail.com]
>> Sent: Thursday, May 28, 2015 6:24 PM
>> To: Cook, Malcolm
>> Cc: emacs-orgmode
>> Subject: Re: [O] Recently emacs hangs on startup due to ESS
>>
>> On Thu, May 28, 2015 at 5:38 PM, Cook, Malcolm 
>> wrote:
>> >> On Thu, May 28, 2015 at 5:07 PM, Cook, Malcolm 
>> >> wrote:
>> >> > I would install latest ess fresh.
>> >>
>> >> I wondered about that as well, so I tried that prior to posting here.
>> >> Sorry, I should have listed my version, which is now 15.03-1.
>> >>
>> >> > What version of emacs?  The package manager is a moving target
>> >> > these
>> >> days.
>> >>
>> >> GNU Emacs 24.5.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.16.2)
>> >> (installed via Arch Linux standard package)
>> >>
>> >> > Try to use the package manager to interactively install the latest
>> >> >
>> >> >> - emacs -Q
>> >> >> following:
>> >> >>
>> http://melpa.org/?utm_source=dlvr.it&utm_medium=twitter#/getting-
>> >> star
>> >> >> ted
>> >> >> - putting this in the buffer
>> >> >
>> >> > (require 'package) ;; You might already have this line (add-to-list
>> >> > 'package-archives
>> >> >  '("melpa" . "http://melpa.org/packages/";) t) (when (<
>> >> > emacs-major-version 24)
>> >> >   ;; For important compatibility libraries like cl-lib
>> >> >   (add-to-list 'package-archives '("gnu" .
>> >> > "http://elpa.gnu.org/packages/";)))
>> >> > (package-initialize) ;; You might already have this line
>> >> >
>> >>
>> >> I could do this, though I've sort of decided to steer away from
>> >> packages and just manage things manually via my ~/.elisp/site-lisp
>> >> folder. Would this have an affect? My process was to simply download
>> >> the .zip of ESS, and unpack to ~/.elisp/site-lisp/ess (after deleting
>> >> the old version). This way, my .emacs can continue to point to
>> >> ~/.elisp/site-lisp/ess/lisp regardless of what version I have.
>> >>
>> >> If manual vs. [m]elpa would make a difference, I suppose I could give
>> >> the above a whirl.
>> >>
>> >
>> > Well, you'll get everything compiled if you use the package manager.
>> Worth it just for that!  There are other ways to get those files 
>> byte-compiled,
>> but the package manager is probably the best.
>>
>> ESS is sounding like compilation is optional, and I never have.
>> - http://ess.r-project.org/Manual/ess.html#Installation
>>
>> >
>> > Also, the package manager can help you discover when updates exist to
>> ALL your eamcs packages.  Worth learning for that.
>>
>> Definitely. I may look into that. I pretty much just use Org and R, so not 
>> super
>> worried about it, but I really don't know enough to understand what other
>> packages ship with emacs that I could/should be updating!
>>
>> >
>> > OTOH, as I said, it has been in flux lately and is still a moving target.
>> >
>> > BTW, when did you last update emacs?
>>
>> $ grep emacs /var/log/pacman.log
>>
>> [2014-06-14 20:49] [PACMAN] upgraded emacs (24.3-6 -> 24.3-7)
>> [2014-10-23 10:28] [PACMAN] upgraded emacs (24.3-7 -> 24.4-1)
>> [2015-01-19 01:36] [ALPM] upgraded emacs (24.4-1 -> 24.4-2)
>> [2015-04-20 13:14] [ALPM] upgraded emacs (24.4-2 -> 24.5-1)
>>
>> >
>> > And, does (require 'ess-site) ALL BY ITSELF generate your error?
>> >
>>
>> Yup, see the original email:
>>
>> #+begin_quote
>>
>> I can reproduce this with:
>> - emacs -Q
>> - putting this in the buffer
>>
>> (add-to-list 'load-path "/path/to/ess/lisp") (require 'ess-site)
>>
>> - M-x eval-region on the above two lines
>>
>> #+end_quote
>>
>>
>> Thanks for the assistance!
>> John
>>
>> > ~Malcolm
>> >
>> >
>> >>
>> >> Best regards,
>> >> John
>> >>
>> >> >
>> >> >>
>> >> >> - M-x eval-region on the above lines
>> >> >>
>> >> >
>> >> > Then, M-x list-packages and install it by positioning the cursor on
>> >> > the line
>> >> mentioning the ess package from melpa and typing "I".
>> >> >
>> >> > The type "x" to execute your decision, and confirm with "yes".
>> >> >
>> >> > Now, delete or move/hide your old ess bits and restart emacs.
>> >> >
>> >> > Did it work?
>> >> >
>> >> >> -Original Message-
>>

Re: [O] Recently emacs hangs on startup due to ESS

2015-05-28 Thread Cook, Malcolm
John, still recommend you try fresh ess, compiled via package manager.  Also, 
update any packages needing updated.  Maybe speedbar?

I'm dry,

Best,

Malcolm

> -Original Message-
> From: John Hendy [mailto:jw.he...@gmail.com]
> Sent: Thursday, May 28, 2015 6:24 PM
> To: Cook, Malcolm
> Cc: emacs-orgmode
> Subject: Re: [O] Recently emacs hangs on startup due to ESS
> 
> On Thu, May 28, 2015 at 5:38 PM, Cook, Malcolm 
> wrote:
> >> On Thu, May 28, 2015 at 5:07 PM, Cook, Malcolm 
> >> wrote:
> >> > I would install latest ess fresh.
> >>
> >> I wondered about that as well, so I tried that prior to posting here.
> >> Sorry, I should have listed my version, which is now 15.03-1.
> >>
> >> > What version of emacs?  The package manager is a moving target
> >> > these
> >> days.
> >>
> >> GNU Emacs 24.5.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.16.2)
> >> (installed via Arch Linux standard package)
> >>
> >> > Try to use the package manager to interactively install the latest
> >> >
> >> >> - emacs -Q
> >> >> following:
> >> >>
> http://melpa.org/?utm_source=dlvr.it&utm_medium=twitter#/getting-
> >> star
> >> >> ted
> >> >> - putting this in the buffer
> >> >
> >> > (require 'package) ;; You might already have this line (add-to-list
> >> > 'package-archives
> >> >  '("melpa" . "http://melpa.org/packages/";) t) (when (<
> >> > emacs-major-version 24)
> >> >   ;; For important compatibility libraries like cl-lib
> >> >   (add-to-list 'package-archives '("gnu" .
> >> > "http://elpa.gnu.org/packages/";)))
> >> > (package-initialize) ;; You might already have this line
> >> >
> >>
> >> I could do this, though I've sort of decided to steer away from
> >> packages and just manage things manually via my ~/.elisp/site-lisp
> >> folder. Would this have an affect? My process was to simply download
> >> the .zip of ESS, and unpack to ~/.elisp/site-lisp/ess (after deleting
> >> the old version). This way, my .emacs can continue to point to
> >> ~/.elisp/site-lisp/ess/lisp regardless of what version I have.
> >>
> >> If manual vs. [m]elpa would make a difference, I suppose I could give
> >> the above a whirl.
> >>
> >
> > Well, you'll get everything compiled if you use the package manager.
> Worth it just for that!  There are other ways to get those files 
> byte-compiled,
> but the package manager is probably the best.
> 
> ESS is sounding like compilation is optional, and I never have.
> - http://ess.r-project.org/Manual/ess.html#Installation
> 
> >
> > Also, the package manager can help you discover when updates exist to
> ALL your eamcs packages.  Worth learning for that.
> 
> Definitely. I may look into that. I pretty much just use Org and R, so not 
> super
> worried about it, but I really don't know enough to understand what other
> packages ship with emacs that I could/should be updating!
> 
> >
> > OTOH, as I said, it has been in flux lately and is still a moving target.
> >
> > BTW, when did you last update emacs?
> 
> $ grep emacs /var/log/pacman.log
> 
> [2014-06-14 20:49] [PACMAN] upgraded emacs (24.3-6 -> 24.3-7)
> [2014-10-23 10:28] [PACMAN] upgraded emacs (24.3-7 -> 24.4-1)
> [2015-01-19 01:36] [ALPM] upgraded emacs (24.4-1 -> 24.4-2)
> [2015-04-20 13:14] [ALPM] upgraded emacs (24.4-2 -> 24.5-1)
> 
> >
> > And, does (require 'ess-site) ALL BY ITSELF generate your error?
> >
> 
> Yup, see the original email:
> 
> #+begin_quote
> 
> I can reproduce this with:
> - emacs -Q
> - putting this in the buffer
> 
> (add-to-list 'load-path "/path/to/ess/lisp") (require 'ess-site)
> 
> - M-x eval-region on the above two lines
> 
> #+end_quote
> 
> 
> Thanks for the assistance!
> John
> 
> > ~Malcolm
> >
> >
> >>
> >> Best regards,
> >> John
> >>
> >> >
> >> >>
> >> >> - M-x eval-region on the above lines
> >> >>
> >> >
> >> > Then, M-x list-packages and install it by positioning the cursor on
> >> > the line
> >> mentioning the ess package from melpa and typing "I".
> >> >
> >> > The type "x" to execute your decision, and confirm with "yes".
> >> >
> >> > Now, delete or move/hide your old ess bits and restart emacs.
> >> >
> >> > Did it work?
> >> >
> >> >> -Original Message-
> >> >> From: emacs-orgmode-bounces+mec=stowers@gnu.org
> >> [mailto:emacs-
> >> >> orgmode-bounces+mec=stowers@gnu.org] On Behalf Of John
> Hendy
> >> >> Sent: Thursday, May 28, 2015 2:51 PM
> >> >> To: emacs-orgmode
> >> >> Subject: [O] Recently emacs hangs on startup due to ESS
> >> >>
> >> >> Over the past couple of weeks, I've been having some issues with
> >> >> emacs hanging on startup. I usually kill the process, but
> >> >> inadvertently left it in the background today, noting much later
> >> >> that it ended up starting. I played with commenting out various
> >> >> parts of my config until I narrowed things down to the line:
> >> >>
> >> >> (require 'ess-site)
> >> >>
> >> >> the message buffer displays "enabling speedbar support" for a
> >> >> reeeaaally long time before it eventually starts up.
> >> >>

Re: [O] Recently emacs hangs on startup due to ESS

2015-05-28 Thread John Hendy
On Thu, May 28, 2015 at 5:38 PM, Cook, Malcolm  wrote:
>> On Thu, May 28, 2015 at 5:07 PM, Cook, Malcolm 
>> wrote:
>> > I would install latest ess fresh.
>>
>> I wondered about that as well, so I tried that prior to posting here.
>> Sorry, I should have listed my version, which is now 15.03-1.
>>
>> > What version of emacs?  The package manager is a moving target these
>> days.
>>
>> GNU Emacs 24.5.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.16.2)
>> (installed via Arch Linux standard package)
>>
>> > Try to use the package manager to interactively install the latest
>> >
>> >> - emacs -Q
>> >> following:
>> >> http://melpa.org/?utm_source=dlvr.it&utm_medium=twitter#/getting-
>> star
>> >> ted
>> >> - putting this in the buffer
>> >
>> > (require 'package) ;; You might already have this line (add-to-list
>> > 'package-archives
>> >  '("melpa" . "http://melpa.org/packages/";) t) (when (<
>> > emacs-major-version 24)
>> >   ;; For important compatibility libraries like cl-lib
>> >   (add-to-list 'package-archives '("gnu" .
>> > "http://elpa.gnu.org/packages/";)))
>> > (package-initialize) ;; You might already have this line
>> >
>>
>> I could do this, though I've sort of decided to steer away from packages and
>> just manage things manually via my ~/.elisp/site-lisp folder. Would this have
>> an affect? My process was to simply download the .zip of ESS, and unpack to
>> ~/.elisp/site-lisp/ess (after deleting the old version). This way, my .emacs 
>> can
>> continue to point to ~/.elisp/site-lisp/ess/lisp regardless of what version I
>> have.
>>
>> If manual vs. [m]elpa would make a difference, I suppose I could give the
>> above a whirl.
>>
>
> Well, you'll get everything compiled if you use the package manager.  Worth 
> it just for that!  There are other ways to get those files byte-compiled, but 
> the package manager is probably the best.

ESS is sounding like compilation is optional, and I never have.
- http://ess.r-project.org/Manual/ess.html#Installation

>
> Also, the package manager can help you discover when updates exist to ALL 
> your eamcs packages.  Worth learning for that.

Definitely. I may look into that. I pretty much just use Org and R, so
not super worried about it, but I really don't know enough to
understand what other packages ship with emacs that I could/should be
updating!

>
> OTOH, as I said, it has been in flux lately and is still a moving target.
>
> BTW, when did you last update emacs?

$ grep emacs /var/log/pacman.log

[2014-06-14 20:49] [PACMAN] upgraded emacs (24.3-6 -> 24.3-7)
[2014-10-23 10:28] [PACMAN] upgraded emacs (24.3-7 -> 24.4-1)
[2015-01-19 01:36] [ALPM] upgraded emacs (24.4-1 -> 24.4-2)
[2015-04-20 13:14] [ALPM] upgraded emacs (24.4-2 -> 24.5-1)

>
> And, does (require 'ess-site) ALL BY ITSELF generate your error?
>

Yup, see the original email:

#+begin_quote

I can reproduce this with:
- emacs -Q
- putting this in the buffer

(add-to-list 'load-path "/path/to/ess/lisp")
(require 'ess-site)

- M-x eval-region on the above two lines

#+end_quote


Thanks for the assistance!
John

> ~Malcolm
>
>
>>
>> Best regards,
>> John
>>
>> >
>> >>
>> >> - M-x eval-region on the above lines
>> >>
>> >
>> > Then, M-x list-packages and install it by positioning the cursor on the 
>> > line
>> mentioning the ess package from melpa and typing "I".
>> >
>> > The type "x" to execute your decision, and confirm with "yes".
>> >
>> > Now, delete or move/hide your old ess bits and restart emacs.
>> >
>> > Did it work?
>> >
>> >> -Original Message-
>> >> From: emacs-orgmode-bounces+mec=stowers@gnu.org
>> [mailto:emacs-
>> >> orgmode-bounces+mec=stowers@gnu.org] On Behalf Of John Hendy
>> >> Sent: Thursday, May 28, 2015 2:51 PM
>> >> To: emacs-orgmode
>> >> Subject: [O] Recently emacs hangs on startup due to ESS
>> >>
>> >> Over the past couple of weeks, I've been having some issues with
>> >> emacs hanging on startup. I usually kill the process, but
>> >> inadvertently left it in the background today, noting much later that
>> >> it ended up starting. I played with commenting out various parts of
>> >> my config until I narrowed things down to the line:
>> >>
>> >> (require 'ess-site)
>> >>
>> >> the message buffer displays "enabling speedbar support" for a
>> >> reeeaaally long time before it eventually starts up.
>> >>
>> >> I tried debug-on-signal and eval-expression-debug-on-error... I'm not
>> >> sure what is supposed to happen with debug options, but no debug
>> >> buffer pops up. The only lines that appear relevant in *Messages* are:
>> >>
>> >> ad-handle-definition: `ess-indent-command' got redefined
>> >> ad-handle-definition: `ess-eval-line-and-step' got redefined
>> >>
>> >> How might I diagnose this further?. I'm not familiar with chasing
>> >> down Emacs issues other than narrowing it down to a config file option.
>> >>
>> >> I can reproduce this with:
>> >> - emacs -Q
>> >> - putting this in the buffer
>> >>
>> >> (add-to-list 'load-path "/path/t

Re: [O] [BUG] Radio Targets and double quotes

2015-05-28 Thread Nicolas Goaziou
Hello

thomas  writes:

> a radio target reference followed by another radio target in double
> quotes breaks html-export.
> The following minimal throws an error:
>
> ===
>
> Keyword1 "keyword2"
>
> <<>>
>
> <<>>
>
> ===
>
> Error Message:
>
> org-export-activate-smart-quotes: Wrong number of arguments: #[(q
> type) "ÆÇ\"ƒ

I cannot reproduce it. What Org version are you using?

> (after that comes a number of weird symbols that I cannot even copy
> into the email...)

You should use Org uncompiled (C-u org-reload) to get a better backtrace.

Regards,

--
Nicolas Goaziou



Re: [O] Recently emacs hangs on startup due to ESS

2015-05-28 Thread Cook, Malcolm
> On Thu, May 28, 2015 at 5:07 PM, Cook, Malcolm 
> wrote:
> > I would install latest ess fresh.
> 
> I wondered about that as well, so I tried that prior to posting here.
> Sorry, I should have listed my version, which is now 15.03-1.
> 
> > What version of emacs?  The package manager is a moving target these
> days.
> 
> GNU Emacs 24.5.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.16.2)
> (installed via Arch Linux standard package)
> 
> > Try to use the package manager to interactively install the latest
> >
> >> - emacs -Q
> >> following:
> >> http://melpa.org/?utm_source=dlvr.it&utm_medium=twitter#/getting-
> star
> >> ted
> >> - putting this in the buffer
> >
> > (require 'package) ;; You might already have this line (add-to-list
> > 'package-archives
> >  '("melpa" . "http://melpa.org/packages/";) t) (when (<
> > emacs-major-version 24)
> >   ;; For important compatibility libraries like cl-lib
> >   (add-to-list 'package-archives '("gnu" .
> > "http://elpa.gnu.org/packages/";)))
> > (package-initialize) ;; You might already have this line
> >
> 
> I could do this, though I've sort of decided to steer away from packages and
> just manage things manually via my ~/.elisp/site-lisp folder. Would this have
> an affect? My process was to simply download the .zip of ESS, and unpack to
> ~/.elisp/site-lisp/ess (after deleting the old version). This way, my .emacs 
> can
> continue to point to ~/.elisp/site-lisp/ess/lisp regardless of what version I
> have.
> 
> If manual vs. [m]elpa would make a difference, I suppose I could give the
> above a whirl.
> 

Well, you'll get everything compiled if you use the package manager.  Worth it 
just for that!  There are other ways to get those files byte-compiled, but the 
package manager is probably the best.

Also, the package manager can help you discover when updates exist to ALL your 
eamcs packages.  Worth learning for that.

OTOH, as I said, it has been in flux lately and is still a moving target.

BTW, when did you last update emacs?

And, does (require 'ess-site) ALL BY ITSELF generate your error?

~Malcolm


> 
> Best regards,
> John
> 
> >
> >>
> >> - M-x eval-region on the above lines
> >>
> >
> > Then, M-x list-packages and install it by positioning the cursor on the line
> mentioning the ess package from melpa and typing "I".
> >
> > The type "x" to execute your decision, and confirm with "yes".
> >
> > Now, delete or move/hide your old ess bits and restart emacs.
> >
> > Did it work?
> >
> >> -Original Message-
> >> From: emacs-orgmode-bounces+mec=stowers@gnu.org
> [mailto:emacs-
> >> orgmode-bounces+mec=stowers@gnu.org] On Behalf Of John Hendy
> >> Sent: Thursday, May 28, 2015 2:51 PM
> >> To: emacs-orgmode
> >> Subject: [O] Recently emacs hangs on startup due to ESS
> >>
> >> Over the past couple of weeks, I've been having some issues with
> >> emacs hanging on startup. I usually kill the process, but
> >> inadvertently left it in the background today, noting much later that
> >> it ended up starting. I played with commenting out various parts of
> >> my config until I narrowed things down to the line:
> >>
> >> (require 'ess-site)
> >>
> >> the message buffer displays "enabling speedbar support" for a
> >> reeeaaally long time before it eventually starts up.
> >>
> >> I tried debug-on-signal and eval-expression-debug-on-error... I'm not
> >> sure what is supposed to happen with debug options, but no debug
> >> buffer pops up. The only lines that appear relevant in *Messages* are:
> >>
> >> ad-handle-definition: `ess-indent-command' got redefined
> >> ad-handle-definition: `ess-eval-line-and-step' got redefined
> >>
> >> How might I diagnose this further?. I'm not familiar with chasing
> >> down Emacs issues other than narrowing it down to a config file option.
> >>
> >> I can reproduce this with:
> >> - emacs -Q
> >> - putting this in the buffer
> >>
> >> (add-to-list 'load-path "/path/to/ess/lisp") (require 'ess-site)
> >>
> >> - M-x eval-region on the above two lines
> >>
> >>
> >> Thanks for any suggestions,
> >> John
> >


Re: [O] Recently emacs hangs on startup due to ESS

2015-05-28 Thread John Hendy
On Thu, May 28, 2015 at 5:07 PM, Cook, Malcolm  wrote:
> I would install latest ess fresh.

I wondered about that as well, so I tried that prior to posting here.
Sorry, I should have listed my version, which is now 15.03-1.

> What version of emacs?  The package manager is a moving target these days.

GNU Emacs 24.5.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.16.2)
(installed via Arch Linux standard package)

> Try to use the package manager to interactively install the latest
>
>> - emacs -Q
>> following: 
>> http://melpa.org/?utm_source=dlvr.it&utm_medium=twitter#/getting-started
>> - putting this in the buffer
>
> (require 'package) ;; You might already have this line
> (add-to-list 'package-archives
>  '("melpa" . "http://melpa.org/packages/";) t)
> (when (< emacs-major-version 24)
>   ;; For important compatibility libraries like cl-lib
>   (add-to-list 'package-archives '("gnu" . "http://elpa.gnu.org/packages/";)))
> (package-initialize) ;; You might already have this line
>

I could do this, though I've sort of decided to steer away from
packages and just manage things manually via my ~/.elisp/site-lisp
folder. Would this have an affect? My process was to simply download
the .zip of ESS, and unpack to ~/.elisp/site-lisp/ess (after deleting
the old version). This way, my .emacs can continue to point to
~/.elisp/site-lisp/ess/lisp regardless of what version I have.

If manual vs. [m]elpa would make a difference, I suppose I could give
the above a whirl.


Best regards,
John

>
>>
>> - M-x eval-region on the above lines
>>
>
> Then, M-x list-packages and install it by positioning the cursor on the line 
> mentioning the ess package from melpa and typing "I".
>
> The type "x" to execute your decision, and confirm with "yes".
>
> Now, delete or move/hide your old ess bits and restart emacs.
>
> Did it work?
>
>> -Original Message-
>> From: emacs-orgmode-bounces+mec=stowers@gnu.org [mailto:emacs-
>> orgmode-bounces+mec=stowers@gnu.org] On Behalf Of John Hendy
>> Sent: Thursday, May 28, 2015 2:51 PM
>> To: emacs-orgmode
>> Subject: [O] Recently emacs hangs on startup due to ESS
>>
>> Over the past couple of weeks, I've been having some issues with emacs
>> hanging on startup. I usually kill the process, but inadvertently left it in 
>> the
>> background today, noting much later that it ended up starting. I played with
>> commenting out various parts of my config until I narrowed things down to
>> the line:
>>
>> (require 'ess-site)
>>
>> the message buffer displays "enabling speedbar support" for a reeeaaally
>> long time before it eventually starts up.
>>
>> I tried debug-on-signal and eval-expression-debug-on-error... I'm not sure
>> what is supposed to happen with debug options, but no debug buffer pops
>> up. The only lines that appear relevant in *Messages* are:
>>
>> ad-handle-definition: `ess-indent-command' got redefined
>> ad-handle-definition: `ess-eval-line-and-step' got redefined
>>
>> How might I diagnose this further?. I'm not familiar with chasing down Emacs
>> issues other than narrowing it down to a config file option.
>>
>> I can reproduce this with:
>> - emacs -Q
>> - putting this in the buffer
>>
>> (add-to-list 'load-path "/path/to/ess/lisp") (require 'ess-site)
>>
>> - M-x eval-region on the above two lines
>>
>>
>> Thanks for any suggestions,
>> John
>



Re: [O] Recently emacs hangs on startup due to ESS

2015-05-28 Thread Cook, Malcolm
I would install latest ess fresh.

What version of emacs?  The package manager is a moving target these days.

Try to use the package manager to interactively install the latest 

> - emacs -Q
> following: 
> http://melpa.org/?utm_source=dlvr.it&utm_medium=twitter#/getting-started
> - putting this in the buffer

(require 'package) ;; You might already have this line
(add-to-list 'package-archives
 '("melpa" . "http://melpa.org/packages/";) t)
(when (< emacs-major-version 24)
  ;; For important compatibility libraries like cl-lib
  (add-to-list 'package-archives '("gnu" . "http://elpa.gnu.org/packages/";)))
(package-initialize) ;; You might already have this line


> 
> - M-x eval-region on the above lines
>

Then, M-x list-packages and install it by positioning the cursor on the line 
mentioning the ess package from melpa and typing "I".

The type "x" to execute your decision, and confirm with "yes".

Now, delete or move/hide your old ess bits and restart emacs.

Did it work?

> -Original Message-
> From: emacs-orgmode-bounces+mec=stowers@gnu.org [mailto:emacs-
> orgmode-bounces+mec=stowers@gnu.org] On Behalf Of John Hendy
> Sent: Thursday, May 28, 2015 2:51 PM
> To: emacs-orgmode
> Subject: [O] Recently emacs hangs on startup due to ESS
> 
> Over the past couple of weeks, I've been having some issues with emacs
> hanging on startup. I usually kill the process, but inadvertently left it in 
> the
> background today, noting much later that it ended up starting. I played with
> commenting out various parts of my config until I narrowed things down to
> the line:
> 
> (require 'ess-site)
> 
> the message buffer displays "enabling speedbar support" for a reeeaaally
> long time before it eventually starts up.
> 
> I tried debug-on-signal and eval-expression-debug-on-error... I'm not sure
> what is supposed to happen with debug options, but no debug buffer pops
> up. The only lines that appear relevant in *Messages* are:
> 
> ad-handle-definition: `ess-indent-command' got redefined
> ad-handle-definition: `ess-eval-line-and-step' got redefined
> 
> How might I diagnose this further?. I'm not familiar with chasing down Emacs
> issues other than narrowing it down to a config file option.
> 
> I can reproduce this with:
> - emacs -Q
> - putting this in the buffer
> 
> (add-to-list 'load-path "/path/to/ess/lisp") (require 'ess-site)
> 
> - M-x eval-region on the above two lines
> 
> 
> Thanks for any suggestions,
> John



Re: [O] babel scheme not working

2015-05-28 Thread Nick Dokos
Lawrence Bottorff  writes:

> Yes, thanks, the :session did the trick. Is that documented somewhere?
> Also, it ignored my running MIT Scheme and fired up a Guile REPL in
> the next buffer. I guess it's doing something with Geiser, hence,
> Guile?
>

(info "(org) session"):

,
| The ‘:session’ header argument starts a (possibly named) session for an
| interpreted language where the interpreter’s state is preserved.  All
| code blocks sharing the same name are exectuted by the same interpreter
| process.  By default, a session is not started.
`

The interpreter that geiser runs is specified in
geiser-default-implementation.


> On Thu, May 28, 2015 at 3:20 PM, Nick Dokos  wrote:
>
> Lawrence Bottorff  writes:
>
> > The MIT scheme repl is running in the next buffer. . .
> >
>
> Did you try it?
>
> --8<---cut here---start->8---
> #+BEGIN_SRC scheme :session foo
>  (define (mydouble x)
>  (+ x x))
> #+END_SRC
>
> #+RESULTS:
>
> doesn't seem to remember from one block to the next. So, after defining 
> the code above
>
> #+BEGIN_SRC scheme :session foo
>  (mydouble 5)
> #+END_SRC
>
> #+RESULTS:
> : 10
> --8<---cut here---end--->8---
>
> Without the session, I get
>
> #+RESULTS
> : An error occurred.
>
> instead. This is with guile as the scheme interpreter, but that should
> not make any difference.
>
> > On May 28, 2015 2:16 PM, "Nick Dokos"  wrote:
> >
> >     Lawrence Bottorff  writes:
> >
> >     > . . . installed geiser via elpa -- and got some functionality. 
> Although a simple thing like 
> >     >
> >     > #+BEGIN_SRC scheme
> >     > (define (mydouble x)
> >     > (+ x x))  
> >     >   #+END_SRC
> >     >
> >     > doesn't seem to remember from one block to the next. So, after 
> defining the code above
> >     >
> >     > #+BEGIN_SRC scheme
> >     > (mydouble 5)
> >     >  #+END_SRC
> >     >
> >     > gives an error, while 
> >     >
> >     >  #+BEGIN_SRC scheme
> >     > (define (mysquare x)
> >     >   (* x x))
> >     > (mysquare 5)
> >     >  #+END_SRC
> >     >
> >     >   #+RESULTS:
> >     >   : 25
> >     >
> >     > works. Any way to have it remember like a REPL does?
> >
> >     Use a session?
>

Nick





[O] Recently emacs hangs on startup due to ESS

2015-05-28 Thread John Hendy
Over the past couple of weeks, I've been having some issues with emacs
hanging on startup. I usually kill the process, but inadvertently left
it in the background today, noting much later that it ended up
starting. I played with commenting out various parts of my config
until I narrowed things down to the line:

(require 'ess-site)

the message buffer displays "enabling speedbar support" for a
reeeaaally long time before it eventually starts up.

I tried debug-on-signal and eval-expression-debug-on-error... I'm not
sure what is supposed to happen with debug options, but no debug
buffer pops up. The only lines that appear relevant in *Messages* are:

ad-handle-definition: `ess-indent-command' got redefined
ad-handle-definition: `ess-eval-line-and-step' got redefined

How might I diagnose this further?. I'm not familiar with chasing down
Emacs issues other than narrowing it down to a config file option.

I can reproduce this with:
- emacs -Q
- putting this in the buffer

(add-to-list 'load-path "/path/to/ess/lisp")
(require 'ess-site)

- M-x eval-region on the above two lines


Thanks for any suggestions,
John



Re: [O] babel scheme not working

2015-05-28 Thread Lawrence Bottorff
Yes, thanks, the :session did the trick. Is that documented somewhere?
Also, it ignored my running MIT Scheme and fired up a Guile REPL in the
next buffer. I guess it's doing something with Geiser, hence, Guile?

On Thu, May 28, 2015 at 3:20 PM, Nick Dokos  wrote:

> Lawrence Bottorff  writes:
>
> > The MIT scheme repl is running in the next buffer. . .
> >
>
> Did you try it?
>
> --8<---cut here---start->8---
> #+BEGIN_SRC scheme :session foo
>  (define (mydouble x)
>  (+ x x))
> #+END_SRC
>
> #+RESULTS:
>
> doesn't seem to remember from one block to the next. So, after defining
> the code above
>
> #+BEGIN_SRC scheme :session foo
>  (mydouble 5)
> #+END_SRC
>
> #+RESULTS:
> : 10
> --8<---cut here---end--->8---
>
> Without the session, I get
>
> #+RESULTS
> : An error occurred.
>
> instead. This is with guile as the scheme interpreter, but that should
> not make any difference.
>
>
> > On May 28, 2015 2:16 PM, "Nick Dokos"  wrote:
> >
> > Lawrence Bottorff  writes:
> >
> > > . . . installed geiser via elpa -- and got some functionality.
> Although a simple thing like
> > >
> > > #+BEGIN_SRC scheme
> > > (define (mydouble x)
> > > (+ x x))
> > >   #+END_SRC
> > >
> > > doesn't seem to remember from one block to the next. So, after
> defining the code above
> > >
> > > #+BEGIN_SRC scheme
> > > (mydouble 5)
> > >  #+END_SRC
> > >
> > > gives an error, while
> > >
> > >  #+BEGIN_SRC scheme
> > > (define (mysquare x)
> > >   (* x x))
> > > (mysquare 5)
> > >  #+END_SRC
> > >
> > >   #+RESULTS:
> > >   : 25
> > >
> > > works. Any way to have it remember like a REPL does?
> >
> > Use a session?
>
> Nick
>
>
>


Re: [O] babel scheme not working

2015-05-28 Thread Nick Dokos
Lawrence Bottorff  writes:

> The MIT scheme repl is running in the next buffer. . .
>

Did you try it?

--8<---cut here---start->8---
#+BEGIN_SRC scheme :session foo
 (define (mydouble x)
 (+ x x))
#+END_SRC

#+RESULTS:

doesn't seem to remember from one block to the next. So, after defining the 
code above

#+BEGIN_SRC scheme :session foo
 (mydouble 5)
#+END_SRC

#+RESULTS:
: 10
--8<---cut here---end--->8---

Without the session, I get

#+RESULTS
: An error occurred.

instead. This is with guile as the scheme interpreter, but that should
not make any difference.


> On May 28, 2015 2:16 PM, "Nick Dokos"  wrote:
>
> Lawrence Bottorff  writes:
>
> > . . . installed geiser via elpa -- and got some functionality. Although 
> a simple thing like 
> >
> > #+BEGIN_SRC scheme
> > (define (mydouble x)
> > (+ x x))  
> >   #+END_SRC
> >
> > doesn't seem to remember from one block to the next. So, after defining 
> the code above
> >
> > #+BEGIN_SRC scheme
> > (mydouble 5)
> >  #+END_SRC
> >
> > gives an error, while 
> >
> >  #+BEGIN_SRC scheme
> > (define (mysquare x)
> >   (* x x))
> > (mysquare 5)
> >  #+END_SRC
> >
> >   #+RESULTS:
> >   : 25
> >
> > works. Any way to have it remember like a REPL does?
>
> Use a session?

Nick




Re: [O] [BUG] in last org in indentation of source blocks

2015-05-28 Thread Titus von der Malsburg

On 2015-05-28 Thu 11:15, Thomas S. Dye wrote:
> Titus von der Malsburg  writes:
>
>> I can’t reproduce the second indent but I think it’s a bug that there is
>> any indentation at all.
>>
>> The documentation of `org-edit-special' (C-x ') says:
>>
>>   Call a special editor for the element at point. …
>>
>> No mention of indentation or other reformatting of my code.
>>
>> The same goes for `org-edit-src-exit' (C-c C-c) which says:
>>
>>   Kill current sub-editing buffer and return to source buffer.
>>
>> The edit-in-buffer feature should not touch the indentation.  If the
>> syntax of the language is sensitive to indentation (e.g. Python) this
>> can break the code.  Example:
>>
>> #+BEGIN_SRC python :results output
>>   print "test"
>> #+END_SRC
>>
>> is invalid Python syntax.
>>
>> Also having one function perform two very different actions (edit code
>> in separate buffer *and* reformat the code) is poor design.  At least in
>> this special case.  When I open the code in a separate buffer but then
>> decide not to change it (C-c C-c), I'll end up with extra indentation
>> and this will create unnecessary changes when I commit the file in git.
>
> Does the variable org-src-preserve-indentation get the behavior you're
> after?

It does.  I propose two changes:

1.) The default value `org-src-preserve-indentation' should be t because
that is safer (see Python example) and more conservative.  (Don’t mess
with my code!)

2.) The documentation of `org-edit-special' and `org-edit-src-exit'
should point out that depending on `org-src-preserve-indentation' the
code may be re-indented.

Even better would be to remove `org-src-preserve-indentation' and to do
the right thing, which is to leave the code untouched.  Emacs already
has facilities for indenting code.  No need to reinvent the wheel.

  Titus




signature.asc
Description: PGP signature


Re: [O] babel scheme not working

2015-05-28 Thread Lawrence Bottorff
The MIT scheme repl is running in the next buffer. . .
On May 28, 2015 2:16 PM, "Nick Dokos"  wrote:

> Lawrence Bottorff  writes:
>
> > . . . installed geiser via elpa -- and got some functionality. Although
> a simple thing like
> >
> > #+BEGIN_SRC scheme
> > (define (mydouble x)
> > (+ x x))
> >   #+END_SRC
> >
> > doesn't seem to remember from one block to the next. So, after defining
> the code above
> >
> > #+BEGIN_SRC scheme
> > (mydouble 5)
> >  #+END_SRC
> >
> > gives an error, while
> >
> >  #+BEGIN_SRC scheme
> > (define (mysquare x)
> >   (* x x))
> > (mysquare 5)
> >  #+END_SRC
> >
> >   #+RESULTS:
> >   : 25
> >
> > works. Any way to have it remember like a REPL does?
>
> Use a session?
>
>
>


Re: [O] [BUG] in last org in indentation of source blocks

2015-05-28 Thread Thomas S. Dye
Titus von der Malsburg  writes:

> I can’t reproduce the second indent but I think it’s a bug that there is
> any indentation at all.
>
> The documentation of `org-edit-special' (C-x ') says:
>
>   Call a special editor for the element at point. …
>
> No mention of indentation or other reformatting of my code.
>
> The same goes for `org-edit-src-exit' (C-c C-c) which says:
>
>   Kill current sub-editing buffer and return to source buffer.
>
> The edit-in-buffer feature should not touch the indentation.  If the
> syntax of the language is sensitive to indentation (e.g. Python) this
> can break the code.  Example:
>
> #+BEGIN_SRC python :results output
>   print "test"
> #+END_SRC
>
> is invalid Python syntax.
>
> Also having one function perform two very different actions (edit code
> in separate buffer *and* reformat the code) is poor design.  At least in
> this special case.  When I open the code in a separate buffer but then
> decide not to change it (C-c C-c), I'll end up with extra indentation
> and this will create unnecessary changes when I commit the file in git.

Does the variable org-src-preserve-indentation get the behavior you're
after?

hth,
Tom
-- 
Thomas S. Dye
http://www.tsdye.com



Re: [O] babel scheme not working

2015-05-28 Thread Nick Dokos
Lawrence Bottorff  writes:

> . . . installed geiser via elpa -- and got some functionality. Although a 
> simple thing like 
>
> #+BEGIN_SRC scheme
> (define (mydouble x)
> (+ x x))  
>   #+END_SRC
>
> doesn't seem to remember from one block to the next. So, after defining the 
> code above
>
> #+BEGIN_SRC scheme
> (mydouble 5)
>  #+END_SRC
>
> gives an error, while 
>
>  #+BEGIN_SRC scheme
> (define (mysquare x)
>   (* x x))
> (mysquare 5)
>  #+END_SRC
>
>   #+RESULTS:
>   : 25
>
> works. Any way to have it remember like a REPL does?

Use a session?




[O] [BUG] Radio Targets and double quotes

2015-05-28 Thread thomas

Hi All,

a radio target reference followed by another radio target in double 
quotes breaks html-export.

The following minimal throws an error:

===

Keyword1 "keyword2"

<<>>

<<>>

===

Error Message:

org-export-activate-smart-quotes: Wrong number of arguments: #[(q 
type) "ÆÇ\"ƒ


(after that comes a number of weird symbols that I cannot even copy into 
the email...)


Removing the quotes around "keyword2" fixes the problem:

===

Keyword1 keyword2

<<>>

<<>>

===

What also works is to add another word between Keyword1 and "keyword2":

===

Keyword1 and "keyword2"

<<>>

<<>>

===

Thanks,
thomas



Re: [O] babel scheme not working

2015-05-28 Thread Lawrence Bottorff
. . . installed geiser via elpa -- and got some functionality. Although a
simple thing like

#+BEGIN_SRC scheme
(define (mydouble x)
(+ x x))
  #+END_SRC

doesn't seem to remember from one block to the next. So, after defining the
code above

#+BEGIN_SRC scheme
(mydouble 5)
 #+END_SRC

gives an error, while

 #+BEGIN_SRC scheme
(define (mysquare x)
  (* x x))
(mysquare 5)
 #+END_SRC

  #+RESULTS:
  : 25

works. Any way to have it remember like a REPL does?


[O] babel scheme not working

2015-05-28 Thread Lawrence Bottorff
 #+BEGIN_SRC scheme
(define (mydouble x)
(+ x x))

  #+END_SRC

produces

org-babel-execute-src-block: Symbol's value as variable is void:
geiser-default-implementation

also, no indentation or color coding of any sort (maybe this isn't a
feature yet?)

LB


Re: [O] Org-lint

2015-05-28 Thread Nicolas Goaziou
Hello,

Karl Voit  writes:

> Who do I have to contact, when I've got ideas of checks that
> corrupted my Org-mode files?

You can implement checks and send them to the ML. You can also suggest
them on the ML.

> For example, I have the issue that once upon a Org-mode-Git-
> checkout, the property drawers got corrupted over time: duplicate
> LOGBOOKs

Duplicate LOGBOOK drawers is not an error. You could, for example, use
the second one as an archive. More generally, you can have multiple
drawers with the same name in a given entry.

> and order of LOGBOOK and PROPERTIES is switched. I noticed
> it, when many drawers were already broken. I still find them in my
> files from time to time :-(

Org Lint already looks for PROPERTIES drawers not at their expected
location.

> Another one would be duplicate IDs.

Org Lint checks this already, but it proceed document-wise. It will not
find duplicate ID across files.


Regards,

-- 
Nicolas Goaziou



Re: [O] LaTeX_HEADER blocks

2015-05-28 Thread Nicolas Goaziou
Hello,

Mark Edgington  writes:

> It is possible in org-mode to do either
>
> #+LaTeX: \somecommand
>
> or
>
> #+BEGIN_LaTeX
> \somecommand
> #+END_LaTeX
>
> I typically use the latter (the block form) because I often have
> multiple lines of LaTeX I would like to include at certain locations
> of a document.
>
> Similar to #+LaTeX, there is also #+LaTeX_HEADER, which ensures that
> something is included as part of the preamble.  Unfortunately,
> however, there is no equivalent block form for #+LaTeX_HEADER.  As a
> result, when there are several items one wishes to have in the
> preamble, it's necessary to have many such lines, each with a
> "#+LaTeX_HEADER: " prefix.
>
> For the sake of consistency and convenience, wouldn't it be worthwhile
> to add a "LaTeX_HEADER" block type to accompany the "LaTeX" block
> type?

This would not be consistent.

#+LATEX_HEADER was free for grabs but #+BEGIN_LATEX_HEADER already means
something: it is a special block. As a consequence, export back-ends
ignore LATEX_HEADER but handle BEGIN_LATEX_HEADER (basically, they
ignore the wrapper but export the contents). We would need to
make #+begin_latex_header an export block.

However, I plan to change syntax for export blocks for Org 8.4 and it
will not be possible to define arbitrarily export blocks. In fact,

  #+begin_latex
  ...
  #+end_latex

are expected to become

  #+begin_export latex [attributes]
  ...
  #+begin_export

If latex header block idea is implemented, I think it could instead use
a syntax such as

  #+begin_export latex :header t
  ...
  #+end_export


Regards,

-- 
Nicolas Goaziou



Re: [O] [BUG] in last org in indentation of source blocks

2015-05-28 Thread Titus von der Malsburg

On 2015-05-28 Thu 04:49, Rainer M Krug wrote:
> I reralised this morning that there eems to be a bug introduced in one
> of the last commits which causes repeted editing of source blocks to
> indent more each time the are edited (C-').
>
> Original:
> ,
> | #+begin_src sh
> | echo 2
> | #+end_src
> `
>
> After C-' and back again
> ,
> | #+begin_src sh
> |   echo 2
> | #+end_src
> `
>
> After second C-' and back
> ,
> | #+begin_src sh
> | echo 2
> | #+end_src
> `
>
> When C-', the indirect buffer has the same indentation as the source
> block, but when switching back, two more spaces are added.

I can’t reproduce the second indent but I think it’s a bug that there is
any indentation at all.

The documentation of `org-edit-special' (C-x ') says:

  Call a special editor for the element at point. …

No mention of indentation or other reformatting of my code.

The same goes for `org-edit-src-exit' (C-c C-c) which says:

  Kill current sub-editing buffer and return to source buffer.

The edit-in-buffer feature should not touch the indentation.  If the
syntax of the language is sensitive to indentation (e.g. Python) this
can break the code.  Example:

#+BEGIN_SRC python :results output
  print "test"
#+END_SRC

is invalid Python syntax.

Also having one function perform two very different actions (edit code
in separate buffer *and* reformat the code) is poor design.  At least in
this special case.  When I open the code in a separate buffer but then
decide not to change it (C-c C-c), I'll end up with extra indentation
and this will create unnecessary changes when I commit the file in git.

  Titus



signature.asc
Description: PGP signature


[O] Include other sources (zotero, database) in org-mode search?

2015-05-28 Thread M
I'm currently building a large knowledge database with my org-mode notes.
However there are other sources of knowledge like

- my colleciton of Freeplane mindmaps (xml files)
- my zotero Library

Is it possible to let org-mode also index and search such sources so that I
can search within all relevant sources (org and external) with ONE search?


Kind regards

MArtin





[O] Include other sources (zotero, database) in org-mode search?

2015-05-28 Thread Martin Beck
I'm currently building a large knowledge database with my org-mode notes.
However there are other sources of knowledge like

- my colleciton of Freeplane mindmaps (xml files)
- my zotero Library

Is it possible to let org-mode also index and search such sources so that I
can search within all relevant sources (org and external) with ONE search?


Kind regards

MArtin





Re: [O] org-preview-latex-fragment ignores \includes in the LATEX_HEADER

2015-05-28 Thread Nick Dokos
Stefan Otte  writes:

> Hey,
>
> I'm using orgmode with lots of LaTeX for equations. A typical document
> start with
>
>   #+TITLE: Some Title
>   #+LaTeX_HEADER: \include{commands}
>
> commands.tex contains commands like:
>   \newcommand{\RRR}{{\mathbb{R}}}
>
> The pdf export works flawlessly, however `org-preview-latex-fragment`
> seems to ignore "\include{commands}", i.e., equations that use
> commands that are defined in commands.tex are rendered as blank/empty
> image.
>
> Is it the intended behavior that `org-preview-latex-fragment` ignores
> "\include", is it a bug, or is there a better way to do it?
>
>

Fragments are islands unto themselves with their own special
handling. See the doc for the variable org-format-latex-header.

Nick




[O] Confusing creation of frames and windows

2015-05-28 Thread M
I'm not sure where exactly my problem comes from, but I find it quite
confusing how Emacs / org-mode creates new frames or does show something in
the existing frame or window.

Is there a tutorial or a best-practice setup to get it easy and intuitive?

Kind regards

Martin






Re: [O] Easy to use asking for Or-gmode property values (e.g., for Org-contacts)

2015-05-28 Thread Karl Voit
* Karl Voit  wrote:
>
> This is why I came up with this idea: how about I paste new
> information at the end of and then call a function which helps me a
> lot:
>
> - ask for each property (or a set of pre-defined properties)
>   - prompt property name
>   - let the user mark a region using keyboard or mouse
>   - if user presses confirmation keyoard shortcut (return?)
> - if region: copy the region and set it as the new content for the current
>   property (overwriting any old property settings)
> - if no region is set: do not change property

Jonathan Leech-Pepin sent me his solution to the issue. Instead of
asking for a set of properties, he wrote a function that takes the
currently selected region, asks for a property, and overwrites its
value with the region string.

I found an edge-case which I fixed (by removing leading and trailing
whitespaces) and I added comments as far as I understood the code.

The resulting function is:
,
| (defun my-org-region-to-property (&optional property)
|   (interactive)
|   ;; if no region is defined, do nothing
|   (if (use-region-p)
|   ;; if a region string is found, ask for a property and set property to
|   ;; the string in the region
|   (let ((val (replace-regexp-in-string
|   "\\`[ \t\n]*" ""
|   (replace-regexp-in-string "[ \t\n]*\\'" ""
| (substring (buffer-string)
|(- (region-beginning) 
1)
|(region-end
|  )
| ;; if none was stated by user, read property from user
| (prop (or property
|   (org-read-property-name
| ;; set property
| (org-set-property prop val
`

Thank you very much, Jonathan!

The only downside of this method is, that I have to wait four
seconds until Org-mode has parsed the list of possible properties
within my contacts.org file. 

Is there some kind of caching I could activate similar to (setq
org-refile-use-cache t)?

-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
   > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github




[O] Integrating Org with OS X Reminders (and Siri!)

2015-05-28 Thread Ken Mankoff
Hi List,

I've written a set of small scripts so that I can use the Reminders.app on my 
iPhone and easily get that information into Org. This means I can pick up the 
phone, say "Hey Siri, Remind me about something", and get that info into Org!

Functionality is basic - items show up in Agenda just like MobileOrg items, 
with a "REFILE" flag set so that I can then refile them. If you mark an item as 
done in Org, that state is not reflected on your iPhone or in Reminders.app 
(although this could be possible with a bit of extra coding).

It is a hacked solution with many parts (rem, rem.py, rem.sh, rem.org, and 
rem.plist), described below:

1) Set up Reminders in iCloud so that Reminders on iPhone and Desktop are 
synced.

2) Install "rem" utility from: https://github.com/kykim/rem

3) Build and put the binary somewhere and check that "rem ls" lists your 
reminders

4) Take following "rem.py" and put it somewhere and make sure it runs and 
prints out all reminders and their details. You probably need to change 
"~/bin/rem" line near the top to the path to your "rem" binary above.

#!/usr/bin/env python

import subprocess

def rem(args):
'''Execute the 'rem' command with whatever arguments passed and capture 
output'''
cmd = "~/bin/rem " + args + " |perl -p -e 's/[[:^ascii:]]//g'"
value = subprocess.check_output(cmd, shell=True)
return value

def get_lists():
'''Return a list of the list names'''
r = rem("ls")
r = r.split("\n")
r = r[1:-1]  # drop the "Reminders" title and final newline
r = [rr.strip() for rr in r]
l = [rr for rr in r if not rr[0].isdigit()]
return l

def get_num_items(lists):
'''Return an integer vector with the number of items in each list'''
n = []
for l in lists:
i = rem("ls " + l)
i = i.split("\n")
i = i[2:-1]  # drop the "Reminders" title and final newline
n.append(len(i))
return n

def reminder_item_to_task(list, item, depth=2, TODO=False):
task = rem("cat " + list + " " + str(item))
task = task.split("\n")[:-1]

TODO = "TODO " if TODO else ""

title = task[0].split(": ")[1:]
title = ''.join(title)
title = '*'*depth + " " + TODO + title

depth += 1

meta = task[2:4]
meta = [m.replace('\t','') for m in meta]
meta = [' '*depth + m for m in meta]
meta = '\n'.join(meta)

notes = task[4:]
if len(notes) == 0:
notes = ''
else:
notes[0] = notes[0].split(": ")[1]
notes = [' '*depth + n for n in notes]
notes = '\n'.join(notes)

return title + "\n" + meta + "\n" + notes

if __name__ == "__main__":
lists = get_lists()
num = get_num_items(lists)
for l,n in zip(lists,num):
for i in range(n):
t = reminder_item_to_task(l, i+1, TODO=True)
print t


5) Customize the following "rem.sh" script that should run the "rem.py" and 
produce an Org file. This Org file is tagged REFILE (something I use in my 
Agenda to help me refile MobilOrg generated items).



#!/usr/bin/env bash

SRC=~/tmp/rem.org
DEST=~/Documents/Org/rem.org

echo "# -*- coding: utf-8; eval: (auto-revert-mode 1); -*-" > ${SRC}
echo "#+FILETAGS: REFILE" >> ${SRC}
/Users/mankoff/bin/rem.py >> ${SRC}

# check if it changed
if ! cmp ${SRC} ${DEST} > /dev/null 2>&1
then
cp ${SRC} ${DEST}
fi


6) Set up a LaunchAgent plist (here com.kenmankoff.rem2org.plist) so that any 
reminders are automatically imported into Org. This file goes into 
~/Library/LaunchAgents and is also customized for your paths...


http://www.apple.com/DTDs/PropertyList-1.0.dtd";>


Label
com.kenmankoff.rem2org
ProgramArguments

/Users/mankoff/bin/rem.sh

WatchPaths

/Users/mankoff/Library/Calendars/




7) Load the LaunchAgent with "launchctl load com.kenmankoff.rem2org.plist"

8) Add a section to your Agenda so that "REFILE" tags items show up:

   (tags "REFILE" ((org-agenda-overriding-header "REFILE")))

9) Add an item on your phone, or check one off. Refresh your Agenda. Items 
should appear/disappear.


Hope someone finds this useful,

  -k.




[O] Org-lint (was: Org-lint and #+call lines)

2015-05-28 Thread Karl Voit
* Thomas S. Dye  wrote:
>
> Org-lint is a big help picking up an old project.  Thanks Nicolas.

Hey, I missed org-lint so far.

However, I was desperately asking for an Org-mode syntax validation
multiple times for a long time.[1]

Who do I have to contact, when I've got ideas of checks that
corrupted my Org-mode files? 

For example, I have the issue that once upon a Org-mode-Git-
checkout, the property drawers got corrupted over time: duplicate
LOGBOOKs and order of LOGBOOK and PROPERTIES is switched. I noticed
it, when many drawers were already broken. I still find them in my
files from time to time :-(

Another one would be duplicate IDs.

[1] http://thread.gmane.org/gmane.emacs.orgmode/84494/focus=84864
and others

-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
   > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github




Re: [O] How to end a :session?

2015-05-28 Thread Rainer M Krug
Andreas Leha  writes:

> Rainer M Krug  writes:
>> Andreas Leha  writes:
>>
>>> Hi Rainer,
>>>
>>> Rainer M Krug  writes:
 Andreas Leha  writes:

> Hi Rainer,

 Hi Andreas,

>
> Rainer M Krug  writes:
>> Christopher Witte  writes:
>>
>>> perhaps what you want is a named session, see
>>> http://orgmode.org/manual/session.html
>>
>> Sure - that's what I have.
>>
>> But how can I close the named session when I don't need it anymore, or
>> want to start, the next time I use the named session, with a new
>> session?
>>
>>
>>>
>>> On 28 May 2015 at 10:44, Rainer M Krug  wrote:
>>>
 Hi

 I can start a session as follow:

 --8<---cut here---start->8---
 #+begin_src R :session Test
 cat("Session Test\n")
 #+end_src
 --8<---cut here---end--->8---

 Now I hava an R session named *Test*. But how can I closes this 
 session?
 I thought about just quitting R

 --8<---cut here---start->8---
 #+begin_src R :session Test
 q(save = "no)
 #+end_src
 --8<---cut here---end--->8---

 but this does not return as ESS is waiting for the prompt (">").

 Is there a way of closing the session *Test* and close the buffer?

 My reasoning is that I want to do different longer analysis in one org
 file and start each in its own session, i.e. clean R. But as they
 involve several steps, I don't want to put them into one code block.

 So I have several code blocks which I want to execute in a "throw away
 session" which I would like to discard afterwards.

 So I am looking for something like

 #+CLOSE_SESSION Test

 which would then close the session *Test*

 Is something like this possible at the moment?

>
> How about
>
> #+name: killRsession
> #+begin_src emacs-lisp :var rsession="*myR*" :results none
> (progn
>   (switch-to-buffer rsession)
>   (ess-quit)
>   (sleep-for 1)
>   (kill-buffer))
> #+end_src
>
>
> #+call: killRsession("*myR*") :results none

 Thanks - this works. But I get an error which says:

 ,
 | save-excursion: Wrong type argument: integer-or-marker-p, nil
 `

 Any suggestion on how to avoid this?

>>>
>>> I do not see that error, so hard to say.  Do you have a backtrace?  Wild
>>> guess: Maybe the ess-quit changed?  What version of ess are you using?
>>
>> ess-15.03
>>
>
> I am on ess-15.09-devel.

That might explain. For some time, I was using the git version (and I
still update it daily) but I was quite a few times bitten by changes /
bugs so I decided to use the latest stable release of ESS.

>
>>>
>>> Note, that this could be improved by replacing the (sleep-for 1) with
>>> something that actually waits until R has quit...
>>
>> I can live with the error for now, but I might look into it some time
>> later.
>>
>
> Fine.
>
> Andreas
>
>

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature


Re: [O] How to end a :session?

2015-05-28 Thread Andreas Leha
Rainer M Krug  writes:
> Andreas Leha  writes:
>
>> Hi Rainer,
>>
>> Rainer M Krug  writes:
>>> Andreas Leha  writes:
>>>
 Hi Rainer,
>>>
>>> Hi Andreas,
>>>

 Rainer M Krug  writes:
> Christopher Witte  writes:
>
>> perhaps what you want is a named session, see
>> http://orgmode.org/manual/session.html
>
> Sure - that's what I have.
>
> But how can I close the named session when I don't need it anymore, or
> want to start, the next time I use the named session, with a new
> session?
>
>
>>
>> On 28 May 2015 at 10:44, Rainer M Krug  wrote:
>>
>>> Hi
>>>
>>> I can start a session as follow:
>>>
>>> --8<---cut here---start->8---
>>> #+begin_src R :session Test
>>> cat("Session Test\n")
>>> #+end_src
>>> --8<---cut here---end--->8---
>>>
>>> Now I hava an R session named *Test*. But how can I closes this session?
>>> I thought about just quitting R
>>>
>>> --8<---cut here---start->8---
>>> #+begin_src R :session Test
>>> q(save = "no)
>>> #+end_src
>>> --8<---cut here---end--->8---
>>>
>>> but this does not return as ESS is waiting for the prompt (">").
>>>
>>> Is there a way of closing the session *Test* and close the buffer?
>>>
>>> My reasoning is that I want to do different longer analysis in one org
>>> file and start each in its own session, i.e. clean R. But as they
>>> involve several steps, I don't want to put them into one code block.
>>>
>>> So I have several code blocks which I want to execute in a "throw away
>>> session" which I would like to discard afterwards.
>>>
>>> So I am looking for something like
>>>
>>> #+CLOSE_SESSION Test
>>>
>>> which would then close the session *Test*
>>>
>>> Is something like this possible at the moment?
>>>

 How about

 #+name: killRsession
 #+begin_src emacs-lisp :var rsession="*myR*" :results none
 (progn
   (switch-to-buffer rsession)
   (ess-quit)
   (sleep-for 1)
   (kill-buffer))
 #+end_src


 #+call: killRsession("*myR*") :results none
>>>
>>> Thanks - this works. But I get an error which says:
>>>
>>> ,
>>> | save-excursion: Wrong type argument: integer-or-marker-p, nil
>>> `
>>>
>>> Any suggestion on how to avoid this?
>>>
>>
>> I do not see that error, so hard to say.  Do you have a backtrace?  Wild
>> guess: Maybe the ess-quit changed?  What version of ess are you using?
>
> ess-15.03
>

I am on ess-15.09-devel.

>>
>> Note, that this could be improved by replacing the (sleep-for 1) with
>> something that actually waits until R has quit...
>
> I can live with the error for now, but I might look into it some time
> later.
>

Fine.

Andreas




Re: [O] How to end a :session?

2015-05-28 Thread Rainer M Krug
Andreas Leha  writes:

> Hi Rainer,
>
> Rainer M Krug  writes:
>> Andreas Leha  writes:
>>
>>> Hi Rainer,
>>
>> Hi Andreas,
>>
>>>
>>> Rainer M Krug  writes:
 Christopher Witte  writes:

> perhaps what you want is a named session, see
> http://orgmode.org/manual/session.html

 Sure - that's what I have.

 But how can I close the named session when I don't need it anymore, or
 want to start, the next time I use the named session, with a new
 session?


>
> On 28 May 2015 at 10:44, Rainer M Krug  wrote:
>
>> Hi
>>
>> I can start a session as follow:
>>
>> --8<---cut here---start->8---
>> #+begin_src R :session Test
>> cat("Session Test\n")
>> #+end_src
>> --8<---cut here---end--->8---
>>
>> Now I hava an R session named *Test*. But how can I closes this session?
>> I thought about just quitting R
>>
>> --8<---cut here---start->8---
>> #+begin_src R :session Test
>> q(save = "no)
>> #+end_src
>> --8<---cut here---end--->8---
>>
>> but this does not return as ESS is waiting for the prompt (">").
>>
>> Is there a way of closing the session *Test* and close the buffer?
>>
>> My reasoning is that I want to do different longer analysis in one org
>> file and start each in its own session, i.e. clean R. But as they
>> involve several steps, I don't want to put them into one code block.
>>
>> So I have several code blocks which I want to execute in a "throw away
>> session" which I would like to discard afterwards.
>>
>> So I am looking for something like
>>
>> #+CLOSE_SESSION Test
>>
>> which would then close the session *Test*
>>
>> Is something like this possible at the moment?
>>
>>>
>>> How about
>>>
>>> #+name: killRsession
>>> #+begin_src emacs-lisp :var rsession="*myR*" :results none
>>> (progn
>>>   (switch-to-buffer rsession)
>>>   (ess-quit)
>>>   (sleep-for 1)
>>>   (kill-buffer))
>>> #+end_src
>>>
>>>
>>> #+call: killRsession("*myR*") :results none
>>
>> Thanks - this works. But I get an error which says:
>>
>> ,
>> | save-excursion: Wrong type argument: integer-or-marker-p, nil
>> `
>>
>> Any suggestion on how to avoid this?
>>
>
> I do not see that error, so hard to say.  Do you have a backtrace?  Wild
> guess: Maybe the ess-quit changed?  What version of ess are you using?

ess-15.03

>
> Note, that this could be improved by replacing the (sleep-for 1) with
> something that actually waits until R has quit...

I can live with the error for now, but I might look into it some time
later.

Thanks a lot,

Rainer

>
> - Andreas
>
>

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature


[O] [BUG] in last org in indentation of source blocks

2015-05-28 Thread Rainer M Krug
I reralised this morning that there eems to be a bug introduced in one
of the last commits which causes repeted editing of source blocks to
indent more each time the are edited (C-').

Original:
,
| #+begin_src sh
| echo 2
| #+end_src
`

After C-' and back again
,
| #+begin_src sh
|   echo 2
| #+end_src
`

After second C-' and back
,
| #+begin_src sh
| echo 2
| #+end_src
`

When C-', the indirect buffer has the same indentation as the source
block, but when switching back, two more spaces are added.

Cheers,

Rainer

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature


Re: [O] ob-sed

2015-05-28 Thread Bjarte Johansen
I think I have addressed all your comments in the attached patch.

Regards,
Bjarte




0001-Org-Babel-now-supports-sed-scripts.patch
Description: Binary data


Re: [O] How to end a :session?

2015-05-28 Thread Andreas Leha
Hi Rainer,

Rainer M Krug  writes:
> Andreas Leha  writes:
>
>> Hi Rainer,
>
> Hi Andreas,
>
>>
>> Rainer M Krug  writes:
>>> Christopher Witte  writes:
>>>
 perhaps what you want is a named session, see
 http://orgmode.org/manual/session.html
>>>
>>> Sure - that's what I have.
>>>
>>> But how can I close the named session when I don't need it anymore, or
>>> want to start, the next time I use the named session, with a new
>>> session?
>>>
>>>

 On 28 May 2015 at 10:44, Rainer M Krug  wrote:

> Hi
>
> I can start a session as follow:
>
> --8<---cut here---start->8---
> #+begin_src R :session Test
> cat("Session Test\n")
> #+end_src
> --8<---cut here---end--->8---
>
> Now I hava an R session named *Test*. But how can I closes this session?
> I thought about just quitting R
>
> --8<---cut here---start->8---
> #+begin_src R :session Test
> q(save = "no)
> #+end_src
> --8<---cut here---end--->8---
>
> but this does not return as ESS is waiting for the prompt (">").
>
> Is there a way of closing the session *Test* and close the buffer?
>
> My reasoning is that I want to do different longer analysis in one org
> file and start each in its own session, i.e. clean R. But as they
> involve several steps, I don't want to put them into one code block.
>
> So I have several code blocks which I want to execute in a "throw away
> session" which I would like to discard afterwards.
>
> So I am looking for something like
>
> #+CLOSE_SESSION Test
>
> which would then close the session *Test*
>
> Is something like this possible at the moment?
>
>>
>> How about
>>
>> #+name: killRsession
>> #+begin_src emacs-lisp :var rsession="*myR*" :results none
>> (progn
>>   (switch-to-buffer rsession)
>>   (ess-quit)
>>   (sleep-for 1)
>>   (kill-buffer))
>> #+end_src
>>
>>
>> #+call: killRsession("*myR*") :results none
>
> Thanks - this works. But I get an error which says:
>
> ,
> | save-excursion: Wrong type argument: integer-or-marker-p, nil
> `
>
> Any suggestion on how to avoid this?
>

I do not see that error, so hard to say.  Do you have a backtrace?  Wild
guess: Maybe the ess-quit changed?  What version of ess are you using?

Note, that this could be improved by replacing the (sleep-for 1) with
something that actually waits until R has quit...

- Andreas




Re: [O] How to end a :session?

2015-05-28 Thread Rainer M Krug
Andreas Leha  writes:

> Hi Rainer,

Hi Andreas,

>
> Rainer M Krug  writes:
>> Christopher Witte  writes:
>>
>>> perhaps what you want is a named session, see
>>> http://orgmode.org/manual/session.html
>>
>> Sure - that's what I have.
>>
>> But how can I close the named session when I don't need it anymore, or
>> want to start, the next time I use the named session, with a new
>> session?
>>
>>
>>>
>>> On 28 May 2015 at 10:44, Rainer M Krug  wrote:
>>>
 Hi

 I can start a session as follow:

 --8<---cut here---start->8---
 #+begin_src R :session Test
 cat("Session Test\n")
 #+end_src
 --8<---cut here---end--->8---

 Now I hava an R session named *Test*. But how can I closes this session?
 I thought about just quitting R

 --8<---cut here---start->8---
 #+begin_src R :session Test
 q(save = "no)
 #+end_src
 --8<---cut here---end--->8---

 but this does not return as ESS is waiting for the prompt (">").

 Is there a way of closing the session *Test* and close the buffer?

 My reasoning is that I want to do different longer analysis in one org
 file and start each in its own session, i.e. clean R. But as they
 involve several steps, I don't want to put them into one code block.

 So I have several code blocks which I want to execute in a "throw away
 session" which I would like to discard afterwards.

 So I am looking for something like

 #+CLOSE_SESSION Test

 which would then close the session *Test*

 Is something like this possible at the moment?

>
> How about
>
> #+name: killRsession
> #+begin_src emacs-lisp :var rsession="*myR*" :results none
> (progn
>   (switch-to-buffer rsession)
>   (ess-quit)
>   (sleep-for 1)
>   (kill-buffer))
> #+end_src
>
>
> #+call: killRsession("*myR*") :results none

Thanks - this works. But I get an error which says:

,
| save-excursion: Wrong type argument: integer-or-marker-p, nil
`

Any suggestion on how to avoid this?

Thanks,

Rainer
>
> Andreas
>
>

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature


Re: [O] Marking/highlighting text temporarily

2015-05-28 Thread Alan Schmitt
On 2015-05-18 23:42, Marcin Borkowski  writes:

> On 2015-04-24, at 08:19, Vikas Rawal  wrote:
>
>> I am revising a long book manuscript, and would like to mark parts of text
>> (not just the headlines) just to remind myself that these need to be dealt
>> with.
>>
>> What could be an the easy way of doing it?
>
> Well, it seems that the thread went somewhere else (completely), but it
> just occured to me that you might want Bookmark+ (in case nobody
> mentioned it).  You have normal Emacs bookmarks but on Drew-steroids,
> among others you can /highlight/ all bookmarks in a buffer.  (And AFAIR
> you can have a dedicated bookmark file for e.g. one project, so that you
> effectively have "categories" of bookmarks.)

Is it possible to collaborate using this? I guess you would need one
bookmark file per project, and add that file to the repository …

Thanks,

Alan

-- 
OpenPGP Key ID : 040D0A3B4ED2E5C7


signature.asc
Description: PGP signature


Re: [O] How to end a :session?

2015-05-28 Thread Andreas Leha
Hi Rainer,

Rainer M Krug  writes:
> Christopher Witte  writes:
>
>> perhaps what you want is a named session, see
>> http://orgmode.org/manual/session.html
>
> Sure - that's what I have.
>
> But how can I close the named session when I don't need it anymore, or
> want to start, the next time I use the named session, with a new
> session?
>
>
>>
>> On 28 May 2015 at 10:44, Rainer M Krug  wrote:
>>
>>> Hi
>>>
>>> I can start a session as follow:
>>>
>>> --8<---cut here---start->8---
>>> #+begin_src R :session Test
>>> cat("Session Test\n")
>>> #+end_src
>>> --8<---cut here---end--->8---
>>>
>>> Now I hava an R session named *Test*. But how can I closes this session?
>>> I thought about just quitting R
>>>
>>> --8<---cut here---start->8---
>>> #+begin_src R :session Test
>>> q(save = "no)
>>> #+end_src
>>> --8<---cut here---end--->8---
>>>
>>> but this does not return as ESS is waiting for the prompt (">").
>>>
>>> Is there a way of closing the session *Test* and close the buffer?
>>>
>>> My reasoning is that I want to do different longer analysis in one org
>>> file and start each in its own session, i.e. clean R. But as they
>>> involve several steps, I don't want to put them into one code block.
>>>
>>> So I have several code blocks which I want to execute in a "throw away
>>> session" which I would like to discard afterwards.
>>>
>>> So I am looking for something like
>>>
>>> #+CLOSE_SESSION Test
>>>
>>> which would then close the session *Test*
>>>
>>> Is something like this possible at the moment?
>>>

How about

--8<---cut here---start->8---
#+name: killRsession
#+begin_src emacs-lisp :var rsession="*myR*" :results none
(progn
  (switch-to-buffer rsession)
  (ess-quit)
  (sleep-for 1)
  (kill-buffer))
#+end_src


#+call: killRsession("*myR*") :results none
--8<---cut here---end--->8---

Andreas




[O] Easy to use asking for Or-gmode property values (e.g., for Org-contacts)

2015-05-28 Thread Karl Voit
Hi!

I am using Org-contacts that way, that I copy new information from
external sources and move them to the properties afterwards:

: ** Firstname Lastname  :FirstnameLastname:
: :PROPERTIES:
: :TYPE:
: :TITLE:
: :EMAIL: firstn...@company.com
: :URL:
: :MOBILE: 0043/
: :HOMEPHONE:
: :WORKPHONE:
: :PHONE:
: :COMPANY: This Company
: :STREET: Companystreet 42
: :POSTALCODE: 8010
: :CITY: Thiscity
: :COUNTRY: Österreich
: :PHOTOGRAPH: [[photo:FirstnameLastname.jpg]]
: :BORN: 1970-12-31
: :ITOLDTHEM_EMAIL: thisort...@mydomain.com
: :ITOLDTHEM_ADDRESS:
: :ITOLDTHEM_PHONE:
: :ADDRESS_CHANGE_METHOD: email
: :CREATED:  [2015-05-27 Wed 19:46]
: :END:
:
: - <2013-01-13 Fri> met at dinner party
:   - This old company
:   - firstn...@oldcompany.com
: - <2015-05-27 Wed> contact from XING with new data
:   - This Company
:   - firstn...@company.com
:   - Companystreet 42, 8010 Thiscity
:   - he is born on December 31st, 1970

This way, I do have the whole history below the properties and the
most current information.

The task of adding information is tedious: copy & paste from external
sources and then copy & paste to the properties accordingly.

This is why I came up with this idea: how about I paste new
information at the end of and then call a function which helps me a
lot:

- ask for each property (or a set of pre-defined properties)
  - prompt property name
  - let the user mark a region using keyboard or mouse
  - if user presses confirmation keyoard shortcut (return?)
- if region: copy the region and set it as the new content for the current
  property (overwriting any old property settings)
- if no region is set: do not change property

The workflow would improve a lot! And I do guess that this might be a
very handy function for lots of other purposes as well: ask me for all
or some properties!

With my very limited understanding of elisp: can this (easily) done?

Is there a code snippet which does similar stuff?

-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
   > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github




Re: [O] How to end a :session?

2015-05-28 Thread Rainer M Krug
Christopher Witte  writes:

> perhaps what you want is a named session, see
> http://orgmode.org/manual/session.html

Sure - that's what I have.

But how can I close the named session when I don't need it anymore, or
want to start, the next time I use the named session, with a new
session?


>
> On 28 May 2015 at 10:44, Rainer M Krug  wrote:
>
>> Hi
>>
>> I can start a session as follow:
>>
>> --8<---cut here---start->8---
>> #+begin_src R :session Test
>> cat("Session Test\n")
>> #+end_src
>> --8<---cut here---end--->8---
>>
>> Now I hava an R session named *Test*. But how can I closes this session?
>> I thought about just quitting R
>>
>> --8<---cut here---start->8---
>> #+begin_src R :session Test
>> q(save = "no)
>> #+end_src
>> --8<---cut here---end--->8---
>>
>> but this does not return as ESS is waiting for the prompt (">").
>>
>> Is there a way of closing the session *Test* and close the buffer?
>>
>> My reasoning is that I want to do different longer analysis in one org
>> file and start each in its own session, i.e. clean R. But as they
>> involve several steps, I don't want to put them into one code block.
>>
>> So I have several code blocks which I want to execute in a "throw away
>> session" which I would like to discard afterwards.
>>
>> So I am looking for something like
>>
>> #+CLOSE_SESSION Test
>>
>> which would then close the session *Test*
>>
>> Is something like this possible at the moment?
>>
>> Rainer
>>
>> --
>> Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
>> Biology, UCT), Dipl. Phys. (Germany)
>>
>> Centre of Excellence for Invasion Biology
>> Stellenbosch University
>> South Africa
>>
>> Tel :   +33 - (0)9 53 10 27 44
>> Cell:   +33 - (0)6 85 62 59 98
>> Fax :   +33 - (0)9 58 10 27 44
>>
>> Fax (D):+49 - (0)3 21 21 25 22 44
>>
>> email:  rai...@krugs.de
>>
>> Skype:  RMkrug
>>
>> PGP: 0x0F52F982
>>

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature


Re: [O] How to end a :session?

2015-05-28 Thread Christopher Witte
perhaps what you want is a named session, see
http://orgmode.org/manual/session.html

On 28 May 2015 at 10:44, Rainer M Krug  wrote:

> Hi
>
> I can start a session as follow:
>
> --8<---cut here---start->8---
> #+begin_src R :session Test
> cat("Session Test\n")
> #+end_src
> --8<---cut here---end--->8---
>
> Now I hava an R session named *Test*. But how can I closes this session?
> I thought about just quitting R
>
> --8<---cut here---start->8---
> #+begin_src R :session Test
> q(save = "no)
> #+end_src
> --8<---cut here---end--->8---
>
> but this does not return as ESS is waiting for the prompt (">").
>
> Is there a way of closing the session *Test* and close the buffer?
>
> My reasoning is that I want to do different longer analysis in one org
> file and start each in its own session, i.e. clean R. But as they
> involve several steps, I don't want to put them into one code block.
>
> So I have several code blocks which I want to execute in a "throw away
> session" which I would like to discard afterwards.
>
> So I am looking for something like
>
> #+CLOSE_SESSION Test
>
> which would then close the session *Test*
>
> Is something like this possible at the moment?
>
> Rainer
>
> --
> Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
> Biology, UCT), Dipl. Phys. (Germany)
>
> Centre of Excellence for Invasion Biology
> Stellenbosch University
> South Africa
>
> Tel :   +33 - (0)9 53 10 27 44
> Cell:   +33 - (0)6 85 62 59 98
> Fax :   +33 - (0)9 58 10 27 44
>
> Fax (D):+49 - (0)3 21 21 25 22 44
>
> email:  rai...@krugs.de
>
> Skype:  RMkrug
>
> PGP: 0x0F52F982
>


Re: [O] org-preview-latex-fragment ignores \includes in the LATEX_HEADER

2015-05-28 Thread Stefan Otte
Hey,

"\input" does not solve the problem. Still no preview images. (The pdf
export still works as expected.)


Best,
 Stefan



On Wed, May 27, 2015 at 3:37 PM, Robert Klein  wrote:
> Hi,
>
> On Wed, 27 May 2015 15:02:02 +0200
> Stefan Otte  wrote:
>
>> Hey,
>>
>> I'm using orgmode with lots of LaTeX for equations. A typical document
>> start with
>>
>>   #+TITLE: Some Title
>>   #+LaTeX_HEADER: \include{commands}
>>
>> commands.tex contains commands like:
>>   \newcommand{\RRR}{{\mathbb{R}}}
>>
>> The pdf export works flawlessly, however `org-preview-latex-fragment`
>> seems to ignore "\include{commands}", i.e., equations that use
>> commands that are defined in commands.tex are rendered as blank/empty
>> image.
>>
>> Is it the intended behavior that `org-preview-latex-fragment` ignores
>> "\include", is it a bug, or is there a better way to do it?
>>
>
> afaik \include doesn't work in LaTeX headers; you'll have to use \input
> there.
>
> Could you try to use \input?
>
> Best regards
> Robert



[O] How to end a :session?

2015-05-28 Thread Rainer M Krug
Hi

I can start a session as follow:

--8<---cut here---start->8---
#+begin_src R :session Test
cat("Session Test\n")
#+end_src
--8<---cut here---end--->8---

Now I hava an R session named *Test*. But how can I closes this session?
I thought about just quitting R

--8<---cut here---start->8---
#+begin_src R :session Test
q(save = "no)
#+end_src
--8<---cut here---end--->8---

but this does not return as ESS is waiting for the prompt (">").

Is there a way of closing the session *Test* and close the buffer?

My reasoning is that I want to do different longer analysis in one org
file and start each in its own session, i.e. clean R. But as they
involve several steps, I don't want to put them into one code block.

So I have several code blocks which I want to execute in a "throw away
session" which I would like to discard afterwards.

So I am looking for something like

#+CLOSE_SESSION Test

which would then close the session *Test*

Is something like this possible at the moment?

Rainer

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature


Re: [O] How to create agenda which ignores headings with deadline/scheduled dates older than 3 months

2015-05-28 Thread rene
Nick Dokos  gmail.com> writes:

> [Not sure why, but quoting the OP's message did not work - I had to do
> it by hand - I wonder if the problem is with the message or my setup:
> if someone could verify, I'd appreciate it.]
> 
> "Martin Beck"  web.de> writes:
> 
> > how can I set up an agenda view in org-mode which does NOT show old
> > entries which contain scheduled or deadline dates older than 3 months? 
> 
> C-h v org-agenda-todo-ignore-timestamp RET
> C-h v org-agenda-todo-ignore-scheduled RET
> C-h v org-agenda-todo-ignore-deadlines RET

How can you show entries that has a deadline date but no scheduled date?

If it bears a scheduled date then I don't want to show that entry.