Re: [O] Limit on length of babel block #+name: value?

[Christian Moe]

Hi,

I cannot reproduce this on 8.0.2, at least not with the info
provided. E.g., the following works fine:

#+name: improvement-treatment
#+begin_src R :results graphics :file test.png
  x <- 1:10
  y <- x^2
  plot(x, y)  
#+end_src

#+RESULTS: improvement-treatment
[[file:test.png]]

So does any variation with an arbitrarily long string as NAME.

Yours,
Christian

John Hendy writes:

> I was just completely baffled for about 5-10 straight minutes as to
> why my block was not producing a  results section with my generated
> graphics file from an R block.
>
> I kept double checking my header options one by one despite having
> simply copied/pasted/modified it from a previous working block. Turns
> out it appears that #+name has a character limit!
>
> This (on Org-mode version 8.0.2 (release_8.0.2-65-g1e32d7)), doesn't work:
>
> #+name: improvement-treatment
>
> It appears the name can be 20 characters long (the above is 21).
>
> Is this by design or something I accidentally uncovered? Forgive me if
> it's come up before or is documented. I did a couple searches but
> didn't see it.
>
>
> Thanks,
> John

Re: [O] M-RET and C-RET turn current line of text into a heading?

[Bastien]

Samuel Wales  writes:

> |-+--++--|
> | command | context  | pos| action   |
> |-+--++--|
> | c-ret   | any  | any| create headline above ENTRY  |
> | m-ret   | headline or item | beg| create new above header/item |
> | m-ret   | headline or item | middle | split|
> | m-ret   | headline or item | end| create new below header/item |
> | m-ret   | line | beg| create headline above LINE   |
> | m-ret twice | line | beg| create item above line   |
> | m-ret   | line | middle | turn line into a headline|
> | m-ret twice | line | middle | turn line into an item   |
> | m-ret   | line | end| create headline below line   |
> | m-ret twice | line | end| create item below line   |
> |-+--++--|

Thanks a lot Samuel for writing this.

Just a quick note to tell you that this discussion *is* important,
and well read, as we plan to rewrite those functions.  Presenting
features wrt contexts so clearly is great -- thanks for doing this.

-- 
 Bastien

Re: [O] [BUG] worg table of contents

[Bastien]

Hi Rick,

Rick Frankel  writes:

> The following javascript snippet will add a function to show
> the toc when it is "clicked", but I'm not sure where to put it (at the
> bottom of "preamble.html"?)

I'd say it's a good place, yes.

Beware that the new preamble.html will only appear in pages that have
been republished.   I can republish all Worg pages if needed.

-- 
 Bastien

Re: [O] Export Org-mode content to Reveal.js presentations

[Yujie Wen]

Hi, Vikas,

  I've just updated the codes. Now org-reveal generates HTML of UTF-8
encoding, as the HTML exporter does.

  You can try with the latest codes.

Regards,
Yujie


2013/5/16 Vikas Rawal 

> >
> >   It is a limitation of org-reveal, I will take a look at the unicode
> issue.
>
> Thanks.
>
> >   For a temporary workaround, you can try changing the character coding
> on your
> > browser. Say, for firefox, it is menu "View" -> "Character Encoding",
> for IE,
> > it is menu "View" -> "Encoding".
> That works for now. Thanks again,
>
> Vikas
>
>
>

Re: [O] Export Org-mode content to Reveal.js presentations

[Vikas Rawal]

> 
>   It is a limitation of org-reveal, I will take a look at the unicode issue.

Thanks.
 
>   For a temporary workaround, you can try changing the character coding on 
> your
> browser. Say, for firefox, it is menu "View" -> "Character Encoding", for IE,
> it is menu "View" -> "Encoding".
That works for now. Thanks again,

Vikas

Re: [O] Export Org-mode content to Reveal.js presentations

[Yujie Wen]

Hi, Vikas,

  It is a limitation of org-reveal, I will take a look at the unicode issue.

  For a temporary workaround, you can try changing the character coding on
your browser. Say, for firefox, it is menu "View" -> "Character Encoding",
for IE, it is menu "View" -> "Encoding".

Regards,
Yujie


2013/5/16 Vikas Rawal 

>
> >I'd like to introduce a new Org-Mode exporter, Org-reveal, that
> > exports Org-mode contents to Reveaj.js presentations.
>
> Thanks. I was trying to use it for a presentation that has unicode
> characters. Unicode characters do not come out okay. Is this a
> limitation of reveal.js, org-reveal or my setup. Parts of the file
> without unicode characters show up fine, but unicode characters show
> up as gibberish. Unicode characters show up fine in a normal html
> export.
>
> Vikas
>
>

[O] Limit on length of babel block #+name: value?

[John Hendy]

I was just completely baffled for about 5-10 straight minutes as to
why my block was not producing a  results section with my generated
graphics file from an R block.

I kept double checking my header options one by one despite having
simply copied/pasted/modified it from a previous working block. Turns
out it appears that #+name has a character limit!

This (on Org-mode version 8.0.2 (release_8.0.2-65-g1e32d7)), doesn't work:

#+name: improvement-treatment

It appears the name can be 20 characters long (the above is 21).

Is this by design or something I accidentally uncovered? Forgive me if
it's come up before or is documented. I did a couple searches but
didn't see it.


Thanks,
John

Re: [O] Export Org-mode content to Reveal.js presentations

[Vikas Rawal]

>I'd like to introduce a new Org-Mode exporter, Org-reveal, that
> exports Org-mode contents to Reveaj.js presentations.

Thanks. I was trying to use it for a presentation that has unicode
characters. Unicode characters do not come out okay. Is this a
limitation of reveal.js, org-reveal or my setup. Parts of the file
without unicode characters show up fine, but unicode characters show
up as gibberish. Unicode characters show up fine in a normal html
export.

Vikas

Re: [O] M-RET and C-RET turn current line of text into a heading?

[Samuel Wales]

Hi Eric,

On 5/15/13, Eric Abrahamsen  wrote:
> I still think it's pretty important to have an option for creating a new
> headline *below* all the contents of the current subtree -- what C-RET
> used to do.

This might be a good thing to make a user preference.

> Also, the above provides a whole lot of options for creating a new
> headline/item above the current line -- is that really such a common
> thing to do?

It is for me.

> And the variable `org-M-RET-may-split-line' is still not taken into
> account...

I don't see why it shouldn't be taken into account.

Samuel

-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com

The disease DOES progress.  MANY people have died from it.  ANYBODY can get it.

Re: [O] M-RET and C-RET turn current line of text into a heading?

[Eric Abrahamsen]

Samuel Wales  writes:

> How about this?  IMO this would be ideal.
>
>   - M-RET is for the current context
>   - C-RET is for a new context
>
> |-+--++--|
> | command | context  | pos| action   |
> |-+--++--|
> | c-ret   | any  | any| create headline above ENTRY  |
> | m-ret   | headline or item | beg| create new above header/item |
> | m-ret   | headline or item | middle | split|
> | m-ret   | headline or item | end| create new below header/item |
> | m-ret   | line | beg| create headline above LINE   |
> | m-ret twice | line | beg| create item above line   |
> | m-ret   | line | middle | turn line into a headline|
> | m-ret twice | line | middle | turn line into an item   |
> | m-ret   | line | end| create headline below line   |
> | m-ret twice | line | end| create item below line   |
> |-+--++--|
>
> Notes:
>
>   - C-RET (in all contexts) creates new headline ABOVE (not
> below) the current entry
>
>   - "beg" does not only refer to beginning of line.  it also
> refers to the blank spaces before a list item or stars
> and space in a headline
>
> I should mention that M-RET still takes several seconds.
>
> Also, C-RET and M-RET currently seem to be identical?

Yes, that was part of the problem -- too many keys doing the same thing.

I still think it's pretty important to have an option for creating a new
headline *below* all the contents of the current subtree -- what C-RET
used to do.

Also, the above provides a whole lot of options for creating a new
headline/item above the current line -- is that really such a common
thing to do?

And the variable `org-M-RET-may-split-line' is still not taken into
account...

Eric

Re: [O] BMCOL column width as absolute?

[James Harkins]

On May 15, 2013 12:41 AM, "Nicolas Goaziou"  wrote:
> James Harkins  writes:
>
> > Hi, in the new beamer exporter, are there any plans to support an
> > absolute width for columns, rather than a fraction of \textwidth?
>
> None that I know of, but it could be of some use. Do you want to provide
> a patch?

I could try, but not in the near future. Hm, now what is that thing that
reminds me to do something, even weeks or months later? Oh right, org-mode
;-)

Oddly enough, absolute lengths achieve the desired effect: If I write a
column width as 5cm, it appears in LaTeX as "5cm\textwidth." LaTeX
processes it as 5cm, but puts a confusing error in the log ("confusing" =
the error's line number is at the end of the frame containing the columns
environment with this odd width spec). So the patch would only correct the
syntax and remove the error, but I expect it wouldn't change the PDF result.

hjh

Re: [O] Choosing image format according to export backend

[John Hendy]

On Wed, May 15, 2013 at 12:38 PM, Vincent Beffara  wrote:
> Dear list,
>
> I would like to have the same org file export to both PDF (through
> LaTeX) and HTML. The problem I have is images: for printing, PDF images
> would be best but for display in a browser, it is much better to have a
> PNG file rather than a link to the PDF. So what I need is for the
> exporter to choose the image differently according to the backend.

I know this is more of a request for coding help, but just wanted to
add my vote that this would be great. I don't use html *that* much,
but having the option would be awesome, and the replacement of all
*.pdf links with *.png (and typically re-running R code to generate
.png version, or running imagemagick on the dir to create them) is
typically too much of a barrier so I just stick with PDF/Beamer.

I'd love something like this.


John

>
> I found this piece of code on stackoverflow:
>
> #+begin_src emacs-lisp :exports results :results value raw
> (case (and (boundp 'backend) backend)
>   (nil "")
>   (latex "[[file:traps.pdf]]")
>   (html "[[file:traps.png]]"))
> #+end_src
>
> That works, but I was not able to make it recognize captions and such
> (except by pasting them in both options or otherwise modifying the lisp
> code above). Plus the markup is a bit heavy. Is there a simpler way?
>
> [One thing I thought about was to keep only one of them in the markup,
> and modifying the output for the other backend. I kind of know how to
> do that within LaTeX by redefining the \includegraphics command but it
> feels ... well ... not elegant. Maybe using a hook during one of the
> exports?]
>
> Cheers,
>
> --
> Vincent
>
>

[O] Manual fix - Table name

[Benny Simonsen]

Hi

In the manual, http://orgmode.org/manual/References.html
It seems as there is an error in the "Remote references" section:
#+NAME should be replaced by #+TBLNAME

En example could be included, e.g.:
#+tblNAME:TB_NAME
| Test |
|--|
|  100 |
|  25% |
|--|


#+tblNAME:TBNAME_2
| Value |
|---|
|   25. |
|---|
#+TBLFM: @I$1=remote(TB_NAME, @I$1)*remote(TB_NAME, @3$1)


Regards,
Benny

Re: [O] Inhibit default EMAIL in derived exporter

[Nicolas Goaziou]

Hello,

Viktor Rosenfeld  writes:

> commit 16f12e0 changed how the EMAIL option is configured in a derived
> exporter that also uses this keyword.

I fixed it in maint. Thank you for reporting it.


Regards,

-- 
Nicolas Goaziou

Re: [O] org-mime

[Eric Schulte]

Uwe Brauer  writes:

>>> "Eric" == Eric Schulte  writes:
>
>> Joseph Vidal-Rosset  writes:
>>> 
>>> -
>
>> A while back Org-mode switched its method of exporting latex equations
>> to HTML.  Equations used to be exported as png images, however they are
>> now exported as markup which may then be processed on the fly by
>> client-side javascript.  Most mail readers do not allow javascript in
>> html email, and I doubt that the required javascript headers are
>> included in the mail html mime part.
>
>> I don't know if it is currently possible to do the javascript
>> pre-processing as part of the HTML export, but that would probably be
>> the best solution in this case.
>
> Couldn't the old functionality (converting to png) be reactivated, at
> least optionally?? For me this change are bad news, since the feature
> (to export LaTeX math to something visible) is very important to me and
> even if this approach may have disadvantages, it seems to me more
> universal than the  javascript business.
>

Indeed the old latex->png functionality is still available, I just had
to update org-mime to work with the new exporter.  Export of latex to
attached png images should once again be working in the master branch of
the git repo.

Best,

>
>
> Uwe Brauer 
>
>

-- 
Eric Schulte
http://cs.unm.edu/~eschulte

Re: [O] bug in `org-export-string-as' when org-html-with-latex is set to dvipng

[Eric Schulte]

Nicolas Goaziou  writes:

> Hello,
>
> Eric Schulte  writes:
>
>> Evaluate the following to exercise the bug.
>>
>> ;; -*- emacs-lisp -*-
>> (let ((org-html-with-latex 'dvipng))
>>   (org-export-string-as
>>"\\begin{equation}\n\\frac{Eric}{Schulte}\n\\end{equation}\n" 'html 
>> t))
>>
>> This functionality is required to port org-mime to the new exporting
>> backend.
>
> Thank you for the report. I pushed a fix for that in maint. Does it now
> behave as expected?
>

Indeed this does now work.  Thanks for the quick fix.

>
>
> Regards,

-- 
Eric Schulte
http://cs.unm.edu/~eschulte

Re: [O] M-RET and C-RET turn current line of text into a heading?

[Samuel Wales]

How about this?  IMO this would be ideal.

  - M-RET is for the current context
  - C-RET is for a new context

|-+--++--|
| command | context  | pos| action   |
|-+--++--|
| c-ret   | any  | any| create headline above ENTRY  |
| m-ret   | headline or item | beg| create new above header/item |
| m-ret   | headline or item | middle | split|
| m-ret   | headline or item | end| create new below header/item |
| m-ret   | line | beg| create headline above LINE   |
| m-ret twice | line | beg| create item above line   |
| m-ret   | line | middle | turn line into a headline|
| m-ret twice | line | middle | turn line into an item   |
| m-ret   | line | end| create headline below line   |
| m-ret twice | line | end| create item below line   |
|-+--++--|

Notes:

  - C-RET (in all contexts) creates new headline ABOVE (not
below) the current entry

  - "beg" does not only refer to beginning of line.  it also
refers to the blank spaces before a list item or stars
and space in a headline

I should mention that M-RET still takes several seconds.

Also, C-RET and M-RET currently seem to be identical?

Samuel

-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com

The disease DOES progress.  MANY people have died from it.  ANYBODY can get it.

Re: [O] org-table.el

[Loyall, David]

That is good to know.  Thanks!

> Achim Gratz writes:
> Loyall, David writes:
> > In line 1145 org-table.el [1]
> > (defun org-table-get (line column)
> >
> > ...should it read like this instead?
> > (defun org-table-get (&optional line column)
> 
> Not necessarily, it simply means you have to use an explicit nil argument
> instead of relying on a missing argument being interpreted as nil.

Re: [O] Choosing image format according to export backend

[Vincent Beffara]

> I would like to have the same org file export to both PDF (through
> LaTeX) and HTML. The problem I have is images: for printing, PDF images
> would be best but for display in a browser, it is much better to have a
> PNG file rather than a link to the PDF. So what I need is for the
> exporter to choose the image differently according to the backend.

... my entry for the dirtiest piece of code possible (but it works for
now):

(defun vb-massage-includegraphics (str backend opts)
  (replace-regexp-in-string ".png}" ".pdf}" str))
(add-hook 'org-export-filter-final-output-functions
  'vb-massage-includegraphics)

Am I on the right track? Meaning, after adding a test on the backend,
possibly a file existence check and so on. Or am I missing a simpler
way?

Cheers,

-- 
Vincent

[O] [BUG] worg table of contents

[Rick Frankel]

The table of contents on worg is shown/hidden using the :hover
pseudo-element on the #table-of-contents element.

The problem is that this doesn't work on an ipad (or other touch
device). The following javascript snippet will add a function to show
the toc when it is "clicked", but I'm not sure where to put it (at the
bottom of "preamble.html"?)

#+BEGIN_SRC javascript
document.addEventListener('DOMContentLoaded',function() {
document.getElementById("table-of-contents").onclick = function() {
var elem = document.getElementById("text-table-of-contents");
elem.style.display = elem.style.display == "block" ? "none" : "block";
}
});
#+END_SRC

rick

[O] Choosing image format according to export backend

[Vincent Beffara]

Dear list,

I would like to have the same org file export to both PDF (through
LaTeX) and HTML. The problem I have is images: for printing, PDF images
would be best but for display in a browser, it is much better to have a
PNG file rather than a link to the PDF. So what I need is for the
exporter to choose the image differently according to the backend.

I found this piece of code on stackoverflow:

#+begin_src emacs-lisp :exports results :results value raw
(case (and (boundp 'backend) backend)
  (nil "")
  (latex "[[file:traps.pdf]]")
  (html "[[file:traps.png]]"))
#+end_src

That works, but I was not able to make it recognize captions and such
(except by pasting them in both options or otherwise modifying the lisp
code above). Plus the markup is a bit heavy. Is there a simpler way?

[One thing I thought about was to keep only one of them in the markup,
and modifying the output for the other backend. I kind of know how to
do that within LaTeX by redefining the \includegraphics command but it
feels ... well ... not elegant. Maybe using a hook during one of the
exports?]

Cheers,

-- 
Vincent

Re: [O] Export Org-mode content to Reveal.js presentations

[Julian M. Burgos]

Hi Yujie,

I fixed the URL, but I do not think that is the issue.  I took your
Readme.org file and exported it using the "regular" HTML exporter, and
then using the reveal exporter.  The HTML in both files is very
different, but when I open them in a browser both show very similar
looking pages.  The file obtained from the reveal exporter does not
generate a presentation. 

Maybe I am doing something wrong.  If I am using your Readme.org file, I
should be able to do C-c C-e R R to generate a Readme.html file with the
right HTML.  Then I should be able to copy
this file into my .reveal directory, open it with a browser and see the
presentation, right?  Or I am missing something? 

Any help will be welcomed.  I have to give a 30 minute talk on Friday
and I really like to get this working! :)

Julian

Yujie Wen writes:

> Hi, Julian,
>
>   It seems the URL is wrong. Please see my comments below.
>
>   Let me know if there is still problem.
>
> Regards,
> Yujie
>
>
> 2013/5/15 Julian M. Burgos 
>
>> Hi Yujie,
>>
>> Thanks for the exporter!  I am still a bit confused though (seems my
>> natural state).  Let say I downloaded reveal.js and placed it on my home
>> directory (I am using Linux), so that the path to reveal.js is the
>> following:
>>
>> /home/julian/.reveal/js/reveal.js
>>
>> so then I should add to my .emacs file
>>
>> (setq org-reveal-root "file:home/julian/.reveal/js/reveal.js")
>
> It should be three slashes ('/'), not four. Please try:
> (setq org-reveal-root "file:///home/julian/.reveal/js/reveal.js")
>
>>
>> and with this I should be able to do C-c C-e R R and export to reveal,
>> regardless of the location of the org file, right?  But it is not
>> working, so obviously I am doing something wrong.  I get a "regular"
>> HTML file instead.  Any ideas?
>>
>> Many thanks,
>>
>> Julian
>>
>> Yujie Wen writes:
>>
>> > Hi, Gary,
>> >
>> >   You are right. For absolute path to reveal.js, the org-reveal-root
>> should
>> > be set in URL form, "file:///path_to_reveal.js".
>> >
>> >   I will update the document to make it clear. Thanks for your
>> suggestion.
>> >
>> > Regards,
>> > Yujie
>> >
>> >
>> > 2013/5/15 Gary Oberbrunner 
>> >
>> >> Just want to say I just set this up, and it's great!  Easy to work with,
>> >> and my first org-mode presentation was live in under 10 min.  One minor
>> >> nit: on my Windows machine, I had to set org-reveal-root to a file:///
>> URL,
>> >> not a filesystem path.  Otherwise the presentation wouldn't load.
>> >>
>> >>
>> >> On Thu, May 9, 2013 at 4:42 PM, Simon Thum  wrote:
>> >>
>> >>> Hi Yujie,
>> >>>
>> >>> thanks for your great work! I just have had my first important
>> reveal.js
>> >>> presentation, and wished I had an org-mode exporter while I was
>> hand-coding
>> >>> the presentation.
>> >>>
>> >>> Next time It'll be easier no doubt.
>> >>>
>> >>> Cheers,
>> >>>
>> >>> Simon
>> >>>
>> >>>
>> >>> On 05/03/2013 02:48 PM, Yujie Wen wrote:
>> >>>
>>  Hi,
>> 
>> I'd like to introduce a new Org-Mode exporter, Org-reveal, that
>>  exports Org-mode contents to Reveaj.js presentations.
>> 
>> Reveal.js is a web-based presentation framework, with beautiful 3-D
>>  effects and 2-D slides arrangements. The original sample illustration
>>  can be found at http://lab.hakim.se/reveal-js/**#/<
>> http://lab.hakim.se/reveal-js/#/>
>>  .
>> 
>> With Org-reveal, you can easily exports your Org documents to
>>  Reveal.js presentations. A sample presentation created by Org-reveal
>> can
>>  be found at http://naga-eda.org/home/**yujie/org-reveal/<
>> http://naga-eda.org/home/yujie/org-reveal/>
>>  .
>> 
>> Org-reveal is hosted on https://github.com/yjwen/org-**reveal<
>> https://github.com/yjwen/org-reveal>.
>>  Should
>>  you have any suggestion or bug-report, please contact me yjwen.ty AT
>>  gmail DOT com.
>> 
>>  Thanks and regards,
>>  Yujie
>> 
>> 
>> >>>
>> >>>
>> >>
>> >>
>> >> --
>> >> Gary
>> >>
>>
>>
>> --
>> Julian Mariano Burgos, PhD
>> Hafrannsóknastofnunin/Marine Research Institute
>> Skúlagata 4, 121 Reykjavík, Iceland
>> Sími/Telephone : +354-5752037
>> Bréfsími/Telefax:  +354-5752001
>> Netfang/Email: jul...@hafro.is
>>


-- 
Julian Mariano Burgos, PhD
Hafrannsóknastofnunin/Marine Research Institute
Skúlagata 4, 121 Reykjavík, Iceland
Sími/Telephone : +354-5752037
Bréfsími/Telefax:  +354-5752001
Netfang/Email: jul...@hafro.is

Re: [O] Bug?: org-agenda-to-appt Munging Deadline Dates and Scheduled Times

[Bastien]

Hi Nick,

Nick Daly  writes:

> Hi all, please let me know if the attached minimal example doesn't
> come through for whatever reason.

It does -- thanks for catching this important issue, I just pushed
a fix for it.

-- 
 Bastien

Re: [O] I merged worg-new-exporter into worg.git master

[Bastien]

Vincent Beffara  writes:

>> I merged worg-new-exporter into worg.git master, and updated
>> the emacs.el file on the server -- many thanks again to those
>> involved in this move.
>
> Didn't you rather do the opposite? Or do I have the wrong source?
>
> commit 362d3bcd63aa57e940269f5ec74fda52a76dd175
> Merge: 2b36b92 f1a4042
> Author: Bastien Guerry 
> Date:   Tue May 14 11:47:45 2013 +0200
>
> Merge branch 'master' into worg-new-exporter

*Sigh* -- yes, you're right, fixed.  Thanks!

-- 
 Bastien

Re: [O] Export Org-mode content to Reveal.js presentations

[Yujie Wen]

Hi, Julian,

  It seems the URL is wrong. Please see my comments below.

  Let me know if there is still problem.

Regards,
Yujie


2013/5/15 Julian M. Burgos 

> Hi Yujie,
>
> Thanks for the exporter!  I am still a bit confused though (seems my
> natural state).  Let say I downloaded reveal.js and placed it on my home
> directory (I am using Linux), so that the path to reveal.js is the
> following:
>
> /home/julian/.reveal/js/reveal.js
>
> so then I should add to my .emacs file
>
> (setq org-reveal-root "file:home/julian/.reveal/js/reveal.js")

It should be three slashes ('/'), not four. Please try:
(setq org-reveal-root "file:///home/julian/.reveal/js/reveal.js")

>
> and with this I should be able to do C-c C-e R R and export to reveal,
> regardless of the location of the org file, right?  But it is not
> working, so obviously I am doing something wrong.  I get a "regular"
> HTML file instead.  Any ideas?
>
> Many thanks,
>
> Julian
>
> Yujie Wen writes:
>
> > Hi, Gary,
> >
> >   You are right. For absolute path to reveal.js, the org-reveal-root
> should
> > be set in URL form, "file:///path_to_reveal.js".
> >
> >   I will update the document to make it clear. Thanks for your
> suggestion.
> >
> > Regards,
> > Yujie
> >
> >
> > 2013/5/15 Gary Oberbrunner 
> >
> >> Just want to say I just set this up, and it's great!  Easy to work with,
> >> and my first org-mode presentation was live in under 10 min.  One minor
> >> nit: on my Windows machine, I had to set org-reveal-root to a file:///
> URL,
> >> not a filesystem path.  Otherwise the presentation wouldn't load.
> >>
> >>
> >> On Thu, May 9, 2013 at 4:42 PM, Simon Thum  wrote:
> >>
> >>> Hi Yujie,
> >>>
> >>> thanks for your great work! I just have had my first important
> reveal.js
> >>> presentation, and wished I had an org-mode exporter while I was
> hand-coding
> >>> the presentation.
> >>>
> >>> Next time It'll be easier no doubt.
> >>>
> >>> Cheers,
> >>>
> >>> Simon
> >>>
> >>>
> >>> On 05/03/2013 02:48 PM, Yujie Wen wrote:
> >>>
>  Hi,
> 
> I'd like to introduce a new Org-Mode exporter, Org-reveal, that
>  exports Org-mode contents to Reveaj.js presentations.
> 
> Reveal.js is a web-based presentation framework, with beautiful 3-D
>  effects and 2-D slides arrangements. The original sample illustration
>  can be found at http://lab.hakim.se/reveal-js/**#/<
> http://lab.hakim.se/reveal-js/#/>
>  .
> 
> With Org-reveal, you can easily exports your Org documents to
>  Reveal.js presentations. A sample presentation created by Org-reveal
> can
>  be found at http://naga-eda.org/home/**yujie/org-reveal/<
> http://naga-eda.org/home/yujie/org-reveal/>
>  .
> 
> Org-reveal is hosted on https://github.com/yjwen/org-**reveal<
> https://github.com/yjwen/org-reveal>.
>  Should
>  you have any suggestion or bug-report, please contact me yjwen.ty AT
>  gmail DOT com.
> 
>  Thanks and regards,
>  Yujie
> 
> 
> >>>
> >>>
> >>
> >>
> >> --
> >> Gary
> >>
>
>
> --
> Julian Mariano Burgos, PhD
> Hafrannsóknastofnunin/Marine Research Institute
> Skúlagata 4, 121 Reykjavík, Iceland
> Sími/Telephone : +354-5752037
> Bréfsími/Telefax:  +354-5752001
> Netfang/Email: jul...@hafro.is
>

[O] Add seconds field in custom time stamps

[Nicolas Bercher]

Hi,

I'm quite an emacs newbie but I'm using org-mode since
2 two years.

I'd like to get a higher resolution in time stamps by
adding "seconds" field (%S ?), to obtain something like
this:

  <2013-05-15 Wed 14:18:55>

or

  [2013-05-15 Wed 14:18:55]

But it seems not easy and might confuse, for example,
the rendering of dates within the Agenda (C-a a a).

I've tried to play around with org-time-stamp-custom-formats
without success.

Any pointer or something to start from?

Thanks,
Nicolas

Re: [O] Export Org-mode content to Reveal.js presentations

[Julian M. Burgos]

Hi Yujie,

Thanks for the exporter!  I am still a bit confused though (seems my
natural state).  Let say I downloaded reveal.js and placed it on my home
directory (I am using Linux), so that the path to reveal.js is the
following:

/home/julian/.reveal/js/reveal.js

so then I should add to my .emacs file 

(setq org-reveal-root "file:home/julian/.reveal/js/reveal.js")

and with this I should be able to do C-c C-e R R and export to reveal,
regardless of the location of the org file, right?  But it is not
working, so obviously I am doing something wrong.  I get a "regular"
HTML file instead.  Any ideas?

Many thanks,

Julian

Yujie Wen writes:

> Hi, Gary,
>
>   You are right. For absolute path to reveal.js, the org-reveal-root should
> be set in URL form, "file:///path_to_reveal.js".
>
>   I will update the document to make it clear. Thanks for your suggestion.
>
> Regards,
> Yujie
>
>
> 2013/5/15 Gary Oberbrunner 
>
>> Just want to say I just set this up, and it's great!  Easy to work with,
>> and my first org-mode presentation was live in under 10 min.  One minor
>> nit: on my Windows machine, I had to set org-reveal-root to a file:/// URL,
>> not a filesystem path.  Otherwise the presentation wouldn't load.
>>
>>
>> On Thu, May 9, 2013 at 4:42 PM, Simon Thum  wrote:
>>
>>> Hi Yujie,
>>>
>>> thanks for your great work! I just have had my first important reveal.js
>>> presentation, and wished I had an org-mode exporter while I was hand-coding
>>> the presentation.
>>>
>>> Next time It'll be easier no doubt.
>>>
>>> Cheers,
>>>
>>> Simon
>>>
>>>
>>> On 05/03/2013 02:48 PM, Yujie Wen wrote:
>>>
 Hi,

I'd like to introduce a new Org-Mode exporter, Org-reveal, that
 exports Org-mode contents to Reveaj.js presentations.

Reveal.js is a web-based presentation framework, with beautiful 3-D
 effects and 2-D slides arrangements. The original sample illustration
 can be found at 
 http://lab.hakim.se/reveal-js/**#/
 .

With Org-reveal, you can easily exports your Org documents to
 Reveal.js presentations. A sample presentation created by Org-reveal can
 be found at 
 http://naga-eda.org/home/**yujie/org-reveal/
 .

Org-reveal is hosted on 
 https://github.com/yjwen/org-**reveal.
 Should
 you have any suggestion or bug-report, please contact me yjwen.ty AT
 gmail DOT com.

 Thanks and regards,
 Yujie


>>>
>>>
>>
>>
>> --
>> Gary
>>


-- 
Julian Mariano Burgos, PhD
Hafrannsóknastofnunin/Marine Research Institute
Skúlagata 4, 121 Reykjavík, Iceland
Sími/Telephone : +354-5752037
Bréfsími/Telefax:  +354-5752001
Netfang/Email: jul...@hafro.is

Re: [O] I merged worg-new-exporter into worg.git master

[Vincent Beffara]

Hi,

> I merged worg-new-exporter into worg.git master, and updated
> the emacs.el file on the server -- many thanks again to those
> involved in this move.

Didn't you rather do the opposite? Or do I have the wrong source?

commit 362d3bcd63aa57e940269f5ec74fda52a76dd175
Merge: 2b36b92 f1a4042
Author: Bastien Guerry 
Date:   Tue May 14 11:47:45 2013 +0200

Merge branch 'master' into worg-new-exporter

-- 
Vincent

[O] disable org-replace-disputed-keys for org-read-date

[Miro Bezjak]

Hi all,

for orgmode 7.9.x I had the following defadvice.


(defadvice org-read-date (around my-no-disputed-keys activate)
  "Ignore org-replace-disputed-keys when calendar is active."
  (let ((org-replace-disputed-keys nil))
ad-do-it))


Contrary to the `org-replace-disputed-keys' documentation (only being
relevant at load-time), the advice worked because in 7.9.x `org-read-date'
used `org-defkey' to add the relevant keybindings each time it was called.

In 8.0.x, this advice no longer works since
`org-read-date-minibuffer-local-map' is being used.

Basically, I'm trying to use windmove keys, but not when I'm entering dates
through calendar. In calendar, shift + arrow keys are really handy and
calendar is not active for a long time.

Does anyone have any suggestion how I can achieve that in 8.0.x without
patching org.el?

Should I make a patch to introduce defcustom that will ignore disputed keys
while setting up `org-read-date-minibuffer-local-map'? Anyone else
interested in this besides me?

Kind Regards,
Miro

Re: [O] M-RET and C-RET turn current line of text into a heading?

[Eric Abrahamsen]

Christian Moe  writes:

> Eric Abrahamsen writes:
>
>> I don't see why `org-ctrl-c-star' --> `org-toggle-heading' isn't enough
>> for creating headlines out of existing text. 
>
> Fair point, but I find it useful to have a simpler and speedier
> combination, redundant or not. For instance, I often use Org to make
> structured documents out of plain text, text copy-pasted from PDFs etc.,
> which involves scrolling through the document and repeatedly turning the
> lines at point into headings. It quickly becomes a nuisance to do this
> with a sequence of two double keypresses (`C-c *', that is, `C-c S-8' --
> not to mention that I routinely switch between keyboards for three
> languages with somewhat different ideas where `*' should be).
>
>> At the very least, we shouldn't now have three keystrokes (C-c *,
>> M-RET, C-RET) that do the same thing! Also,
>> `org-M-RET-may-split-line', which was once a very interesting
>> variable, now does nothing since M-RET simply doesn't split the line.
>
> True. I think this needs to be revisited (before too many people get
> used to the recent arrangement).

Ugh, I've had plenty of experience trying to impose structure on
unstructured text. PDF copy-n-paste is a nightmare, particular where
columns were involved.

However! Having a useful set of commands is one thing, and having useful
keybindings for those commands is another. M-RET/C-RET are still pretty
crucial for taking notes out of thin air. They each have their own
behavior when point is at beginning, middle, and end of line, as well,
and I'd hope that all would be left in place.

`org-ctrl-c-star' either calls `org-table-recalculate' or
`org-toggle-heading', which are strange bedfellows. The key chord seems
much more tied to table recalculation (there are multiple various
behaviors triggered by prefix args) than to heading toggling. We might
consider splitting `org-toggle-heading' off onto its own key.

Or perhaps it would be enough tweak keybindings? Maybe leave the current
bindings and behavior of `org-ctrl-c-star', but add the "fat finger"
bindings of 'C-c 8' and 'C-c C-8' to `org-ctrl-c-star' (or even bind
them directly to `org-toggle-heading').

It would be inelegant, but that way you could park a pinkie on the
control key, and travel through a buffer with 'C-s' or '(C-u, C-)
C-n', hitting 'C-c C-8' as needed.

Just one possibility,

E

Re: [O] M-RET and C-RET turn current line of text into a heading?

[Christian Moe]

Eric Abrahamsen writes:

> I don't see why `org-ctrl-c-star' --> `org-toggle-heading' isn't enough
> for creating headlines out of existing text. 

Fair point, but I find it useful to have a simpler and speedier
combination, redundant or not. For instance, I often use Org to make
structured documents out of plain text, text copy-pasted from PDFs etc.,
which involves scrolling through the document and repeatedly turning the
lines at point into headings. It quickly becomes a nuisance to do this
with a sequence of two double keypresses (`C-c *', that is, `C-c S-8' --
not to mention that I routinely switch between keyboards for three
languages with somewhat different ideas where `*' should be).

> At the very least, we shouldn't now have three keystrokes (C-c *,
> M-RET, C-RET) that do the same thing! Also,
> `org-M-RET-may-split-line', which was once a very interesting
> variable, now does nothing since M-RET simply doesn't split the line.

True. I think this needs to be revisited (before too many people get
used to the recent arrangement).

Yours,
Christian

[O] Figure not exporting properly in Beamer

[Angel de Vicente]

Hi,

I'm using Org 7.8.03 and I have a test file to create a Beamer
presentation. At some point I have:

** Images

#+CAPTION: Sample AMR
#+label:   fig:amr-sample
[[file:amr.png]]

and a few weeks ago, after processing this I got in the tex file:

-
\frametitle{Images}
\label{sec-1-3}


\begin{figure}[htb]
\centering
\includegraphics[width=.9\linewidth]{amr.png}
\caption{\label{fig:amr-sample}Sample AMR}
\end{figure}
\end{frame}
-

Today I tried again, but instead I get:

--
\frametitle{Images}
\label{sec-1-3}


\href{t}{file:amr.png}
\end{frame}
--

I probably forgot something that I did last time, but I cannot see
it. Any hints?

Thanks,
-- 
Ángel de Vicente
http://angel-de-vicente.blogspot.com/

Re: [O] M-RET and C-RET turn current line of text into a heading?

[Eric Abrahamsen]

Christian Moe  writes:

> Hi,
>
> My user input is partially to blame for this, I think. See toward the
> end of this thread:
>
> http://comments.gmane.org/gmane.emacs.orgmode/69749
>
> I was under the impression that the behavior of M-RET had changed, but I
> may have given a wrong or incomplete description of the "old behavior" I
> seemed to remember and wanted back. I agree that the current behavior
> does not seem ideal either.
>
> Here's some more misguided user input: Wouldn't it be intuitive if M-RET
> at the beginning of a line turned that line into a heading (as it
> currently does), but M-RET at the end of a line inserted a new heading
> below (would require a change from the current workings)? Not sure about
> M-RET somewhere in the middle of a line.

Hey, I'm all about misguided user input :)

I read that brief thread, and it looks like there was a call for
opinions that I missed! Better late than never...

I don't see why `org-ctrl-c-star' --> `org-toggle-heading' isn't enough
for creating headlines out of existing text. At the very least, we
shouldn't now have three keystrokes (C-c *, M-RET, C-RET) that do the
same thing! Also, `org-M-RET-may-split-line', which was once a very
interesting variable, now does nothing since M-RET simply doesn't split
the line.

Or am I missing something about the new arrangement?

However it falls out, I would love to have two commands back: one that
starts a new heading under point, and one that starts a new heading at
the end of the current subtree. Ie, what M-RET and C-RET used to do...

Eric

> Yours,
> Christian
>
>
> Eric Abrahamsen writes:
>
>> For the past couple of weeks I'm finding that both M-RET and C-RET turn
>> the line under point into a heading, instead of inserting a new heading
>> elsewhere. This happens with `org-M-RET-may-split-line' set to anything.
>>
>> So this:
>>
>> #+begin_src org
>> * Chapter One
>> :PROPERTIES:
>> :some_prop: t
>> :END:
>> In which not [point is here] very much happens. But this is a further test 
>> to see
>> what happens on multiline text.
>> #+end_src
>>
>> becomes:
>>
>> #+begin_src org
>> * Chapter One
>> :PROPERTIES:
>> :some_prop: t
>> :END:
>> * In which not very much happens. But this is a further test to see
>> what happens on multiline text.
>> #+end_src
>>
>> This also happens with emacs -Q. Has no one else seen this?
>>
>> Thanks,
>> Eric

Re: [O] ical2org.py

[aitor]

Hi,

On Wed, May 15, 2013 at 12:56:02AM +0200, Bastien wrote:
> Hi Simon,
> 
> Simon Thum  writes:
> 
> > It's going to be confusing if we add them all.
> 
> On the contrary -- I think collecting all the information about
> various solutions in the same place is the only way to encourage
> comparisons, which is the best way to let one solution emerge,
> if needed.

indeed. Should I've known there were already so many implementations of
ical2org I wouldn't have created mine! Silly thing is, it never ocurred
to me to just search "ical2org" on google.


best,
aitor

Re: [O] M-RET and C-RET turn current line of text into a heading?

[Christian Moe]

Hi,

My user input is partially to blame for this, I think. See toward the
end of this thread:

http://comments.gmane.org/gmane.emacs.orgmode/69794

I was under the impression that the behavior of M-RET had changed, but I
may have given a wrong or incomplete description of the "old behavior" I
seemed to remember and wanted back. I agree that the current behavior
does not seem ideal either.

Here's some more misguided user input: Wouldn't it be intuitive if M-RET
at the beginning of a line turned that line into a heading (as it
currently does), but M-RET at the end of a line inserted a new heading
below (would require a change from the current workings)? Not sure about
M-RET somewhere in the middle of a line.

Yours,
Christian


Eric Abrahamsen writes:

> For the past couple of weeks I'm finding that both M-RET and C-RET turn
> the line under point into a heading, instead of inserting a new heading
> elsewhere. This happens with `org-M-RET-may-split-line' set to anything.
>
> So this:
>
> #+begin_src org
> * Chapter One
> :PROPERTIES:
> :some_prop: t
> :END:
> In which not [point is here] very much happens. But this is a further test to 
> see
> what happens on multiline text.
> #+end_src
>
> becomes:
>
> #+begin_src org
> * Chapter One
> :PROPERTIES:
> :some_prop: t
> :END:
> * In which not very much happens. But this is a further test to see
> what happens on multiline text.
> #+end_src
>
> This also happens with emacs -Q. Has no one else seen this?
>
> Thanks,
> Eric