Re: [O] LaTeX export \listoffigures
Hi Nick! 2012/8/27 Nick Dokos : > --8<---cut here---start->8--- > #+LATEX: \listoffigures > > * foo > foo "a b c" bar > --8<---cut here---end--->8--- Thanks! -- Henri-Paul Indiogine Curriculum & Instruction Texas A&M University TutorFind Learning Centre http://www.tutorfind.ca Email: hindiog...@gmail.com Skype: hindiogine
Re: [O] Please consider making a donation
Bastien writes: > Hello all, > > I've been a freelancer for the last two months and I want to continue > this experience. > > As such, my main challenge is to discipline myself not to spend too > much time on Org -- because, as you can imagine, it *is* very tempting. > > So the more donation I receive, the more time I will have for Org. > > Any donation will first go into a new computer, as my lovely Thinkpad > X61 is about to die. > > I you think of any Emacs/Org development you would like to sponsor, > independantly from what's already existing, please send me an email. > > Thanks for your help! You're on my shortlist of people to donate to when I have some spare cash. I'm eternally grateful for the work you've put into Org! If I had the ability, I'd just pay you to work on it straight-up. As an aside, Thinkpads are pretty notorious for living through hell. My T410 is currently ridiculously beat up, but still runs like a charm. -- Jeremiah Dodds blog : http://jdodds.github.com github : https://github.com/jdodds freenode : exhortatory twitter: kaens
Re: [O] Org-mode release 7.9
2012/8/26 Robert Horn : > > I decided to try ELPA to upgrade in place for the first time, and used > it to upgrade to the latest org 7.9. No apparent errors there. (good > work BTW). > > Tests: > - proper org-version? yes 7.9, no problems reported > - [f8] to trigger a capture I get the error: > > org-capture-select-template: Symbol's function definition is void: > org-contextualize-keys > I had the same problem with emacs 24.2 after upgrading to org 7.9 (package version is given as: 20120827) via ELPA. I could somehow circumvent the problem by adding (add-to-list 'load-path "~/.emacs.d/elpa/org-20120827") to my .emacs. Cheers, Manuel
Re: [O] LaTeX export \listoffigures
Henri-Paul Indiogine wrote:
> Greetings!
>
> I am using orgmode with export to LaTeX to write my dissertation. My
> thanks to all codes and contributors. Without org-mode it would take
> me even more time.
>
> I am wondering how to have the LaTeX command \listoffigures
> automatically added by the export function.
>
> I have the following from the top of the org file:
>
> #+TAGS: noexport(n) chp(c) sec(s) subsec(b) temp(t) app(a)
> #+LaTeX_CLASS: book
> #+LaTeX_header: \usepackage[margin=2.5cm]{geometry}
> #+LaTeX_header: \usepackage{appendix}
> #+LANGUAGE: en
> #+DESCRIPTION: Doctoral dissertation at Texas A&M University
> #+TODO: VOID(v) STRT(s) COMP(c) REVD(r) DONE(d)
> #+OPTIONS: H:3 num:t toc:t \n:nil @:t ::t |:t ^:nil -:t f:t *:t <:t
> #+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:nil pri:nil tags:nil
> #+EXPORT_SELECT_TAGS: export
> #+EXPORT_EXCLUDE_TAGS: noexport
>
> So, I know how to add packages in the preamble. However,
> \listoffigures does not go in the preamble but soon after
> \begin{document} and \tableofcontents
>
> It seems that the "book" LaTeX class automatically adds
> \tableofcontents. How can I tweak that to add \listoffigures and
> maybe \listoftables ?
>
No, it's the exporter itself that adds the \tableofcontents - or not:
with
#+OPTIONS: toc:nil
\tableofcontents will not be generated.
In any case, in the same way that you can add something to the preamble
with #+LaTeX_header, you can add something to the document with
#+LATEX. The trick is to add it first thing so that it goes right after
the \tableofcontents:
--8<---cut here---start->8---
#+LATEX: \listoffigures
* foo
foo "a b c" bar
--8<---cut here---end--->8---
should work.
Nick
Re: [O] How to make kill-sexp work as in the rest of Emacs?
On 8/27/12, Nick Dokos wrote: > (modify-syntax-entry ?\" "\"") Works great. I will put it in org mode hook. Thanks. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com
Re: [O] How to make kill-sexp work as in the rest of Emacs?
Samuel Wales wrote: > On 8/27/12, Nick Dokos wrote: > > It does not work the same way in the "rest of emacs": sexp commands > > behave differently depending on the mode. You can e.g. > > I should have made it clear that I understood that. I want to know > how to just fix that one thing. > Try (modify-syntax-entry ?\" "\"") in the org buffer. If you want it in every org buffer, I would modify org-mode in org.el with the above. Nick
Re: [O] How to make kill-sexp work as in the rest of Emacs?
On 8/27/12, Nick Dokos wrote: > It does not work the same way in the "rest of emacs": sexp commands > behave differently depending on the mode. You can e.g. I should have made it clear that I understood that. I want to know how to just fix that one thing. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com
[O] LaTeX export \listoffigures
Greetings!
I am using orgmode with export to LaTeX to write my dissertation. My
thanks to all codes and contributors. Without org-mode it would take
me even more time.
I am wondering how to have the LaTeX command \listoffigures
automatically added by the export function.
I have the following from the top of the org file:
#+TAGS: noexport(n) chp(c) sec(s) subsec(b) temp(t) app(a)
#+LaTeX_CLASS: book
#+LaTeX_header: \usepackage[margin=2.5cm]{geometry}
#+LaTeX_header: \usepackage{appendix}
#+LANGUAGE: en
#+DESCRIPTION: Doctoral dissertation at Texas A&M University
#+TODO: VOID(v) STRT(s) COMP(c) REVD(r) DONE(d)
#+OPTIONS: H:3 num:t toc:t \n:nil @:t ::t |:t ^:nil -:t f:t *:t <:t
#+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:nil pri:nil tags:nil
#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCLUDE_TAGS: noexport
So, I know how to add packages in the preamble. However,
\listoffigures does not go in the preamble but soon after
\begin{document} and \tableofcontents
It seems that the "book" LaTeX class automatically adds
\tableofcontents. How can I tweak that to add \listoffigures and
maybe \listoftables ?
Thanks,
Henri-Paul
--
Henri-Paul Indiogine
Curriculum & Instruction
Texas A&M University
TutorFind Learning Centre
http://www.tutorfind.ca
Email: hindiog...@gmail.com
Skype: hindiogine
Re: [O] How to make kill-sexp work as in the rest of Emacs?
Samuel Wales wrote: > I like doing kill-sexp to kill a "quoted string like this". How do I > get that to > work again? > It does not work the same way in the "rest of emacs": sexp commands behave differently depending on the mode. You can e.g. (set-syntax-table lisp-mode-syntax-table) and then the sexp commands will behave lispishly. C-mode buffers do the equivalent of (set-syntax-table c-mode-syntax-table) and text mode buffers (of which org-mode is a derived mode) do (set-syntax-table text-mode-syntax-table) Setting the syntax table to e.g. the lisp mode one will certainly allow you to kill quoted strings with kill-sexp. Whether it has other, less desirable consequences, I don't know: you'll just have to try and see. Nick
Re: [O] Bug with org-agenda-span & org-agenda-start-day
Charles Philip Chan writes: Hi Bastien: > Bastien writes: > > Hi Bastien: > >> You need to add (org-agenda-start-on-weekday nil) to the list of >> properties for this agenda view. >> >> See the docstring of `org-agenda-start-on-weekday' for details. > > Ah, OK. Thanks. I spoke too soon. I tried it out and this is not working. For example today is Monday, Aug. 27. If I set the agenda span to anything but "7" or "week", it works- the start date is "Aug. 28" (I even tried "month" and "year"). This works even if "org-agenda-start-on-weekday" is non-nil (my "org-agenda-start-on-weekday" is set globally to "0"). However, if I set it to either "7" or "week", the start day in the agenda is Sunday, Aug. 26. This is really strange. Cheers, Charles -- Sigh. I like to think it's just the Linux people who want to be on the "leading edge" so bad they walk right off the precipice. (Craig E. Groeschel) pgpwovVRtbzW8.pgp Description: PGP signature
Re: [O] timestamped items not showing in today agenda view
Hi List, Just to follow up on this, Bastien helped me figure it out off-list. The solution is to use or in place of , and some combination of < or <= depending on exactly what you want to see where and when. -k. On Wed, Aug 22, 2012 at 1:59 AM, Bastien wrote: > Hi Ken, > > Ken Mankoff writes: > >>> Can you tell what is the value of these variables? >>> >>> org-agenda-todo-ignore-deadlines >>> org-agenda-todo-ignore-scheduled >>> org-agenda-todo-ignore-timestamp >>> org-agenda-todo-ignore-with-date >>> org-agenda-tags-todo-honor-ignore-options >> >> At the time I wrote that email they were all unset, so default values. I >> tried setting them all to nil and t, and neither had any effect. Scheduled >> item with timestamp shows up in (agenda) but not (tags-todo) search > > Can you send a minimal .org file and a minimal .el configuration file > that let us reproduce the problem with emacs -Q ? > > Otherwise it will be difficult to debug. > > Thanks in advance for your effort! > > -- > Bastien
Re: [O] Bug with org-agenda-span & org-agenda-start-day
Bastien writes: Hi Bastien: > You need to add (org-agenda-start-on-weekday nil) to the list of > properties for this agenda view. > > See the docstring of `org-agenda-start-on-weekday' for details. Ah, OK. Thanks. Cheers, Charles -- "Even more amazing was the realization that God has Internet access. I wonder if He has a full newsfeed?" (By Matt Welsh) pgpjYQZqPxRqI.pgp Description: PGP signature
Re: [O] Strange Problem with "org-agenda-redo"
Bastien writes: Hi Bastien: Thanks for fixing this. > Mhh... This was a real bug, I had a good sweat on this one. I hope you didn't lose a lot of weight on this one. ;-) Charles -- "I'd crawl over an acre of 'Visual This++' and 'Integrated Development That' to get to gcc, Emacs, and gdb. Thank you." (By Vance Petree, Virginia Power) pgpkihVH3QeL0.pgp Description: PGP signature
Re: [O] Please consider making a donation
+1! me too.
Re: [O] Including multiple plots resulting from a loop of R code in LaTeX
On Mon, Aug 27, 2012 at 3:40 PM, Nick Dokos wrote: > John Hendy wrote: > >> There are six of these sections, however when I do C-c C-c on the >> block and then C-c C-e p to export to LaTeX, I get duplicate sections >> back to back. I have to delete the entire results section and only do >> C-c C-e p with an empty results section to have the duplicate removed. >> >> Why might this be? >> > > Don't know - but did you try a named source block? If that workd, > i.e. does not give you the duplication of results, then a) you have a > workaround and b) that provides extra information about the (possible) > bug. If it doesn't - ah, well: it was a shot in the dark in the first > place :-) Thanks for the suggestion. I should have included that I did have my block named, so sorry for not including that. I guess it all came down to :results output org in the end. Thanks again, John > > Also, are you sure you don't have anything between the source block and > the results block? > > Nick
Re: [O] Including multiple plots resulting from a loop of R code in LaTeX
On Mon, Aug 27, 2012 at 3:50 PM, Eric Schulte wrote:
> John Hendy writes:
>
>>> Disregard again... adding multiple newlines with cat() doesn't work,
>>> but I had the idea to do:
>>>
>>> cat(paste("[[../plots/",filename,"]]",sep=""), sep="\n")
>>> cat("\n")
>>>
>>> Works great. I suppose I can use this to add #+attr_latex options as
>>> well as captions. Cool stuff.
>>
>> Getting a bit of odd behavior on LaTeX export. Here's the gist of my
>> block below. I've iterated through various model parameters and saved
>> the results to filenames based on those parameters. These are stored
>> in a vector =filenames=.
>>
>> #+begin_src R :session model :results output raw :exports results
>>
>> for(i in 1:nrow(filenames)) {
>>
>> # insert section header
>> cat(paste("*Param1 = ", as.character(params[i, 1]),
>> "; Param2 = ", as.character(params[i, 2]),"*", sep=""))
>> cat("\n\n")
>> cat("#+begin_center")
>> cat("\n")
>>
>> read.csv(filename)
>>
>> for(j in 1:5) {
>>
>> ggplot code
>>
>> pdf(output-filename)
>> print(p)
>> dev.off()
>>
>> cat(paste("[[../plots/",output-filename,"]]",sep=""), sep="\n")
>> cat("\n")
>>
>> } # end plotting loop
>>
>> cat("#+end_center")
>> cat("\n\n")
>>
>> } # end filename cycling loop
>>
>> #+end_src
>>
>> I get results like so:
>>
>> #+RESULTS:
>> *Param1 = 4; Param2 = 0.025*
>>
>>
>> #+begin_center
>> [[../plots/filename1.pdf]]
>>
>> [[../plots/filename2.pdf]]
>>
>> [[../plots/filename3.pdf]]
>>
>> [[../plots/filename4.pdf]]
>>
>> [[../plots/filename5.pdf]]
>>
>> #+end_center
>>
>> There are six of these sections, however when I do C-c C-c on the
>> block and then C-c C-e p to export to LaTeX, I get duplicate sections
>> back to back. I have to delete the entire results section and only do
>> C-c C-e p with an empty results section to have the duplicate removed.
>>
>
> Try replacing ":results output raw" with ":results output org"
>
>>
>> Why might this be?
>>
>
> Because Babel is not able to remove the old results of "raw" output as
> the output has no obvious delimiters. However "org" output should be
> wrapped in begin/end_org blocks allowing old output to be cleaned up.
>
> Best,
>
That works! Sigh... so much to learn...
John
>>
>>
>> John
>>
>>
>>>
>>> Thanks!
>>>
Thanks,
John
>
> If I understand correctly that should result in the behavior you're
> after.
>
> Best,
>
>>
>>
>> Thanks,
>> John
>>
>
> --
> Eric Schulte
> http://cs.unm.edu/~eschulte
>>
>
> --
> Eric Schulte
> http://cs.unm.edu/~eschulte
Re: [O] Including multiple plots resulting from a loop of R code in LaTeX
John Hendy writes:
>> Disregard again... adding multiple newlines with cat() doesn't work,
>> but I had the idea to do:
>>
>> cat(paste("[[../plots/",filename,"]]",sep=""), sep="\n")
>> cat("\n")
>>
>> Works great. I suppose I can use this to add #+attr_latex options as
>> well as captions. Cool stuff.
>
> Getting a bit of odd behavior on LaTeX export. Here's the gist of my
> block below. I've iterated through various model parameters and saved
> the results to filenames based on those parameters. These are stored
> in a vector =filenames=.
>
> #+begin_src R :session model :results output raw :exports results
>
> for(i in 1:nrow(filenames)) {
>
> # insert section header
> cat(paste("*Param1 = ", as.character(params[i, 1]),
> "; Param2 = ", as.character(params[i, 2]),"*", sep=""))
> cat("\n\n")
> cat("#+begin_center")
> cat("\n")
>
> read.csv(filename)
>
> for(j in 1:5) {
>
> ggplot code
>
> pdf(output-filename)
> print(p)
> dev.off()
>
> cat(paste("[[../plots/",output-filename,"]]",sep=""), sep="\n")
> cat("\n")
>
> } # end plotting loop
>
> cat("#+end_center")
> cat("\n\n")
>
> } # end filename cycling loop
>
> #+end_src
>
> I get results like so:
>
> #+RESULTS:
> *Param1 = 4; Param2 = 0.025*
>
>
> #+begin_center
> [[../plots/filename1.pdf]]
>
> [[../plots/filename2.pdf]]
>
> [[../plots/filename3.pdf]]
>
> [[../plots/filename4.pdf]]
>
> [[../plots/filename5.pdf]]
>
> #+end_center
>
> There are six of these sections, however when I do C-c C-c on the
> block and then C-c C-e p to export to LaTeX, I get duplicate sections
> back to back. I have to delete the entire results section and only do
> C-c C-e p with an empty results section to have the duplicate removed.
>
Try replacing ":results output raw" with ":results output org"
>
> Why might this be?
>
Because Babel is not able to remove the old results of "raw" output as
the output has no obvious delimiters. However "org" output should be
wrapped in begin/end_org blocks allowing old output to be cleaned up.
Best,
>
>
> John
>
>
>>
>> Thanks!
>>
>>>
>>>
>>> Thanks,
>>> John
>>>
If I understand correctly that should result in the behavior you're
after.
Best,
>
>
> Thanks,
> John
>
--
Eric Schulte
http://cs.unm.edu/~eschulte
>
--
Eric Schulte
http://cs.unm.edu/~eschulte
Re: [O] Including multiple plots resulting from a loop of R code in LaTeX
John Hendy wrote: > There are six of these sections, however when I do C-c C-c on the > block and then C-c C-e p to export to LaTeX, I get duplicate sections > back to back. I have to delete the entire results section and only do > C-c C-e p with an empty results section to have the duplicate removed. > > Why might this be? > Don't know - but did you try a named source block? If that workd, i.e. does not give you the duplication of results, then a) you have a workaround and b) that provides extra information about the (possible) bug. If it doesn't - ah, well: it was a shot in the dark in the first place :-) Also, are you sure you don't have anything between the source block and the results block? Nick
Re: [O] Including multiple plots resulting from a loop of R code in LaTeX
> Disregard again... adding multiple newlines with cat() doesn't work,
> but I had the idea to do:
>
> cat(paste("[[../plots/",filename,"]]",sep=""), sep="\n")
> cat("\n")
>
> Works great. I suppose I can use this to add #+attr_latex options as
> well as captions. Cool stuff.
Getting a bit of odd behavior on LaTeX export. Here's the gist of my
block below. I've iterated through various model parameters and saved
the results to filenames based on those parameters. These are stored
in a vector =filenames=.
#+begin_src R :session model :results output raw :exports results
for(i in 1:nrow(filenames)) {
# insert section header
cat(paste("*Param1 = ", as.character(params[i, 1]),
"; Param2 = ", as.character(params[i, 2]),"*", sep=""))
cat("\n\n")
cat("#+begin_center")
cat("\n")
read.csv(filename)
for(j in 1:5) {
ggplot code
pdf(output-filename)
print(p)
dev.off()
cat(paste("[[../plots/",output-filename,"]]",sep=""), sep="\n")
cat("\n")
} # end plotting loop
cat("#+end_center")
cat("\n\n")
} # end filename cycling loop
#+end_src
I get results like so:
#+RESULTS:
*Param1 = 4; Param2 = 0.025*
#+begin_center
[[../plots/filename1.pdf]]
[[../plots/filename2.pdf]]
[[../plots/filename3.pdf]]
[[../plots/filename4.pdf]]
[[../plots/filename5.pdf]]
#+end_center
There are six of these sections, however when I do C-c C-c on the
block and then C-c C-e p to export to LaTeX, I get duplicate sections
back to back. I have to delete the entire results section and only do
C-c C-e p with an empty results section to have the duplicate removed.
Why might this be?
John
>
> Thanks!
>
>>
>>
>> Thanks,
>> John
>>
>>>
>>> If I understand correctly that should result in the behavior you're
>>> after.
>>>
>>> Best,
>>>
Thanks,
John
>>>
>>> --
>>> Eric Schulte
>>> http://cs.unm.edu/~eschulte
[O] [babel] #+INCLUDE does not account for relative paths to images
I've noticed that if I include one Org file into another using #+INCLUDE, then I'm not getting a proper path to babel-generated figures at least while doing HTML export. I believe it is still an issue for non-babel images. I feel like it would be nice to export an updated relative path to included image file with a different base when exporting master document. Current implementation forces either to keep project Org files in the same folder or use more sophisticated relative paths like ../sibling-project/foo.png . Though I did not try the latter. -- Mikhail
Re: [O] org-notify.el doesn't work
Thanks for your help. But this is something I already know. I'll try to contact the author.
Re: [O] org2blog: referencing to other blog posts?
On Mon, Aug 27, 2012 at 11:50 PM, Puneeth Chaganti wrote: > Hi, > > I hope we are talking of org2blog/wp. There's another package called > org2blog authored by tehom, that works for blogger. > > On Sun, Aug 26, 2012 at 11:44 PM, Steinar Bang wrote: >> Is there a way to reference other blog posts in org2blog, other than >> using absolute URLs for that article on the server? > > Currently, there's no way to reference other blog posts, other than > using absolute URLs. > >> I will use absolute URLs as a workaround, if there is no way, but it >> would feel better to "work inside the system". > > I think using absolute URLs would be the most robust way of doing > this, but of course, this process can be simplified, by providing a > way of inserting those links from within org2blog. I imagine this > would use link abbreviations, and provide some sort of a completion > mechanism to insert links to other posts. I'll try and get to this, > some time soon. I've implemented something very basic and crude for this. Feel free to try it out and let me know if it works for you and suggest improvements. Thanks, Puneeth
Re: [O] Problems Setting Drawers in .emacs
Thanks Nick
You are right, something in my .emacs file was causing this
--Rodolfo
On Mon, Aug 27, 2012 at 12:10 AM, Nick Dokos wrote:
> Rodolfo Aramayo wrote:
>
>> Hi,
>>
>> I am having essentially the same problem described on the following thread:
>>
>> http://thread.gmane.org/gmane.emacs.orgmode/22263
>>
>> Which is essentially:
>>
>> when I define in my .emacs file:
>>
>> ;; Define some default drawers.
>> (setq org-drawers (quote ("PROPERTIES" "SETUP")))
>>
>> PROPERTIES and SETUP aren't recognised as drawers in my org
>> files. They don't close and open using tab and the fontification of them
>> indicates that org isn't recognising them as drawers.
>> If I however define a drawer in my org file like:
>> #+DRAWERS: NOTES
>> this works correctly
>>
>> I am using Org-mode version 7.8.11 and GNU Emacs 24.1.1
>> (x86_64-apple-darwin10.8.0)
>>
>> Are there any known fixes for this issue?
>>
>
> I cannot reproduce this. With the appended minimal .emacs,
> I get completion on the drawer names and as far as I can tell
> everything works.
>
> Nick
>
> Org-mode version 7.8.11 (release_7.8.11-605-g5f273b @
> /home/nick/elisp/org-mode/lisp/)
>
> --8<---cut here---start->8---
> ;;; -*- mode: emacs-lisp -*-
> ;;; constant part
> (add-to-list 'load-path (expand-file-name "~/src/emacs/org/org-mode/lisp"))
> (add-to-list 'load-path (expand-file-name
> "~/src/emacs/org/org-mode/contrib/lisp"))
>
> (add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\|txt\\)$" .
> org-mode))
>
> (require 'org-install)
>
> (setq debug-on-error t)
> (setq debug-on-quit t)
> (setq eval-expression-print-length nil)
> (setq eval-expression-print-level nil)
>
> (global-set-key "\C-cl" 'org-store-link)
> (global-set-key "\C-ca" 'org-agenda)
>
> ;; Define some default drawers.
> (setq org-drawers (quote ("PROPERTIES" "SETUP" "NOTES")))
> --8<---cut here---end--->8---
>
Re: [O] org2blog: referencing to other blog posts?
Hi, I hope we are talking of org2blog/wp. There's another package called org2blog authored by tehom, that works for blogger. On Sun, Aug 26, 2012 at 11:44 PM, Steinar Bang wrote: > Is there a way to reference other blog posts in org2blog, other than > using absolute URLs for that article on the server? Currently, there's no way to reference other blog posts, other than using absolute URLs. > I will use absolute URLs as a workaround, if there is no way, but it > would feel better to "work inside the system". I think using absolute URLs would be the most robust way of doing this, but of course, this process can be simplified, by providing a way of inserting those links from within org2blog. I imagine this would use link abbreviations, and provide some sort of a completion mechanism to insert links to other posts. I'll try and get to this, some time soon. > Also is there a way to link related articles, that will show up in the > wordpress blog. I haven't been using WordPress (and org2blog) for quite some time now. Is there a new feature in WordPress that lets you link related articles? Or are you using some plugin? Hope this helps, Puneeth
[O] link doesn't get fontified
In this paragraph, when I open Org, the first link does not get fontified. The other two links do. When I fill the paragraph, it gets fontified, but the paragraph does not get filled. When I fill the paragraph again, it gets filled and fontified correctly. === Most physicians and scientists are not aware of [[http://thekafkapandemic.blogspot.com/2012/01/more-you-than-you.html][disease progression]]. They are not aware that [[http://thekafkapandemic.blogspot.com/2011/06/severity.html][severe]] sufferers exist and are numerous and have [[http://thekafkapandemic.blogspot.com/2012/01/three-things-people-dont-know.html][breadth of facts]]. They are not aware of the many deaths. === I have not been able to determine the circumstances in which this occurs. It seems intermittent. It has occurred for a long time, so it is not due to a recent Org. This is not a critical bug, as it seems to only affect the Org buffer. Thanks. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com
Re: [O] exporter / org-man
On 8/24/12, Bastien wrote: >> Well, if the org-e-* stuff gets renamed to oe-* instead it becomes a >> non-issue plus it would allow to keep the old exporter around for a >> while in either contrib/ or obsolete/… otherwise I'm not too enamored >> with the double dashes. > > Yes, that's exactly the plan. Thank you. I am relieved that the old exporter will still work. I think a lot of people will still need it. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com
Re: [O] Please consider making a donation
Done. I really appreciate all the work put into Org! Thanks. On Fri, Aug 24, 2012 at 05:59:12PM +0200, Bastien wrote: > Hello all, > > I've been a freelancer for the last two months and I want to continue > this experience. > > As such, my main challenge is to discipline myself not to spend too > much time on Org -- because, as you can imagine, it *is* very tempting. > > So the more donation I receive, the more time I will have for Org. > > Any donation will first go into a new computer, as my lovely Thinkpad > X61 is about to die. > > I you think of any Emacs/Org development you would like to sponsor, > independantly from what's already existing, please send me an email. > > Thanks for your help! > > -- > Bastien > > -- Russell Adamsrlad...@adamsinfoserv.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint:1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
[O] org sync with SD/prophet/ http://syncwith.us?
Hi, New subscriber here - pushed to subscribe by someone on irc suggesting that I bounce this question up here :-) Has anyone looked at making org-mode sync with SD / http://syncwith.us ? It seems generally useful as a 'bridge' between several other defect tracking / task tracking systems - and hey, org-mode is good glue too, right? :-) Thoughts, experiences, past abortive attempts? thanks, --elijah
[O] bugs in commenting and filling
Here are 6 bugs (or at least changes that might need to be documented) in Org commenting and filling. Context: commenting and filling used to use generic Emacs facilities, but now use Org-specific ones. original: === x bug 1: the line above now does not get commented even if comment-empty-lines is t. bug 2: this line now does not indent consistently with the rest of emacs. === comment-dwim: === # x # bug 1: the line above now does not get commented even if # comment-empty-lines is t. # bug 2: this line now does not indent consistently with the # rest of emacs. === bug 3: outside of org with filladapt turned OFF, filling this paragraph does not indent it. also auto-fill indents unlike the rest of emacs. ret tab is ok. #bug 4: this paragraph now gets exported in HTML subtree #export, which will likely surprise many people who formerly #used "#" comments instead of "# " comments and don't #carefully check all output. they might #even publish private information automatically without #realizing it using old files that they forgot or did not #know to convert. #bug 5: filling this paragraph with "===" on the following #line will fill the ===, unlike the rest of emacs with #filladapt turned ON. we are supposed to not use filladapt #with org. therefore, how do you emulate the filladapt #behavior so that there is consistency between emacs and #org? Bug 6: what does the Org-specific commenting do? i was not able to determine that from the docstring to org-comment-or-uncomment-region. maybe update docstring would help others trying to find out why commenting works differently in org from the rest of emacs? Hope it helps. Thanks. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com
Re: [O] Please consider making a donation
BernardH writes: > You might want to lower the barrier to donate by providing a link to > http://orgmode.org/org-mode-donate.html ☺. Er.. I forgot :) > BTW, if it is to give you money, why not cut the middlemen and provide > your IBAN ?(As a fellow countryman, it saddened me to pay for €→$(→€ ?) > and to Visa™ and PayPal™ (which I despise) for naught. Here you go: http://lumiere.ens.fr/~guerry/u/bastien_guerry_rib_2012.jpg Thanks! -- Bastien
Re: [O] Bug with org-agenda-span & org-agenda-start-day
Hi Charles, Charles Philip Chan writes: > Bastien writes: > > Hi Bastien: > >> I'm not sure to understand what is wrong and how org-agenda-span is >> involved in the problem. > > OK, I will explain in more detail. I have set org-agenda-start-day to > "+1d" in the block. If I set "org-agenda-span" to anything but "7" (for > example "6" or "8"), the resulting agenda view is correct and the start > day is tomorrow (and span the number of days I specified). However, if I > set org-agenda-span to "7", the resulting agenda view does not start > tomorrow, but the Sunday of the current week. You need to add (org-agenda-start-on-weekday nil) to the list of properties for this agenda view. See the docstring of `org-agenda-start-on-weekday' for details. HTH, -- Bastien
Re: [O] Shouldn't comment-region protect from export ?
Nicolas Goaziou writes: > I knew I shouldn't have messed again with old exporter... Don't worry, we will get rid of them soon... I *know* what relief this will be for you! :) -- Bastien
Re: [O] Hyperlink to fileset
Hi Loris, "Loris Bennett" writes: > Achim Gratz writes: > >> Loris Bennett writes: >>> Obviously I could simply learn elisp and do this myself, as described in >>> the manual, but has anyone already implemented a link type to an emacs >>> fileset? >> >> [[elisp:(filesets-open nil "bla")][Fileset: bla]] >> >> >> Regards, >> Achim. > > Thanks. Maybe this could be added to the list of links in the manual: > > http://orgmode.org/manual/External-links.html Well, this is just one example on how to use elisp: links, so adding such hacks in Worg is fine IMO. > BTW: Can I suppress the 'yes/no' dialogue for elisp execution just for > such links? (setq org-confirm-elisp-link-function nil) See also `org-confirm-elisp-link-not-regexp'. HTH, -- Bastien
Re: [O] Small suggestion for org-taskjuggler.el
Hi Bill, Bill Day writes: > In working with org-mode's taskjuggler exporter, I have noticed that > it does not support the attributes chargeset and charge in > taskjuggler 3. These attributes are necessary to use taskjuggler's > cost estimating functions. I am not much of a coder, but I have > tried my hand at a patch. > > commit 15b522901ff0dcd8a581ad55cd4bf4c3688908ad > Author: Bill Day > Date: Sun Aug 26 16:58:32 2012 -0400 > > Modified taskjuggler to add chargeset and charge Applied in master, thanks! -- Bastien
Re: [O] comma as decimal point: bug?
Hi all, instead of having the comma as a decimal mark in all the regexps offered by the customization interface of `org-table-number-regexp', I added the comma for a new choice, which has the most liberal definition for what is a number. Using this regexp as the default will confuse the users: if they see "4,3" is aligned as a number, they will expect it to be treated as a number. This is not the case for ">3.5": even when such string is aligned as a number, the user can clearly see by herself that this cannot be part of an arithmetic operation. I think the new option offered solves this issue. Best, -- Bastien
Re: [O] Strange Problem with "org-agenda-redo"
Hi Charles, Charles Philip Chan writes: > I have a strange problem with "org-agenda-redo" and I hope that someone > can shed some light. I have an Agenda view which contains everything I > need for the day which I leave open all the time. The agenda view > already contains a schedule for the current day. A couple of days ago I > decided to add another block I called "Upcoming Events" which contains a > schedule for the next 6 days (I prefer a separate section, so that I can > easily ignore it rather then having a 7 days block). Everything is > working fine with the exception that after I mark a TODO > (scheduled/deadline) or HABIT as done, all my appointment, habits, > scheduled and deadline items disappear from the view after I save all > Agenda files and force a redisplay (s g). If I quite the view and enter > it again through the dispatcher, everything is displayed again. Mhh... This was a real bug, I had a good sweat on this one. Building agenda blocks didn't behave correctly with multiple (agenda) commands, because it reused the parameters of the last (agenda) command as the default for redoing. This is now fixed. Note that, while fixing this, I added the possibility to change the time span of one block independantly from the other: try `f' in one of your block, it should move to the next day/week and leave the other blocks untouched. Thanks for reporting this! -- Bastien
Re: [O] comma as decimal point: bug?
* Nick Dokos wrote: > Karl Voit wrote: > >> Although I totally understand that numbers with commas should be >> made possible (I am a German speaking guy) I guess there will be >> even more issues in the future as long as cosmetics and >> functionality is not aligned. > > Agreed, but IIUC the main problem is that org depends on calc for > the calculations and calc is firmly in the "decimal point MUST be > a period" camp. Although I do not have much clue about «calc» I already assumed this is the case. > So the cosmetics/functionality alignment would involve surgery on > calc, something that nobody should undertake lightly - if at all > :-). Totally agree. The point is: new users and users that does not start reading documentation before usage will not know this. And all I want to mention is that although I myself (now) understand the reasons, I also understand that (new) users will keep on misunderstand this issue until the cosmetics is aligned with the functionality of »calc«. This results in lot of traffic on this list with bug-reports on this. To avoid this, normal users should not get the alignment per default without having to read the explanation of the whole story. This is a trade-off. -- Karl Voit
Re: [O] Kudos to Auréliens and Andrew who finished the GSoC successfully!
Congrats to both of you on successfully completing these projects. Having watched the videos and played around with the merge driver locally these look like great additions to the Org-mode ecosystem. I hope these tools both receive publicity outside of the Org-mode mailing list. Ideally the gnu project will publish an announcement of successful GSOC projects. In addition it may be worthwhile to create pages for each project on the Emacs Wiki [1] and to add announcements to the front page of the orgmode.org site. Also releasing Org-sync as an ELPA package [2] could increase its visibility and user base. Cheers and thanks for the excellent contributions! Bastien writes: > I'm happy to announce Aurélien and Andrew both passed the final > evaluation for their GSoC. Join me in congratulating them :) > > See their code in action: > > Aurélien's Org-sync: > http://www.youtube.com/watch?v=kbj6-j0teCY > > Andrew's Org Merge driver (put your own favorite music): > http://www.youtube.com/watch?v=GbaaFmoEfGw > > If you want to test the code: > > ~$ git clone git://orgmode.org/org-sync.git > ~$ git clone git://orgmode.org/org-merge-driver.git > > I'm really glad they went so far in these projects, despite > the fact that I could not support them as much as I wanted. > > Here are some notes they shared with me about their project, > don't hesitate to pick up some news and ask questions. > > Enjoy! > [...] Footnotes: [1] http://www.emacswiki.org/ [2] http://tromey.com/elpa/ The following has the best documentation I've found on how to bundle an ELPA package (just ignore the Marmalade-specific parts). http://marmalade-repo.org/doc-files/package.5.html -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] comma as decimal point: bug?
Karl Voit wrote: > * Nicolas Goaziou wrote: > > > > Rainer Thiel writes: > > > >> I have seen that as of v. 7.9, org tables are supposed to accept > >> commas as decimal points which is useful if you set up tables to be > >> used in in files where continental conventions are expected to be > >> followed. > > > > Actually, this more subtle. Tables recognize numbers with a comma as the > > decimal mark. But it only means such numbers will be properly aligned to > > the right. Internally, calculations still require dot separator. > > When I read the change-list of Org, I bet that there *will* be > problems because of this cosmetic change :-) > > From user experience perspective, it is quite clear that «Org > recognizes numbers with commas» will be mixed up with «Org can > calculate with numbers containing commas». You can not make this > clear - even with renaming the settings variable. > > Although I totally understand that numbers with commas should be > made possible (I am a German speaking guy) I guess there will be > even more issues in the future as long as cosmetics and > functionality is not aligned. > Agreed, but IIUC the main problem is that org depends on calc for the calculations and calc is firmly in the "decimal point MUST be a period" camp. So the cosmetics/functionality alignment would involve surgery on calc, something that nobody should undertake lightly - if at all :-). I believe the above statement is correct but if anybody has better information, please correct me. Nick
Re: [O] comma as decimal point: bug?
* Nicolas Goaziou wrote: > > Rainer Thiel writes: > >> I have seen that as of v. 7.9, org tables are supposed to accept >> commas as decimal points which is useful if you set up tables to be >> used in in files where continental conventions are expected to be >> followed. > > Actually, this more subtle. Tables recognize numbers with a comma as the > decimal mark. But it only means such numbers will be properly aligned to > the right. Internally, calculations still require dot separator. When I read the change-list of Org, I bet that there *will* be problems because of this cosmetic change :-) >From user experience perspective, it is quite clear that «Org recognizes numbers with commas» will be mixed up with «Org can calculate with numbers containing commas». You can not make this clear - even with renaming the settings variable. Although I totally understand that numbers with commas should be made possible (I am a German speaking guy) I guess there will be even more issues in the future as long as cosmetics and functionality is not aligned. Just my 2 cents ... -- Karl Voit
Re: [O] Please consider making a donation
+1 Je Sun, Aug 26, 2012 at 07:19:46PM + BernardH skribis: > Bastien altern.org> writes: > > > > > Hello all, > > > > I've been a freelancer for the last two months and I want to continue > > this experience. > > > > As such, my main challenge is to discipline myself not to spend too > > much time on Org -- because, as you can imagine, it *is* very tempting. > > > > So the more donation I receive, the more time I will have for Org. > > Great ! > You might want to lower the barrier to donate by providing a link to > http://orgmode.org/org-mode-donate.html ☺. > > BTW, if it is to give you money, why not cut the middlemen and provide > your IBAN ?(As a fellow countryman, it saddened me to pay for €→$(→€ ?) > and to Visa™ and PayPal™ (which I despise) for naught. > > Kudos for your great work on Org ! > > B. > > -- :: Igor Sosa Mayor :: joseleopoldo1...@gmail.com :: :: GnuPG: 0x1C1E2890 :: http://www.gnupg.org/ :: :: jabberid: rogorido :::: pgpxjIWhgWs1Y.pgp Description: PGP signature
Re: [O] Please consider making a donation
I also donated a bit :) Thanks for the great work! - Waldemar On Sat, Aug 25, 2012 at 12:59 AM, Bastien wrote: > Hello all, > > I've been a freelancer for the last two months and I want to continue > this experience. > > As such, my main challenge is to discipline myself not to spend too > much time on Org -- because, as you can imagine, it *is* very tempting. > > So the more donation I receive, the more time I will have for Org. > > Any donation will first go into a new computer, as my lovely Thinkpad > X61 is about to die. > > I you think of any Emacs/Org development you would like to sponsor, > independantly from what's already existing, please send me an email. > > Thanks for your help! > > -- > Bastien > >
Re: [O] Subtasks cookies out of export
Hello, William Léchelle writes: > I don't know how much is this feature used, nor specifically for exporting, > but I do believe such an entry belongs to the #+OPTIONS line (just like > priorities, tags, etc.) I have added it in the new exporter: #+OPTIONS: stat:nil (and global variable `org-export-with-statistics-cookies'). Regards, -- Nicolas Goaziou
Re: [O] [new exporter] Problems with entities
Hello, Thomas Holst writes: > Now it works as expected and explained by you. There was an error in my > initial version. It was only a list not a list containing lists. Actually, I overlooked the second part of your example: Dies ist eine Ligatur: f\/ifteen \alpha ab\-cd. ab\-cd should be exported as-as, not as ab$\backslash$-cd, since "\-" is considered as a special string (see `org-export-with-special-strings'). I fixed that mistake in the new exporter. Thanks again. Regards, -- Nicolas Goaziou
Re: [O] #+INCLUDE broken (or changed) in org-mode 7.9? Help!
My bad. Thanks, guys!
On Mon, Aug 27, 2012 at 3:12 AM, Nicolas Goaziou wrote:
> Hello,
>
> Nick Dokos writes:
>
> > And there seems to be a bug in the easy template code in org.el:
> > line 11390 says
> >
> > ("I" "#+INCLUDE %file ?"
> >
> > and it seems to be missing the colon.
>
> Fixed. Thank you.
>
>
> Regards,
>
> --
> Nicolas Goaziou
>
--
Bill Day
williamson@gmail.com
Re: [O] Preserving the geometry of a table range
Hi Jarmo On Sun, Aug 26, 2012 at 8:54 AM, Jarmo Hurri wrote: > I ran into this problem while trying to make a contribution by > implementing functions corresponding to vlookup and hlookup in > traditional spreadsheets. I have only used relatively basic properties > of org, so there might be a simple solution that I just don't know. Only now I see that this second part with the actual problem of your original post is still unanswered. Does this help?: | key (ordered) | val | | val (ordered) | key | |---+-+---+---+-| | 8 | foo | | bar | 42 | |42 | bar | | foo | 8 | #+TBLFM: $5 = '(nth (position $4 '(@<<$2..@>$2) :test 'equal) '(@<<$1..@>$1)) Michael
Re: [O] comma as decimal point: bug?
Am Montag, 27. August 2012, 11:08:59 schrieb Rainer Thiel: > ... > As a user, I can say it would be an advantage when exporting org-files > to LaTeX or ODT etc. > > Many thanks again and best wishes > > Rainer Exporting tables to LaTeX usually is not the last step, obviously you will compile the exported *.tex file into a *.pdf. Right? So stick to a dot as the decimal point in *.org and in *.tex, but use the numprint package to get a table in your *.pdf with commas as decimal points. We had that discussion here and William Henney gave an example in an email dated 22 April 2012. Regards, Alexander
Re: [O] Shouldn't comment-region protect from export ?
On Mon, 27 Aug 2012 12:16:22 +0200, Nicolas Goaziou spake thus: >William Léchelle writes: >> Only now, my #+latex_header: is not properly exported, and rather protected >> and displayed in the document. I didn't check before the patch, but I guess >> it >> worked all right. I'm using subtree export, in case that matters. >I knew I shouldn't have messed again with old exporter... >Anyway, I pushed a fix to the fix. Does it behave as expected now? Yes, it works perfectly, thank you very much ! -- William
Re: [O] Shouldn't comment-region protect from export ?
Hello, William Léchelle writes: > Only now, my #+latex_header: is not properly exported, and rather protected > and displayed in the document. I didn't check before the patch, but I guess it > worked all right. I'm using subtree export, in case that matters. I knew I shouldn't have messed again with old exporter... Anyway, I pushed a fix to the fix. Does it behave as expected now? Regards, -- Nicolas Goaziou
Re: [O] Subtasks cookies out of export
On Mon, 27 Aug 2012 11:41:56 +0200, Nicolas Goaziou spake thus: >> I use subtasks cookies in titles, as described in >> http://orgmode.org/manual/Breaking-down-tasks.html, along with todo keywords, >> when writing a document to be exported, and I'd like then NOT to be exported >> (for they're org metadata). Exporting to pdf, still using the default >> exporter. I would have guess there would be an #+option for that (removing >> the >> progress cookies), but I didn't find it in the export options page. >> >> How much is that possible ? >In the default exporter, you can add a function to >`org-export-preprocess-hook' which will carefully remove every >statistics cookie en the buffer. >In the next exporter, you can still use that hook (named >`org-export-before-parsing-hook' this time) or use the following: > >So, it [is] quite simple already to ignore them. I'm convinced, only I (still) lack the lisp knowledge to write such functions :/ >Do you (and other users) think it's worth to add a customizable variable and >an entry in the #+OPTIONS: line (perhaps with a "stat:nil" value) to achieve >the same? I don't know how much is this feature used, nor specifically for exporting, but I do believe such an entry belongs to the #+OPTIONS line (just like priorities, tags, etc.) Thanks for dealing with this, William
Re: [O] [new exporter] Problems with entities
Hi Nicolas,
· Nicolas Goaziou wrote:
> Hello,
>
> Thomas Holst writes:
>
>> While testing the new exporter we encountered problems with entities. We
>> tried to make ligations work. In LaTeX you write '\/' for a ligation
>> e.g. 'f\/ifteen'. To achieve that we set `org-entities-user':
>>
>> #+BEGIN_SRC emacs-lisp
>> (setq org-entities-user
>> '("Ligatur" "\\/" nil "" "" "" ""))
>> #+END_SRC
>>
[ ... ]
>
> You have defined an entity named "Ligatur". If you want to apply it
> during export, you have to write either \Ligatur or \Ligatur{}. For
> example, \alpha is correctly exported since there is:
>
> ("alpha" "\\alpha" t "α" "alpha" "alpha" "α")
>
> in `org-entities'.
>
> Note that old exporter doesn't apply your entity either (entities usage
> doesn't change between both exporters). It just gives up each time he
> sees a backslash which isn't followed by a known entity name, assuming
> this will be handled by LaTeX.
thanks for explaining. I now have:
#+BEGIN_SRC emacs-lisp
(setq org-entities-user
'(("lig" "\\/" nil "" "" "" "")))
#+END_SRC
Now it works as expected and explained by you. There was an error in my
initial version. It was only a list not a list containing lists.
Thanks again.
--
Bis neulich ...
Thomas
Re: [O] Shouldn't comment-region protect from export ?
On Mon, 27 Aug 2012 11:24:21 +0200, Nicolas Goaziou spake thus: >> Having just pulled from git, comment-region still gets me indented "#" lines, >> which still get exported (using the default exporter). >> >> How is it supposed to be fixed ? >I have pushed a patch against current exporter. Inlined comments should >be properly removed now. Thanks, indeed, these no longer appear. Only now, my #+latex_header: is not properly exported, and rather protected and displayed in the document. I didn't check before the patch, but I guess it worked all right. I'm using subtree export, in case that matters.
Re: [O] Subtasks cookies out of export
Hello, William LÉCHELLE writes: > I use subtasks cookies in titles, as described in > http://orgmode.org/manual/Breaking-down-tasks.html, along with todo keywords, > when writing a document to be exported, and I'd like then NOT to be exported > (for they're org metadata). Exporting to pdf, still using the default > exporter. I would have guess there would be an #+option for that (removing the > progress cookies), but I didn't find it in the export options page. > > How much is that possible ? In the default exporter, you can add a function to `org-export-preprocess-hook' which will carefully remove every statistics cookie en the buffer. In the next exporter, you can still use that hook (named `org-export-before-parsing-hook' this time) or use the following: #+BEGIN_SRC emacs-lisp (defun my-ignore-stat-cookies (cookie backend info) "Ignore every statistics cookie in every export back-end." "") (add-to-list 'org-export-filter-statistics-cookie-functions 'my-ignore-stat-cookies) #+END_SRC So, it will quite simple already to ignore them. Do you (and other users) think it's worth to add a customizable variable and an entry in the #+OPTIONS: line (perhaps with a "stat:nil" value) to achieve the same? Regards, -- Nicolas Goaziou
Re: [O] [new exporter] Problems with entities
Hello,
Thomas Holst writes:
> While testing the new exporter we encountered problems with entities. We
> tried to make ligations work. In LaTeX you write '\/' for a ligation
> e.g. 'f\/ifteen'. To achieve that we set `org-entities-user':
>
> #+BEGIN_SRC emacs-lisp
> (setq org-entities-user
> '("Ligatur" "\\/" nil "" "" "" ""))
> #+END_SRC
>
> The following text is used to show the problem:
>
> Dies ist eine Ligatur: f\/ifteen \alpha ab\-cd.
>
> With the old exporter the translation to LaTeX is:
>
> Dies ist eine Ligatur: f\/ifteen $\alpha$ ab\-cd.
>
> Which is the expected result. With the new exporter we get:
>
> Dies ist eine Ligatur: f$\backslash$/ifteen $\alpha$
> ab$\backslash$-cd.
>
> As you can see the shy hyphen is also wrong. But \alpha is exported
> correctly. So I don't know what is happening here.
You have defined an entity named "Ligatur". If you want to apply it
during export, you have to write either \Ligatur or \Ligatur{}. For
example, \alpha is correctly exported since there is:
("alpha" "\\alpha" t "α" "alpha" "alpha" "α")
in `org-entities'.
Note that old exporter doesn't apply your entity either (entities usage
doesn't change between both exporters). It just gives up each time he
sees a backslash which isn't followed by a known entity name, assuming
this will be handled by LaTeX.
HTH,
Regards,
--
Nicolas Goaziou
Re: [O] Shouldn't comment-region protect from export ?
Hello, William Léchelle writes: > Having just pulled from git, comment-region still gets me indented "#" lines, > which still get exported (using the default exporter). > > How is it supposed to be fixed ? I have pushed a patch against current exporter. Inlined comments should be properly removed now. Thanks for reporting this. Regards, -- Nicolas Goaziou
[O] [new exporter] Problems with entities
Hello,
first I want to thank you all for org-mode 7.9! The list of changes is
incredible!
While testing the new exporter we encountered problems with entities. We
tried to make ligations work. In LaTeX you write '\/' for a ligation
e.g. 'f\/ifteen'. To achieve that we set `org-entities-user':
#+BEGIN_SRC emacs-lisp
(setq org-entities-user
'("Ligatur" "\\/" nil "" "" "" ""))
#+END_SRC
The following text is used to show the problem:
Dies ist eine Ligatur: f\/ifteen \alpha ab\-cd.
With the old exporter the translation to LaTeX is:
Dies ist eine Ligatur: f\/ifteen $\alpha$ ab\-cd.
Which is the expected result. With the new exporter we get:
Dies ist eine Ligatur: f$\backslash$/ifteen $\alpha$
ab$\backslash$-cd.
As you can see the shy hyphen is also wrong. But \alpha is exported
correctly. So I don't know what is happening here.
--
Bis neulich ...
Thomas
Re: [O] comma as decimal point: bug?
Hi Bastien, hi Nicolas, 2012/8/26 Bastien : > But I guess it's confusing to align numbers as if they were numbers, > and to then tell the users "well, they are not really numbers." I myself indeed was confused, but now that I know it only concerns aligning of numbers I have no problem living with it. I had be surprised by the supposed change, anyway, because Bastien (I think) in earlier versions of the manual had most definitely excluded to allow commas to be used as decimal points. I am not a programmer and are probably unaware of the problems coming up when allowing both dots and commas to be used as decimal points. As a user, I can say it would be an advantage when exporting org-files to LaTeX or ODT etc. Many thanks again and best wishes Rainer -- Prof. Dr. Rainer Thiel Institut für Altertumswissenschaften 07737 Jena, Germany (EU) r.th...@uni-jena.de
Re: [O] Shouldn't comment-region protect from export ?
On Thu, 02 Aug 2012 18:40:04 +0200, Bastien spake thus: >William LÉCHELLE writes: >> Using org-mode for export (to pdf), I find myself using comment-region often >> enough, in sections meant to be exported, on indented text lines (e.g. for >> drafting). This inserts "# " at the "beginning" of the line, after the >> indentation, thus not achieving what I wanted comment-region to do >> (i.e. "don't export this"). >This is fixed now, thanks. Having just pulled from git, comment-region still gets me indented "#" lines, which still get exported (using the default exporter). How is it supposed to be fixed ?
Re: [O] Hyperlink to fileset
Achim Gratz writes: > Loris Bennett writes: >> Obviously I could simply learn elisp and do this myself, as described in >> the manual, but has anyone already implemented a link type to an emacs >> fileset? > > [[elisp:(filesets-open nil "bla")][Fileset: bla]] > > > Regards, > Achim. Thanks. Maybe this could be added to the list of links in the manual: http://orgmode.org/manual/External-links.html BTW: Can I suppress the 'yes/no' dialogue for elisp execution just for such links? Loris
[O] Subtasks cookies out of export
Hi list, I use subtasks cookies in titles, as described in http://orgmode.org/manual/Breaking-down-tasks.html, along with todo keywords, when writing a document to be exported, and I'd like then NOT to be exported (for they're org metadata). Exporting to pdf, still using the default exporter. I would have guess there would be an #+option for that (removing the progress cookies), but I didn't find it in the export options page. How much is that possible ? Thanks in advance.
Re: [O] Projects in workflow/agenda setup question
Hi Nathan, Nathan Neff writes: > * Project 1 > ** TODO Task 1 > ** TODO Task 2 > Hitting `C-c C-x <' on "* Project 1" then M-x org-agenda RET t shows me all the TODO. Maybe you have something in your config that prevents this? -- Bastien
Re: [O] Does html table export require that the top row be treated as a header?
Hi John,
John Hendy writes:
> I have a document I will export via pdf and html. My table is like so:
>
> #+attr_latex: align={lp{0.8\textwidth}}
> #+attr_html: width="600px"
> | *R1* | stuff|
> |--+--|
> | *R2* | more stuff |
> |--+--|
> | *R2* | some third stuff |
>
> I'd like horizontal separators in LaTeX and don't care one way or the
> other for html so since there didn't seem to be a way to have them in
> one and not the other I inserted them. When I export the html, it
> looks as though since I have separators it exports the top row as
> class=th instead of tr like a normal row. This bolds and centers it.
>
> Any way to have it treat the top row as a regular row in the presence
> of midlines?
#+BIND: org-export-table-header-tags ("" . "")
HTH,
--
Bastien
Re: [O] #+INCLUDE broken (or changed) in org-mode 7.9? Help!
Hello,
Nick Dokos writes:
> And there seems to be a bug in the easy template code in org.el:
> line 11390 says
>
> ("I" "#+INCLUDE %file ?"
>
> and it seems to be missing the colon.
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
Re: [O] build failure
Neuwirth Erich univie.ac.at> writes: > Pulling the latest version and building it made the problem disappear. > org-version says > 7.9 (release_7.9-80-gf29660.dirty) What have you changed to make it "dirty"? Regards, Achim.
Re: [O] build failure
Pulling the latest version and building it made the problem disappear. org-version says 7.9 (release_7.9-80-gf29660.dirty) On Aug 26, 2012, at 10:50 PM, Bastien wrote: > Hi Erich, > > Erich Neuwirth writes: > >> I just pulled the latest version of the sources on my MacBook with OSX 10.8.1 >> >> Buildung does not work any more, here is the error. >> Loading /Users/neuwirth/devel/org-mode/lisp/org-compat.el (source)... >> Cannot open load file: ../UTILITIES/org-fixup.el >> make[1]: *** [org-version.el] Error 255 >> make: *** [all] Error 2 > > Looks like you're behind commit bf352eced, where org-compat.el has been > updated so that it loads utils/org-fixup.el, not UTILITIES/org-fixup.el > > Please pull again from git, this is fixed there. > >> So I installed the latest version from ELPA > > Yes -- still several things to fix to get a working ELPA version. > We're on it. > > Let us know if git pull does it for you. Thanks! > > -- > Bastien
