[O] Trouble evaluating R source code blocks with C-c C-c

[Vikas Rawal]

I face a strange problem with evaluating R source code blocks. Occasionally, 
they take much longer to produce the results when I try to evaluate them with 
C-c C-c. On the other hand, if I do C-c ‘, go to a temporary R buffer, and 
evaluate the code, everything works fine. In face, when I use C-c C-c, the 
session would sometimes get stuck. Then I have to stop the process using C-g, I 
find that the code had run in R, but the result was not being inserted in Org 
buffer.

Has anyone else faced this problem?

I am on OS-X, Emacs 24, Org-mode version 8.3.4 (release_8.3.4-748-g7e320e, and 
ess-version: 15.09-devel [elpa: 20150913.638]

Vikas

Re: [O] [ANN] Remove XEmacs compatibility layer

[Uwe Brauer]

>>> "Nicolas" == Nicolas Goaziou  writes:

   > Hello,
   > Georgiy Tugai  writes:

   >> If I may ask, was there any particular reason for ditching XEmacs
   >> compatibility?

   > I didn't ditch XEmacs compatibility. Org hadn't compiled on XEmacs for
   > a long time already. Org was broken on XEmacs, and no one volunteered to
   > solve it. Barely anyone even reported it.

This is not entirely true. I got org 8.0.X to work with Xemacs 21.5.X
and Michael Sperber also got to work, I think an even  more recent version
of org mode, but I do not remember the details. It is true however that
a lot of  functionalities  were missing compared to GNU emacs 25.1 which I use
currently.

It also true that no Xemacs hacker really was willing to help out the
compatibility problems (so removing compatibility code is not a big
surprise and in fact  it has happened before with gnus, and as it is most
likely  to happen with auctex in the near future). But given the
email exchange on Xemacs beta in October last year about closing the
whole Xemacs project, this comes barely as a surprise.

Uwe Brauer 

Re: [O] History list for %^{...} in capture

[Aaron Ecay]

Hi Phil,

2016ko maiatzak 20an, Phil Hudson-ek idatzi zuen:
> 
> Arising from a discussion here a couple of weeks ago, I'm thinking about
> how best to add a history list to org-capture's current
> %^{prompt|default|choice2|...|choiceN} escape syntax. Here's my thinking
> so far.

[...]

> 
> WDYT? Good idea? Too complex? Too "busy"? Useful? Not useful?

IMO, it’s very busy, and for a scenario that’s likely to be of use in
only a small number of circumstances.  I think it would be better to
just use a %(...) construct to call an elisp function which does the
completion exactly as you desire for your own usecase.

-- 
Aaron Ecay

Re: [O] Trouble evaluating R source code blocks with C-c C-c

[John Hendy]

Could you give a minimal example? The behavior does ring a bell, but I
can't recall what the solution might have been. I'd be happy to try
and reproduce if you'd like.

I think my typical go-to is to wipe ESS and re-download/make... That's
all I'm good for without more info.


Sorry!
John

On Thu, May 26, 2016 at 9:33 AM, Vikas Rawal
 wrote:
> I face a strange problem with evaluating R source code blocks. Occasionally, 
> they take much longer to produce the results when I try to evaluate them with 
> C-c C-c. On the other hand, if I do C-c ‘, go to a temporary R buffer, and 
> evaluate the code, everything works fine. In face, when I use C-c C-c, the 
> session would sometimes get stuck. Then I have to stop the process using C-g, 
> I find that the code had run in R, but the result was not being inserted in 
> Org buffer.
>
> Has anyone else faced this problem?
>
> I am on OS-X, Emacs 24, Org-mode version 8.3.4 (release_8.3.4-748-g7e320e, 
> and ess-version: 15.09-devel [elpa: 20150913.638]
>
> Vikas
>
>
>
>

Re: [O] BUG: org-beamer-select-environment select multiple environments not working?

[Rainer M Krug]

John Hendy  writes:

> Just to comment on the original attempt, block and column (which is |,
> not c which is columnS) are not mutually exclusive. I just did a
> presentation and used both together. I'm not sure on the use-case for
> columnS, but my structure was two side by side columns in a slide:
>
> #+begin_src org
> * slide
> ** col1  :B_block:BMCOL:
>:PROPERTIES:
>:BEAMER_env: block
>:BEAMER_col: 0.5
>:END:
>
> - list
> - of
> - items
>
> ** col2  :B_block:BMCOL:
>:PROPERTIES:
>:BEAMER_env: block
>:BEAMER_col: 0.5
>:END:
>
> [[pic]]
> #+end_src
>
> Probably not that helpful, just wanted to clarify that some
> environments are still compatible (in case someone finds this and
> thinks that *all* multiple combos are not possible anymore).

Is it possible that *only B_* environments are mutually exclusive?

Rainer

>
>
> John
>
>
> On Wed, May 25, 2016 at 3:31 PM, Nicolas Goaziou  
> wrote:
>> Hello,
>>
>> Rasmus  writes:
>>
>>> Not necessarily.  On the top of my head, you could have a column group
>>> with columns inside.  This example used to be possible.  I haven't checked
>>> now.
>>
>> This one is not possible anymore. A column environment implies columns.
>> You can also provide a columns environment explicitly, at a higher
>> level, e.g., to provide specific options.
>>
>> Regards,
>>
>> --
>> Nicolas Goaziou
>>
>

-- 
Rainer M. Krug
email: Rainerkrugsde
PGP: 0x0F52F982


signature.asc
Description: PGP signature

Re: [O] Inquiry about ical2org

[Eric S Fraga]

On Wednesday, 25 May 2016 at 20:33, John Hendy wrote:
> I found ical2org, and implemented it successfully via the "Share

Which ical2org is this?  If it's the awk script I wrote originally, the
repeat handling was written with the assumption that there would be no
end date for the repeat as org cannot handled end dates for repeated
items.

I can try to fix this in the awk script by simply ignoring end dates in
such cases.  Let me know.

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.93.1, Org release_8.3.4-775-g3308a5

Re: [O] org agenda persistent mark

[Nicolas Goaziou]

Hello,

Jesse Johnson  writes:

> When I enable persistent marks while performing bulk actions in
> org-agenda, the marks are always lost after the bulk action. Any idea
> why? I am using org (elpa version 20160516) in upstream emacs (compiled
> 2015-12-22).

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou

[O] B_column does not insert :BEAMER_COL:

[Rainer M Krug]

Hi

When I set the B_column environment, the property :BEAMER_env: is as
expected, automatically set to =column=, but exporting to beamer results
in an error as the environment is is not actually used in the resulting
latex file. The environment is only correctly created, if the
property :BEAMER_COL: is added.

This is counter-intuitive and not obvious. Would it be possible to
add :BEAMER_COL: automatically as well?

Thanks,

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] PATCH: ox: Starting source code export at non-zero (-n value)

[Nicolas Goaziou]

Hello,

Brian Carlson  writes:

> I put the signed paperwork into the mail this evening.

Great.

> Sure. I'll use previous entries as a starting point.
> I was thinking that the entry should go under: Version 9.0/New 
> Features/Export/
> unless there's a more appropriate place in the Document.

I also think this is the correct location.

> Here's what I thought about putting. I can make a patch if that is preferred
> means of submission. If what I've written doesn't make sense let me know.
>
>  Line Numbering in SRC/EXAMPLE blocks support arbitrary start number
> The -n option to SRC and EXAMPLE blocks can now take an numeric argument to 
> specify

"a numeric argument"

> the staring line number for the source or example block. The +n option can now
> take a numeric argument that will be added to the last line number from the
> previous block as the starting point for the SRC/EXAMPLE block.
> #+BEGIN_SRC emacs-lisp -n 20
> ;; this will export with line number 20
> (message "This is line 21")
> #+END_SRC
>
> #+BEGIN_SRC emacs-lisp +n 10
> ;; This will be listed as line 31
> (message "This is line 32")
> #+END_SRC
>
> I realize that the org texinfo manual probably needs to be updated, as well. 
> I'll take a stab at updating that unless 
> someone else wants to take that on.

You're right. You can merge ORG-NEWS modifications into the
documentation patch.

Thank you !

Regards,

-- 
Nicolas Goaziou

Re: [O] B_column does not insert :BEAMER_COL:

[Nicolas Goaziou]

Hello,

Rainer M Krug  writes:

> When I set the B_column environment, the property :BEAMER_env: is as
> expected, automatically set to =column=, but exporting to beamer results
> in an error as the environment is is not actually used in the resulting
> latex file. The environment is only correctly created, if the
> property :BEAMER_COL: is added.
>
> This is counter-intuitive and not obvious. Would it be possible to
> add :BEAMER_COL: automatically as well?

I think the column environment is a left-over for previous
implementation and should be removed. 

Couldn't you use BMCOL instead ("|")?

Regards,

-- 
Nicolas Goaziou

Re: [O] Inquiry about ical2org

[John Hendy]

On Thu, May 26, 2016 at 3:00 PM, John Hendy  wrote:
> On Thu, May 26, 2016 at 2:49 AM, Eric S Fraga  wrote:
>> On Wednesday, 25 May 2016 at 20:33, John Hendy wrote:
>>> I found ical2org, and implemented it successfully via the "Share
>>
>> Which ical2org is this?  If it's the awk script I wrote originally, the
>> repeat handling was written with the assumption that there would be no
>> end date for the repeat as org cannot handled end dates for repeated
>> items.
>
> Whoops -- yes, the awk script. Sorry, now I'm remembering there was a
> ruby version as well.
>
> Here's an example of a recurring meeting I see:
>
> RRULE:FREQ=MONTHLY;UNTIL=20161114T15Z;INTERVAL=1;BYDAY=2MO
> DTSTART;TZID=Central Standard Time:20160613T09
> DTEND;TZID=Central Standard Time:20160613T103000
> DTSTAMP:20160526T195005Z
>
> I'm no awk expert, but I think I make out what's going on... the
> #repetition rule section extracts (among others) the freq (monthly)
> and interval (1) to build a repeater (+1m), though  and rrend using
> the "until" field.

Bah... sorry about that! Accidental tab right before a space sends away!

Anyway, the point is that the repeater is built if there's any
repetition frequency/interval. You also capture the "until" into
rrend. So, the first date is going to feature a +unit, and this code
adds the end:

else if (rrend != "")
date = date ">--<" rrend

I just commented out both sections that add a "-- ", the other
checking for time2 being "". Is that the correct way to go about this?

If so, no need to update. I'll just leave those commented out.

Out of curiosity, how *is* the rrend code supposed to be handling
these? Or what's the use case for building a --?


Thanks!
John


>>
>> I can try to fix this in the awk script by simply ignoring end dates in
>> such cases.  Let me know.
>>
>> --
>> : Eric S Fraga (0xFFFCF67D), Emacs 25.0.93.1, Org release_8.3.4-775-g3308a5

Re: [O] Export to pdf when path name has ~

[Nicolas Goaziou]

Hello,

Stig Brautaset  writes:

> And, indeed, running pdflatex on that file works perfectly fine from the 
> shell:
>
> #+BEGIN_EXAMPLE
> 17:37:57 /tmp> /Library/TeX/texbin/pdflatex ~/Org/TODO.tex
> This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015) (preloaded 
> format=pdflatex)
>  restricted \write18 enabled.
> entering extended mode
> (/Users/stig/Org/TODO.tex
> LaTeX2e <2015/01/01>
>
> [...]
>
> Output written on TODO.pdf (10 pages, 206446 bytes).
> Transcript written on TODO.log.
> #+END_EXAMPLE
>
>
> ... except if you use the full path (rather than the symlink), in which case
> pdflatex chockes on the filename:
>
> #+begin_example
> 17:27:25 /tmp> pdflatex "/Users/stig/Library/Mobile 
> Documents/com~apple~CloudDocs/Org/TODO.tex"
> This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015) (preloaded 
> format=pdflatex)
>  restricted \write18 enabled.
> entering extended mode
> ! I can't find file `"/Users/stig/Library/Mobile Documents/com"'.
>  
>\protect 
> <*> "/Users/stig/Library/Mobile Documents/com~
>   apple~CloudDocs/Org/TODO.tex"

Indeed. It seems pdflatex doesn't like the ~ sign excepted at the
beginning of the filename. It doesn't seem to be Org related though.

In any case, I'm wondering if we really need to send the full canonical
path (as returned by `file-truename') of the tex file to the pdflatex
process.

For example, we could set `default-directory' to the directory of the
tex file and provide only relative filename with %f. If needed, %F may
be used for the full path. I don't think it would introduce
incompatibilities.

WDYT?

Regards,

-- 
Nicolas Goaziou

Re: [O] Inquiry about ical2org

[John Hendy]

On Thu, May 26, 2016 at 2:49 AM, Eric S Fraga  wrote:
> On Wednesday, 25 May 2016 at 20:33, John Hendy wrote:
>> I found ical2org, and implemented it successfully via the "Share
>
> Which ical2org is this?  If it's the awk script I wrote originally, the
> repeat handling was written with the assumption that there would be no
> end date for the repeat as org cannot handled end dates for repeated
> items.

Whoops -- yes, the awk script. Sorry, now I'm remembering there was a
ruby version as well.

Here's an example of a recurring meeting I see:

RRULE:FREQ=MONTHLY;UNTIL=20161114T15Z;INTERVAL=1;BYDAY=2MO
DTSTART;TZID=Central Standard Time:20160613T09
DTEND;TZID=Central Standard Time:20160613T103000
DTSTAMP:20160526T195005Z

I'm no awk expert, but I think I make out what's going on... the
#repetition rule section extracts (among others) the freq (monthly)
and interval (1) to build a repeater (+1m), though  and rrend using
the "until" field.

>
> I can try to fix this in the awk script by simply ignoring end dates in
> such cases.  Let me know.
>
> --
> : Eric S Fraga (0xFFFCF67D), Emacs 25.0.93.1, Org release_8.3.4-775-g3308a5

Re: [O] g [ANN] Remove XEmacs compatibility layer

[Rasmus]

Nicolas Goaziou  writes:

> I finally did the grunt job and removed all XEmacs compatibility in the
> code base (development branch).
>
> On the Emacs side, the following functions are now considered obsolete
> and may trigger innocuous compilation warnings:
>
> - `org-add-hook',
> - `org-decompose-region',
> - `org-detach-overlay',
> - `org-file-equal-p',
> - `org-float-time',
> - `org-indent-line-to',
> - `org-indent-to-column',
> - `org-looking-at-p',
> - `org-looking-back',
> - `org-match-string-no-properties',
> - `org-propertize',
> - `org-re',
> - `org-select-frame-set-input-focus'
>
> The next step is to remove compatibility code for Emacsen older than
> 24.3 release, if anyone feels like spending some time on it during
> a rainy day.

Nice!

There seems to be a lot of clutter in the font code as well, also to befit
quite dated versions of Emacs.

I have started cleaning it up as well, but let’s see if it matures enough.
The goal is to make every face :inherit something else and to have common
faces for all headline elements etc.

Rasmus

-- 
Lasciate ogni speranza, voi che leggete questo.

Re: [O] Inquiry about ical2org

[Ken Mankoff]

On 2016-05-26 at 16:00, John Hendy  wrote:
> On Thu, May 26, 2016 at 2:49 AM, Eric S Fraga  wrote:
>> On Wednesday, 25 May 2016 at 20:33, John Hendy wrote:
>> Which ical2org is this? If it's the awk script I wrote originally,
>> the repeat handling was written with the assumption that there would
>> be no end date for the repeat as org cannot handled end dates for
>> repeated items.
>
> Whoops -- yes, the awk script. Sorry, now I'm remembering there was a
> ruby version as well.

And a Python version: https://github.com/mankoff/ical2org

  -k.

Re: [O] History list for %^{...} in capture

[Philip Hudson]

OK, that's what was shown in that foregoing discussion I mentioned. In
which case, I guess it would be a good idea to copy that
implementation to Worg, or rather copy it to a github repo and link to
that from Worg. Or would it be better going into /contrib? Or its own
ELPA package?

Can't remember whose implementation it was ATM. I'll go back, find it,
and ask them off-list.

(Sorry for top-posting. I'm stuck with GMail for the moment).

On 26 May 2016 at 16:55, Aaron Ecay  wrote:
> Hi Phil,
>
> 2016ko maiatzak 20an, Phil Hudson-ek idatzi zuen:
>>
>> Arising from a discussion here a couple of weeks ago, I'm thinking about
>> how best to add a history list to org-capture's current
>> %^{prompt|default|choice2|...|choiceN} escape syntax. Here's my thinking
>> so far.
>
> [...]
>
>>
>> WDYT? Good idea? Too complex? Too "busy"? Useful? Not useful?
>
> IMO, it’s very busy, and for a scenario that’s likely to be of use in
> only a small number of circumstances.  I think it would be better to
> just use a %(...) construct to call an elisp function which does the
> completion exactly as you desire for your own usecase.
>
> --
> Aaron Ecay



-- 
Phil Hudson   http://hudson-it.ddns.net
@UWascalWabbit PGP/GnuPG ID: 0x887DCA63

Re: [O] Export to pdf when path name has ~

[Stig Brautaset]

Nicolas Goaziou  writes:

> Stig Brautaset  writes:

[...]

>> pdflatex chockes on the filename:
>>
>> #+begin_example
>> 17:27:25 /tmp> pdflatex "/Users/stig/Library/Mobile 
>> Documents/com~apple~CloudDocs/Org/TODO.tex"
>> This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015) (preloaded 
>> format=pdflatex)
>>  restricted \write18 enabled.
>> entering extended mode
>> ! I can't find file `"/Users/stig/Library/Mobile Documents/com"'.
>>  
>>\protect 
>> <*> "/Users/stig/Library/Mobile Documents/com~
>>   apple~CloudDocs/Org/TODO.tex"
>
> Indeed. It seems pdflatex doesn't like the ~ sign excepted at the
> beginning of the filename. It doesn't seem to be Org related though.

No, it does not seem to be Org related. I thought that at first, but
found it failed in a regular terminal too.

> In any case, I'm wondering if we really need to send the full canonical
> path (as returned by `file-truename') of the tex file to the pdflatex
> process.
>
> For example, we could set `default-directory' to the directory of the
> tex file and provide only relative filename with %f. If needed, %F may
> be used for the full path. I don't think it would introduce
> incompatibilities.
>
> WDYT?

That sounds like it would solve my issue, and is what I was hoping to hear :-)

Stig

[O] Problem exporting to pdflatex

[Charles Millar]

Hi,

I just upgraded via git to Emacs 25. My init file loads OK and 
everything "seems" to work, except:


Upon attempting to export to pdflatex following error results

Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
  file-truename(nil)
  find-file-noselect-1(#Thisfiletobeexported.pdf> 
"/mnt/Data/ActiveFiles/FilesAndFormsTemplates/Thisfiletobeexported.pdf" 
nil nil 
"/mnt/Data/ActiveFiles/FilesAndFormsTemplates/Thisfiletobeexported.pdf" 
(17031 2057))
find-file-noselect("/mnt/Data/ActiveFiles/FilesAndFormsTemplates/Thisfiletobeexported.pdf" 
nil nil nil)

find-file-other-window("/mnt/Data/ActiveFiles/FilesAndFormsTemplates/Thisfiletobeexported.pdf")
  org-open-file("./Thisfiletobeexported.pdf")
  (if a (org-latex-export-to-pdf t s v b) (org-open-file 
(org-latex-export-to-pdf nil s v b)))
  (lambda (a s v b) (if a (org-latex-export-to-pdf t s v b) 
(org-open-file (org-latex-export-to-pdf nil s v b(nil nil nil nil)

  org-export-dispatch(nil)
  funcall-interactively(org-export-dispatch nil)
  call-interactively(org-export-dispatch nil nil)
  command-execute(org-export-dispatch)

LMDE Betsy

GNU Emacs 25.1.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 3.14.5) of 
2016-05-26


Org-mode version 8.3.4 (release_8.3.4-869-gf2c421 @ 
/usr/local/share/emacs/site-lisp/org-mode/lisp/)


Any help appreciated.

Charlie Millar

Re: [O] Problem exporting to pdflatex

[Charles Millar]

Negleted to mention that the export to pdflatex worked fine with Emacs 
24 version included in LMDE Betsy.



On 05/26/2016 07:28 PM, Charles Millar wrote:

Hi,

I just upgraded via git to Emacs 25. My init file loads OK and 
everything "seems" to work, except:


Upon attempting to export to pdflatex following error results

Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
  file-truename(nil)
  find-file-noselect-1(#Thisfiletobeexported.pdf> 
"/mnt/Data/ActiveFiles/FilesAndFormsTemplates/Thisfiletobeexported.pdf" 
nil nil 
"/mnt/Data/ActiveFiles/FilesAndFormsTemplates/Thisfiletobeexported.pdf" 
(17031 2057))
find-file-noselect("/mnt/Data/ActiveFiles/FilesAndFormsTemplates/Thisfiletobeexported.pdf" 
nil nil nil)
find-file-other-window("/mnt/Data/ActiveFiles/FilesAndFormsTemplates/Thisfiletobeexported.pdf") 


  org-open-file("./Thisfiletobeexported.pdf")
  (if a (org-latex-export-to-pdf t s v b) (org-open-file 
(org-latex-export-to-pdf nil s v b)))
  (lambda (a s v b) (if a (org-latex-export-to-pdf t s v b) 
(org-open-file (org-latex-export-to-pdf nil s v b(nil nil nil nil)

  org-export-dispatch(nil)
  funcall-interactively(org-export-dispatch nil)
  call-interactively(org-export-dispatch nil nil)
  command-execute(org-export-dispatch)

LMDE Betsy

GNU Emacs 25.1.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 3.14.5) of 
2016-05-26


Org-mode version 8.3.4 (release_8.3.4-869-gf2c421 @ 
/usr/local/share/emacs/site-lisp/org-mode/lisp/)


Any help appreciated.

Charlie Millar

[O] [ANN] Remove XEmacs compatibility layer

[Nicolas Goaziou]

Hello,

I finally did the grunt job and removed all XEmacs compatibility in the
code base (development branch).

On the Emacs side, the following functions are now considered obsolete
and may trigger innocuous compilation warnings:

- `org-add-hook',
- `org-decompose-region',
- `org-detach-overlay',
- `org-file-equal-p',
- `org-float-time',
- `org-indent-line-to',
- `org-indent-to-column',
- `org-looking-at-p',
- `org-looking-back',
- `org-match-string-no-properties',
- `org-propertize',
- `org-re',
- `org-select-frame-set-input-focus'

The next step is to remove compatibility code for Emacsen older than
24.3 release, if anyone feels like spending some time on it during
a rainy day.

Regards,

-- 
Nicolas Goaziou0x80A93738

Re: [O] [ANN] Remove XEmacs compatibility layer

[Georgiy Tugai]

If I may ask, was there any particular reason for ditching XEmacs
compatibility?

I have no intentions of starting an "edition war" and pre-emptively ask
for forgiveness should this inadvertently occur.

On 26 May, Nicolas Goaziou wrote:
> Hello,
> 
> I finally did the grunt job and removed all XEmacs compatibility in the
> code base (development branch).
> 
> On the Emacs side, the following functions are now considered obsolete
> and may trigger innocuous compilation warnings:
> 
> - `org-add-hook',
> - `org-decompose-region',
> - `org-detach-overlay',
> - `org-file-equal-p',
> - `org-float-time',
> - `org-indent-line-to',
> - `org-indent-to-column',
> - `org-looking-at-p',
> - `org-looking-back',
> - `org-match-string-no-properties',
> - `org-propertize',
> - `org-re',
> - `org-select-frame-set-input-focus'
> 
> The next step is to remove compatibility code for Emacsen older than
> 24.3 release, if anyone feels like spending some time on it during
> a rainy day.
> 
> Regards,
> 
> -- 
> Nicolas Goaziou0x80A93738
> 


signature.asc
Description: PGP signature

Re: [O] B_column does not insert :BEAMER_COL:

[Nicolas Goaziou]

Rainer M Krug  writes:

> Right - that works. But Why do the others have B_ names, while this
> environment has BMCOL?

"BMCOL" is a terrible name. However, it is not an environment per se
since it controls both "columns" and "column" environments.

There is a use-case for handling "columns" independently on "BMCOL"
(i.e., add specific options to the environment). I'm not so sure about
"column". There might be the same reason.

Regards,

Re: [O] Bug: XML entities in the ox-rss exporter

[Arun Isaac]

> I think my patch introduces a bug in `org-rss-build-channel-info'. I'll
> fix this and send a new patch soon.

I didn't realize (plist-get info :title) returns a list, and not a
string.  I have now fixed the bug. Please find attached a new patch.



signature.asc
Description: PGP signature
>From 58c290c9308f07e44bf893331ccf9d9c5d255e04 Mon Sep 17 00:00:00 2001
From: Arun Isaac 
Date: Thu, 26 May 2016 17:24:29 +0530
Subject: [PATCH] ox-rss: Encode characters to their XML entities

* contrib/lisp/ox-rss.el (org-rss-build-channel-info, org-rss-headline):
  Encode disallowed characters in `title' to their XML entities

The `title' field is user specified and may contain characters such as
"&", "<" or ">" that are disallowed in XML. These characters should be
encoded into their corresponding XML entities.
---
 contrib/lisp/ox-rss.el | 15 ---
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/contrib/lisp/ox-rss.el b/contrib/lisp/ox-rss.el
index 0c4a2f2..44ee8db 100644
--- a/contrib/lisp/ox-rss.el
+++ b/contrib/lisp/ox-rss.el
@@ -248,12 +248,13 @@ communication channel."
 			(format-time-string
 			 "%a, %d %b %Y %H:%M:%S %z"
 			 (org-time-string-to-time pubdate0)
-	 (title (or (org-element-property :RSS_TITLE headline)
-			(replace-regexp-in-string
-			 org-bracket-link-regexp
-			 (lambda (m) (or (match-string 3 m)
-	 (match-string 1 m)))
-			 (org-element-property :raw-value headline
+	 (title (org-rss-plain-text
+		 (or (org-element-property :RSS_TITLE headline)
+			 (replace-regexp-in-string
+			  org-bracket-link-regexp
+			  (lambda (m) (or (match-string 3 m)
+	  (match-string 1 m)))
+			  (org-element-property :raw-value headline))) info))
 	 (publink
 	  (or (and hl-perm (concat (or hl-home hl-pdir) hl-perm))
 		  (concat
@@ -318,7 +319,7 @@ as a communication channel."
 (defun org-rss-build-channel-info (info)
   "Build the RSS channel information."
   (let* ((system-time-locale "C")
-	 (title (plist-get info :title))
+	 (title (org-export-data (plist-get info :title) info))
 	 (email (org-export-data (plist-get info :email) info))
 	 (author (and (plist-get info :with-author)
 		  (let ((auth (plist-get info :author)))
-- 
2.8.2

Re: [O] [ANN] Remove XEmacs compatibility layer

[Nicolas Goaziou]

Hello,

Georgiy Tugai  writes:

> If I may ask, was there any particular reason for ditching XEmacs
> compatibility?

I didn't ditch XEmacs compatibility. Org hadn't compiled on XEmacs for
a long time already. Org was broken on XEmacs, and no one volunteered to
solve it. Barely anyone even reported it.

Non-working compatibility code was lingering around and was not
consistently used in all commits. I just cleaned up that mess. At least,
it doesn't make things worse on XEmacs.

We decided to drop XEmacs support some time ago. You may want to search
the mailing list archives about it. No one had took action about it
until now.

I have the feeling that it is not possible anymore to port Org to
XEmacs. However, I am not opposed to someone doing the job, as long as
it introduces only a limited set of changes in the code base.


Regards,

-- 
Nicolas Goaziou

Re: [O] B_column does not insert :BEAMER_COL:

[Rainer M Krug]

Nicolas Goaziou  writes:

> Hello,
>
> Rainer M Krug  writes:
>
>> When I set the B_column environment, the property :BEAMER_env: is as
>> expected, automatically set to =column=, but exporting to beamer results
>> in an error as the environment is is not actually used in the resulting
>> latex file. The environment is only correctly created, if the
>> property :BEAMER_COL: is added.
>>
>> This is counter-intuitive and not obvious. Would it be possible to
>> add :BEAMER_COL: automatically as well?
>
> I think the column environment is a left-over for previous
> implementation and should be removed. 
>
> Couldn't you use BMCOL instead ("|")?

Right - that works. But Why do the others have B_ names, while this
environment has BMCOL?

Rainer

>
> Regards,

-- 
Rainer M. Krug
email: Rainerkrugsde
PGP: 0x0F52F982


signature.asc
Description: PGP signature

Re: [O] Bug: XML entities in the ox-rss exporter

[Arun Isaac]

> Please find attached the patch.

I think my patch introduces a bug in `org-rss-build-channel-info'. I'll
fix this and send a new patch soon.


signature.asc
Description: PGP signature

Re: [O] B_column does not insert :BEAMER_COL:

[Nicolas Goaziou]

Rainer M Krug  writes:

> This adds the :BEAMER_col: property, which is converted on export to
> the column environment with the given width, i.e. the same as B_column
> plus the width in PROPERTIES. As far as I see, it does nothing with
> the columns (B_columns) environment - or am I missing something here?

If you look to the generated LaTeX code, you should see that there is
a both a "columns" and a "column" environment even though you only
specify BMCOL.

> I don't think one can use B_columns without specifying the width
> in :PROPERTIES: 

Of course not. AFAIR, there is no width attribute for "columns" in
Beamer. B_columns is meant to be used in addition to BMCOL, when options
the latter provides are not enough.

> and nothing stops me to add additional PROPERTIES in the BMCOL
> property.

Only if you don't use it along with other environment. Otherwise, the
properties apply to the other environment.

Regards,

Re: [O] Bug: XML entities in the ox-rss exporter

[Nicolas Goaziou]

Hello,

Arun Isaac  writes:

> Subject: [PATCH] ox-rss: Encode characters to their XML entities
>
> * contrib/lisp/ox-rss.el (org-rss-build-channel-info, org-rss-headline):
>   Encode disallowed characters in `title' to their XML entities
>
> The `title' field is user specified and may contain characters such as
> "&", "<" or ">" that are disallowed in XML. These characters should be
> encoded into their corresponding XML entities.

Applied. Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] B_column does not insert :BEAMER_COL:

[Rainer M Krug]

Nicolas Goaziou  writes:

> Rainer M Krug  writes:
>
>> Right - that works. But Why do the others have B_ names, while this
>> environment has BMCOL?
>
> "BMCOL" is a terrible name. However, it is not an environment per se
> since it controls both "columns" and "column" environments.


To quote from the Beamer Manual (emphasis added):

12.7 Splitting a Frame into Multiple Columns:

,
| The *main environment for creating columns* is called columns. Inside
| this environment, you can either place several *column environments*,
| each of which creates a new column, or use the \column command to
| create new columns.
`

But I think you are referring to BMCOL. This adds the :BEAMER_col:
property, which is converted on export to the column environment with
the given width, i.e. the same as B_column plus the width in
PROPERTIES. As far as I see, it does nothing with the columns
(B_columns) environment - or am I missing something here?

>
> There is a use-case for handling "columns" independently on "BMCOL"
> (i.e., add specific options to the environment). I'm not so sure about
> "column". There might be the same reason.

I don't think one can use B_columns without specifying the width
in :PROPERTIES: and nothing stops me to add additional PROPERTIES in the
BMCOL property. 

Rainer

>
> Regards,

-- 
Rainer M. Krug
email: Rainerkrugsde
PGP: 0x0F52F982


signature.asc
Description: PGP signature