Re: [O] args-out-of-range #

2016-03-19 Thread John Kitchin
I pushed a fix for this last night. I don't totally understand why it happens and the fix is to not run the advice in the agenda buffer. On Wednesday, March 16, 2016, Nicolas Goaziou wrote: > Hello, > > br...@uwaterloo.ca writes: > > > This message just started appearing today when I open an ag

Re: [O] args-out-of-range #

2016-03-19 Thread Nicolas Goaziou
Hello, br...@uwaterloo.ca writes: > This message just started appearing today when I open an agenda view > "C-c a a". It is not obvious to me what I am doing or have done > differently, and I would appreciate some advice how to diagnose the > problem: > Emacs: 24.5.1 > Orgmode: 8.3.4-5 (20160229

[O] args-out-of-range #

2016-03-03 Thread britt
This message just started appearing today when I open an agenda view "C-c a a". It is not obvious to me what I am doing or have done differently, and I would appreciate some advice how to diagnose the problem: Emacs: 24.5.1 Orgmode: 8.3.4-5 (20160229 elpa) Thank you, -- Britt The error trace foll

Re: [O] Args out of range: #, 0, 1

2015-01-14 Thread Sebastien Vauban
Nicolas Richard wrote: > Sebastien Vauban writes: >> This still leaves me with one question: how do we reproduce the >> problem? What's the trigger for it? > > Mostly luck. i.e. you need to have called a function that callled > string-match on a string, with a regexp containing (at least) > 4 grou

Re: [O] Args out of range: #, 0, 1

2015-01-13 Thread Nicolas Richard
Sebastien Vauban writes: > This still leaves me with one question: how do we reproduce the problem? > What's the trigger for it? Mostly luck. i.e. you need to have called a function that callled string-match on a string, with a regexp containing (at least) 4 grouping constructs, and the 4th mat

Re: [O] Args out of range: #, 0, 1

2015-01-13 Thread Sebastien Vauban
Hello both Nicolas, Nicolas Richard wrote: > Sebastien Vauban writes: >> I tried to edebug the function `org-babel-demarcate-block' and the >> error arises quite at the beginning: on the `match-string 0', on the >> second line of the `let*'. > > The error means we tried to access portions from 0 t

Re: [O] Args out of range: #, 0, 1

2015-01-13 Thread Nicolas Goaziou
Hello, Sebastien Vauban writes: > I sometimes (or often?) have the above error when pressing `C-c C-v C-d' > onto some region (to put it in a code block). > > Org is supposed to ask me which language it is for, and then wrap my > selection with the right #+begin/end_src markers. Instead, I get

Re: [O] Args out of range: #, 0, 1

2015-01-13 Thread Nicolas Richard
Hello, Sebastien Vauban writes: > I tried to edebug the function `org-babel-demarcate-block' and the error > arises quite at the beginning: on the `match-string 0', on the second > line of the `let*'. The error means we tried to access portions from 0 to 1 in a buffer. That doesn't exist. The

[O] Args out of range: #, 0, 1

2015-01-13 Thread Sebastien Vauban
Hello, I sometimes (or often?) have the above error when pressing `C-c C-v C-d' onto some region (to put it in a code block). Org is supposed to ask me which language it is for, and then wrap my selection with the right #+begin/end_src markers. Instead, I get the "args out of range" error. I tri

Re: [O] Args out of range: 0, 1

2013-06-04 Thread Bastien
Hi, SabreWolfy writes: > Emacs/R is aborting running/exporting an R code block with the message: > > Args out of range: 0, 1 > > in the mini-buffer line. This is triggered when I try to use ascii or print > to output a data structure. I've searched for this error and found it to be > related to

[O] Args out of range: 0, 1

2013-06-04 Thread SabreWolfy
Emacs/R is aborting running/exporting an R code block with the message: Args out of range: 0, 1 in the mini-buffer line. This is triggered when I try to use ascii or print to output a data structure. I've searched for this error and found it to be related to converting HTML to text. with a number