Re: [O] (org-element-context) :end property
Aloha all, Nicolas Goaziou writes: > Hello, > > > White spaces following an object are included in the object. They are > stored in :post-blank property. You can add them with > > (setf (buffer-substring start end) > (concat (or desc path) > (make-string (org-element-property :post-blank eop) ?\s))) To wrap this up, the revised unlinkify function (and a hydra with the org-link-edit functions) are here: https://github.com/abo-abo/hydra/wiki/Org-mode-links All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Bug: org-babel-tangle-publish fails in copy-file step [8.3.1 (release_8.3.1-241-gea7ac0 @ /home/arunisaac/.emacs.d/org-mode/lisp/)]
Arun I writes: > When publishing files using org-babel-tangle-publish, if the :tangle > header argument is given to a source block, and if org-babel-tangle-publish > is called from a directory other than the directory in which the source > file (that is, the file being tangled) exists, then org-babel-tangle-publish > fails in the copy-file step. Thanks for the detailed report and reproducible example, and sorry for the late reply. Fixed in 36233d976d. -- Kyle
Re: [O] Capture abort: (user-error Can't preview LaTeX fragment in a non-file buffer)
On Wed, Sep 30, 2015 at 3:22 PM, Fanpeng Kong wrote: > Hi all, > > I tried to setup my org-mode according to Bernt Hansen’s wonderful > documentation: > > http://doc.norang.ca/org-mode.html#Capture > > But later I found I got problem with Org Capture as in Section 6. when I > typed C-c c, an error message "Capture abort: (user-error Can't preview > LaTeX fragment in a non-file buffer)” occured. After lots of search on the > web I still can not solve it. I am wondering is there anyone can help me > out? Thanks in advance! Maybe you should type C-c C-c to finish the capture. > Things I have tried: > 1. Test Latex preview in org file: > http://orgmode.org/worg/org-tutorials/org-latex-preview.html > Both “dvipng” and “imagemagick” setup methods work fine, I can preview Latex > formula in .org file. > > 2. Use the method described here: > http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=168c5584f5a41c4c0890f4caa89fc11cff021c4e > I replace my “org-mode” package with the one in the link which is supposed > to solve the problem, however, I still got the same error message. > > Versions of some packages I am using: > 1. Emacs: GNU Emacs 24.4.1 (x86_64-apple-darwin13.4.0, NS > apple-appkit-1265.21) of 2014-10-21 on builder10-9.porkrind.org > 2. AucTeX: 11.88.8 > 3. org-mode: Org-mode version 8.3.1 (8.3.1-146-gfd8a18-elpa @ > /Users/xiaok/.emacs.d/elpa/org-20150928/) > > Cheers, > Fanpeng > > > > > > > > -- Yours faithfully, Tian Qiu
Re: [O] (org-element-context) :end property
Aloha Nicolas, Nicolas Goaziou writes: > White spaces following an object are included in the object. They are > stored in :post-blank property. You can add them with > > (setf (buffer-substring start end) > (concat (or desc path) > (make-string (org-element-property :post-blank eop) ?\s))) Perfect. Thanks! All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Bug: Exporting smart single quotes in Org 8.3 seems broken [8.3.2 (8.3.2-elpa @ /Users/jonathan/.emacs.d/elpa/org-20150929/)]
Nicolas Goaziou writes: > Also, I think it would be clearer to rename `opening-double-quote' to > `opening-primary-quote' and `opening-single-quote' to > `opening-secondary-quote'. WDYT? In fact, I thought they needed renaming as well in light of the redefinition of " and '. Rasmus -- Hooray!
Re: [O] Bug: Exporting smart single quotes in Org 8.3 seems broken [8.3.2 (8.3.2-elpa @ /Users/jonathan/.emacs.d/elpa/org-20150929/)]
Rasmus writes:
> Jonathan Oddie writes:
>
>> Hello Nicolas,
>>
>> Thanks for your response.
>>
However, I could customize `org-export-smart-quotes-alist' to export
outer quotes using single quote marks and inner quotes using double
quote marks.
Is that about right?
>>>
>>> Correct. However, `org-export-smart-quotes-alist' aims to be
>>> typographically correct for all handled languages, so it is not
>>> customizable.
>>
>> In British English, I believe standard typographical style uses single
>> quotation marks for normal quotations, and double quotation marks for inner
>> quotations.
>>
>> I can obtain this behaviour with Org 8.3 by evaluating the following form in
>> *scratch*:
>>
>> (push
>> '("en-GB"
>>(opening-single-quote :utf-8 "“" :html "“" :latex "``" :texinfo
>> "``")
>>(closing-single-quote :utf-8 "”" :html "”" :latex "''" :texinfo
>> "''")
>>(opening-double-quote :utf-8 "‘" :html "‘" :latex "`" :texinfo
>> "`")
>>(closing-double-quote :utf-8 "’" :html "’" :latex "'" :texinfo
>> "'")
>>(apostrophe :utf-8 "’" :html "’"))
>> org-export-smart-quotes-alist)
>>
>> and then adding #+LANGUAGE: en-GB to my input org-mode file (sample input
>> and output below).
>>
>> Would a patch to this effect be acceptable for a future Org release? (I
>> would also be happy to contribute a documentation patch for the manual).
>
> I think this would be nice. In ox-latex, 'en-GB' is recognized by both
> babel or polyglossia.
I agree.
Also, I think it would be clearer to rename `opening-double-quote' to
`opening-primary-quote' and `opening-single-quote' to
`opening-secondary-quote'. WDYT?
Regards,
Re: [O] (org-element-context) :end property
Hello, Thomas S. Dye writes: > I've started to use John Kitchin's unlinkify function, which he posted > to the list last year. > > (defun jk/unlinkify () > "Replace an org-link with the description, or if this absent, the path." > (interactive) > (let ((eop (org-element-context))) > (when (eq 'link (car eop)) > (message "%s" eop) > (let* ((start (org-element-property :begin eop)) > (end (org-element-property :end eop)) > (contents-begin (org-element-property :contents-begin eop)) > (contents-end (org-element-property :contents-end eop)) > (path (org-element-property :path eop)) > (desc (and contents-begin > contents-end > (buffer-substring contents-begin contents-end > (setf (buffer-substring start end) (or desc path)) > > However, I get different results depending on whether the link ends with > a space or a character, e.g. > > Foo [[http:www.tsdye.com][desc]] bar. > Foo [[http:www.tsdye.com][desc]], bar. > > Foo descbar. > Foo desc, bar. > > How can I fix this? I'm guessing that org-element-context sets :end > differently depending on the character following the link? White spaces following an object are included in the object. They are stored in :post-blank property. You can add them with (setf (buffer-substring start end) (concat (or desc path) (make-string (org-element-property :post-blank eop) ?\s))) Regards, -- Nicolas Goaziou
[O] (org-element-context) :end property
Aloha all, I've started to use John Kitchin's unlinkify function, which he posted to the list last year. (defun jk/unlinkify () "Replace an org-link with the description, or if this absent, the path." (interactive) (let ((eop (org-element-context))) (when (eq 'link (car eop)) (message "%s" eop) (let* ((start (org-element-property :begin eop)) (end (org-element-property :end eop)) (contents-begin (org-element-property :contents-begin eop)) (contents-end (org-element-property :contents-end eop)) (path (org-element-property :path eop)) (desc (and contents-begin contents-end (buffer-substring contents-begin contents-end (setf (buffer-substring start end) (or desc path)) However, I get different results depending on whether the link ends with a space or a character, e.g. Foo [[http:www.tsdye.com][desc]] bar. Foo [[http:www.tsdye.com][desc]], bar. Foo descbar. Foo desc, bar. How can I fix this? I'm guessing that org-element-context sets :end differently depending on the character following the link? All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] org-capture-templates with multi charachter keys
Hello,
"tenspd137 ." writes:
> (setq org-capture-templates
> '(("t" "Todo" entry (file+headline (concat org-directory
> "/default.org") "Tasks")
> "* TODO %?\n %i\n %a")
> ("j" "Journal" entry (file+datetree (concat org-directory
> "/journal.org"))
> "* %?\nEntered on %U\n %i\n %a")
> ;;product stuff - I would like to move these to files and have
> ;;them loaded - maybe in the future
> ("bf" "Bluefin Todo" entry (file+headline (concat
> org-directory "/bluefin.org") "Tasks")
> "* TODO %?\n %i\n %a")))
>
> the last one I am using "bf" as a key. When I go to use org capture,
> the following is shown in the menu
>
> Select a capture template
> ===
>
> [t] Todo
> [j] Journal
> [bf] Bluefin Todo
>
> [C] Customize org-capture-templates
> [q] Abort
>
> but when I hit b (as in bf), the mini-buffer just says invalid key `b'
>
> How do I use multiple keys?
I think you're missing this bit from org-capture-templates's docstring:
When using several keys, keys using the same prefix key must be
together in the list and preceded by a 2-element entry explaining
the prefix key, for example
("b" "Templates for marking stuff to buy")
--
Kyle
Re: [O] Bug: Exporting smart single quotes in Org 8.3 seems broken [8.3.2 (8.3.2-elpa @ /Users/jonathan/.emacs.d/elpa/org-20150929/)]
Jonathan Oddie writes:
> Hello Nicolas,
>
> Thanks for your response.
>
>>> However, I could customize `org-export-smart-quotes-alist' to export
>>> outer quotes using single quote marks and inner quotes using double
>>> quote marks.
>>>
>>> Is that about right?
>>
>> Correct. However, `org-export-smart-quotes-alist' aims to be
>> typographically correct for all handled languages, so it is not
>> customizable.
>
> In British English, I believe standard typographical style uses single
> quotation marks for normal quotations, and double quotation marks for inner
> quotations.
>
> I can obtain this behaviour with Org 8.3 by evaluating the following form in
> *scratch*:
>
> (push
> '("en-GB"
>(opening-single-quote :utf-8 "“" :html "“" :latex "``" :texinfo
> "``")
>(closing-single-quote :utf-8 "”" :html "”" :latex "''" :texinfo
> "''")
>(opening-double-quote :utf-8 "‘" :html "‘" :latex "`" :texinfo
> "`")
>(closing-double-quote :utf-8 "’" :html "’" :latex "'" :texinfo
> "'")
>(apostrophe :utf-8 "’" :html "’"))
> org-export-smart-quotes-alist)
>
> and then adding #+LANGUAGE: en-GB to my input org-mode file (sample input and
> output below).
>
> Would a patch to this effect be acceptable for a future Org release? (I
> would also be happy to contribute a documentation patch for the manual).
I think this would be nice. In ox-latex, 'en-GB' is recognized by both
babel or polyglossia.
Rasmus
--
And I faced endless streams of vendor-approved Ikea furniture. . .
[O] org-capture-templates with multi charachter keys
Hi all,
I can't seem to find an answer for this, maybe someone could tell me
what I am doing wrong. Based on what I read in the manual and
examples I have seen, the following is valid for creating
org-capture-templates:
(setq org-capture-templates
'(("t" "Todo" entry (file+headline (concat org-directory
"/default.org") "Tasks")
"* TODO %?\n %i\n %a")
("j" "Journal" entry (file+datetree (concat org-directory
"/journal.org"))
"* %?\nEntered on %U\n %i\n %a")
;;product stuff - I would like to move these to files and have
;;them loaded - maybe in the future
("bf" "Bluefin Todo" entry (file+headline (concat
org-directory "/bluefin.org") "Tasks")
"* TODO %?\n %i\n %a")))
the last one I am using "bf" as a key. When I go to use org capture,
the following is shown in the menu
Select a capture template
===
[t] Todo
[j] Journal
[bf] Bluefin Todo
[C] Customize org-capture-templates
[q] Abort
but when I hit b (as in bf), the mini-buffer just says invalid key `b'
How do I use multiple keys?
Thanks!
-C
Re: [O] Bug: Exporting smart single quotes in Org 8.3 seems broken [8.3.2 (8.3.2-elpa @ /Users/jonathan/.emacs.d/elpa/org-20150929/)]
Hello Nicolas,
Thanks for your response.
>> However, I could customize `org-export-smart-quotes-alist' to export
>> outer quotes using single quote marks and inner quotes using double
>> quote marks.
>>
>> Is that about right?
>
> Correct. However, `org-export-smart-quotes-alist' aims to be
> typographically correct for all handled languages, so it is not
> customizable.
In British English, I believe standard typographical style uses single
quotation marks for normal quotations, and double quotation marks for inner
quotations.
I can obtain this behaviour with Org 8.3 by evaluating the following form in
*scratch*:
(push
'("en-GB"
(opening-single-quote :utf-8 "“" :html "“" :latex "``" :texinfo
"``")
(closing-single-quote :utf-8 "”" :html "”" :latex "''" :texinfo
"''")
(opening-double-quote :utf-8 "‘" :html "‘" :latex "`" :texinfo "`")
(closing-double-quote :utf-8 "’" :html "’" :latex "'" :texinfo "'")
(apostrophe :utf-8 "’" :html "’"))
org-export-smart-quotes-alist)
and then adding #+LANGUAGE: en-GB to my input org-mode file (sample input and
output below).
Would a patch to this effect be acceptable for a future Org release? (I would
also be happy to contribute a documentation patch for the manual).
Thanks,
Jonathan
==
test.org input:
==
#+OPTIONS: ':t
#+LANGUAGE: en-GB
This is "a quotation."
This is "a quotation with 'an inner quotation'".
This sentence doesn't contain a contraction.
This quotation "doesn't" contain a contraction.
This "nested quotation 'doesn't' contain a contraction."
This "nested quotation 'doesn't contain' a contraction."
==
UTF-8 output:
==
This is ‘a quotation.’
This is ‘a quotation with “an inner quotation”’.
This sentence doesn’t contain a contraction.
This quotation ‘doesn’t’ contain a contraction.
This ‘nested quotation “doesn’t” contain a contraction.’
This ‘nested quotation “doesn’t contain” a contraction.’
> Also, this variable predates the new algorithm, so it introduces some
> confusion in its entries: there, "opening-double-quote" should be
> understood as "opening-outer-quote" and "opening-single-quote" as
> "opening-inner-quote", or some such.
>
> Regards,
Re: [O] Scheduling a meeting every week for a given time
Hi Claude. Claude Fuhrer writes: I'm trying to add recurring events, but only for a given period of time. You should probably use org-class. See below. For example, I would like to write: Project meeting, every monday between 10:00 and 12:00 from 1. October until 1. December 2015 %%(org-class 2015 10 1 2015 12 1 1) 10:00-12:00 Project meeting or Staff conference, every friday from 15:00 to 17:00, during seven weeks %%(org-class 2015 10 1 2015 11 1 5) 15:00-17:00 Staff conference Best, -- Jorge.
Re: [O] Bug: Exporting smart single quotes in Org 8.3 seems broken [8.3.2 (8.3.2-elpa @ /Users/jonathan/.emacs.d/elpa/org-20150929/)]
Jonathan Oddie writes: > Thank you for the explanation. Just to make sure I understand: it > sounds like '...' and "..." should be thought of as markup, with "..." > always used for outer quotes and '...' for inner quotes in org-mode > source files. > > However, I could customize `org-export-smart-quotes-alist' to export > outer quotes using single quote marks and inner quotes using double > quote marks. > > Is that about right? Correct. However, `org-export-smart-quotes-alist' aims to be typographically correct for all handled languages, so it is not customizable. Also, this variable predates the new algorithm, so it introduces some confusion in its entries: there, "opening-double-quote" should be understood as "opening-outer-quote" and "opening-single-quote" as "opening-inner-quote", or some such. Regards,
[O] Scheduling a meeting every week for a given time
Hi I'm trying to add recurring events, but only for a given period of time. For example, I would like to write: Project meeting, every monday between 10:00 and 12:00 from 1. October until 1. December 2015 or Staff conference, every friday from 15:00 to 17:00, during seven weeks I've tried something like: *** Project meeting DEADLINE: <2015-09-07 lun 12:45-14:20 +1w>--<2015-10-19 lun> But this event then appear every in my agenda. What is the good syntax for that ? Thank you for your help
Re: [O] Bug: Exporting smart single quotes in Org 8.3 seems broken [8.3.2 (8.3.2-elpa @ /Users/jonathan/.emacs.d/elpa/org-20150929/)]
Hello Nicolas, > The smart quotes algorithm changed. Now "..." are always level 1 quotes, > and '...' and always level 2. IOW, '...' are not treated as smart quotes > if they are not located within "...". > > Note that for a given language, "..." can still be treated as single > quotes and '...' as double quotes. Thank you for the explanation. Just to make sure I understand: it sounds like '...' and "..." should be thought of as markup, with "..." always used for outer quotes and '...' for inner quotes in org-mode source files. However, I could customize `org-export-smart-quotes-alist' to export outer quotes using single quote marks and inner quotes using double quote marks. Is that about right? Thanks, Jonathan
Re: [O] Bug: Exporting smart single quotes in Org 8.3 seems broken [8.3.2 (8.3.2-elpa @ /Users/jonathan/.emacs.d/elpa/org-20150929/)]
Hello, Jonathan Oddie writes: > (This is a duplicate of a Stackexchange question posted at > http://emacs.stackexchange.com/questions/17061/is-exporting-of-smart-single-quotes-broken-in-org-8-3) > > I cannot seem get single quotes to export as 'smart' quotes under Org > 8.3.2. Here is a minimal file that reproduces the problem: > > #+OPTIONS: ':t > #+LANGUAGE: en > > This is 'within single quotes'. This is "within double quotes". > > Expected behavior: from "emacs -Q", under which "M-x org-version" > reports 8.2.10, the output when exporting to UTF-8 plaintext is: > > This is ‘within single quotes’. This is “within double quotes” > > and the output when exporting to LaTeX is: > > This is `within single quotes'. This is ``within double quotes''. > > If I load the most recent version of org-mode (starting from "emacs -Q", > typing "M-x package-initialize RET", and "M-x load-library RET org > RET"), "org-version" reports 8.3.2, and the output no longer correctly > translates single quotes. In UTF-8 text, the result is: > > This is ’within single quotes’. This is “within double quotes”. > > In LaTeX, the result is: > > This is 'within single quotes'. This is ``within double quotes''. > > Thanks in advance for any advice, The smart quotes algorithm changed. Now "..." are always level 1 quotes, and '...' and always level 2. IOW, '...' are not treated as smart quotes if they are not located within "...". Note that for a given language, "..." can still be treated as single quotes and '...' as double quotes. Regards, -- Nicolas Goaziou
Re: [O] bug: latex exporter
On 2015-10-02, at 12:31, Eric S Fraga wrote: > But, as this is the org mailing list, to keep it on topic, adventure was > definitely "all text"! ;-) Now you made me want to write a text-adventure game engine on top of Org-mode... I'm afraid that you have just ruined a few weeks of my life... ;-) Best, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz University
Re: [O] bug: latex exporter
On Friday, 2 Oct 2015 at 10:42, Marcin Borkowski wrote: > On 2015-10-02, at 09:32, Eric S Fraga wrote: > >> On Thursday, 1 Oct 2015 at 15:07, Rainer M Krug wrote: >>> This is indeed a twisted and strange thread... >> >> "You are in a maze of twisty little passages, all alike." >> >> For the old-timers out there... :-) > > And now you made me feel old... > > (I know the phrase only from history books, not first-hand. And from > dunnet.el, of course.) Then you're not old! :-) I know it from first hand experience, playing adventure on an Amdahl 470 using a DECwriter (paper, not CRT) terminal, back in the prehistory of computing! But, as this is the org mailing list, to keep it on topic, adventure was definitely "all text"! ;-) -- : Eric S Fraga (0xFFFCF67D), Emacs 24.5.1, Org release_8.3beta-1229-ge900eb
[O] Export datetree item subtree with its date, not the file's
Hi, This is my first post to this group, so I'm sorry if I'm skipping any conventions. And sorry for the dense subject line, I didn't want it to be too long. Thanks a lot for the hard work on org-mode. I have started recently to organise my lecture notes into a datetree. Every now and then I have to export my notes, usually to pdfs, in order to share them with friends, or study/read myself in printed form. Now, when I export to pdf an item, the "\maketitle" header contains the date from the file's "#+DATE:" thing[1]. I'd like it to contain the date for the current item, i.e. if it is under the "*** 2015-09-16 Wednesday" heading, the pdf to have "16 Sep 2015". Now I guess that I can do some temporary-buffer hack to make this happen, but I wonder if there already exist a /normal/ way to achieve this. My overall structure is like this: # $Id: Italianistica.org,v 1.5 2015/09/30 18:08:27 gk Exp gk $ #+TITLE: Appunti di Italianistica #+STARTUP: contents #+OPTIONS: toc:nil tags:nil #+LaTeX_CLASS: gk-appunto #+DATE: * 2015 ** 2015-09 September *** 2015-09-16 Wednesday İtalyanca Dil Uygulamaları I :2015_2016:ITDE2016: [2015-09-16 Wed] amare \ne voler bene _amare_ si usa quasi sempre _all'interno di una coppia_ _voler bene_ si usa tra _amici, parenti, ecc._ When I export-subtree the bottommost entry, I want the date in the exported pdf to be 2015-09-16, not today, nor the date in "#+DATE:", which is deliberately empty to not let a wrong date to appear in the exported file. I tried setting a date property which didn't have an effect, and also adding a "#+DATE: [a date...]" under every lecture note entry heading, in which case the date of the last entry in the file got used, so if I exported the notes from 2015-09-16, and the last time I added a note was the 19th, the exported file had the date 2015-09-19. So how can I, if I can at all, achieve what I want without tucking the tree into a temp buffer, adding the correct #+DATE into it, copying the org header and exporting? Is there a standard way to achieve this? Thanks in advance, -goktug [1] Property? I don't really know what these are called.
[O] [Babel] Headers: variable in output file name?
Hi, I have #+NAME: myplot #+HEADER: :var type="A" #+HEADER: :results output graphics #+HEADER: :file test.pdf :exports both #+BEGIN_SRC R #+END_SRC and call #+CALL: myplot(type="A") #+CALL: myplot(type="B") but instead of getting 'test.pdf' in both cases, I would like to have the type in the name of the output files, say, A.pdf B.pdf Is there anyway to achieve this? (I can in fact add the variable to the name of the output file within the source block, but I wondered whether it is possible via the Babel headers.) Cheers, Loris -- This signature is currently under construction.
Re: [O] bug: latex exporter
On 2015-10-02, at 09:32, Eric S Fraga wrote: > On Thursday, 1 Oct 2015 at 15:07, Rainer M Krug wrote: >> This is indeed a twisted and strange thread... > > "You are in a maze of twisty little passages, all alike." > > For the old-timers out there... :-) And now you made me feel old... (I know the phrase only from history books, not first-hand. And from dunnet.el, of course.) Best, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz University
Re: [O] Different set of packages for LaTeX export
Hi Fabrice, Hope you are well. Last time I saw you was in Pont-à-Mousson in 2005. On Fri, 2 Oct 2015 06:50:03 +0200 Fabrice Popineau wrote: > 2015-10-02 5:30 GMT+02:00 Manfred Lotz : > > > On Thu, 01 Oct 2015 21:21:42 +0200 > > Rasmus wrote: > > > > > Hi Manfred, > > > > > > Manfred Lotz writes: > > > > > > > When creating slides, i.e using beamer I get an option clash > > > > during compiling the tex file because beamer did already load > > > > hyperref. > > > > > > > > How can I solve it? > > > > > > > > Could I have a different package list if the class is beamer? > > > > > > No you can only discriminate based on the compiler version (and > > > actually only in ox-latex, not ox-beamer). > > > > > > > Hm, I think it would be great if a package list could be mapped to a > > certain LaTeX class. > > > > > To solve this, I set up my own LaTeX class. I find it at least as > good as to rely > on Org configuration. Actually, I removed the list of packages that > Org is exporting. > My LaTeX class can produce slides, course notes, exams and so on. > Based on options, I can chose which kind of document and a few things > like the style (font, etc.). > You are right, of course. Using my own class I have the full control to do what I like. Thanks for the idea. -- Manfred
[O] Bug: Exporting smart single quotes in Org 8.3 seems broken [8.3.2 (8.3.2-elpa @ /Users/jonathan/.emacs.d/elpa/org-20150929/)]
Hello Org folks,
(This is a duplicate of a Stackexchange question posted at
http://emacs.stackexchange.com/questions/17061/is-exporting-of-smart-single-quotes-broken-in-org-8-3)
I cannot seem get single quotes to export as 'smart' quotes under Org
8.3.2. Here is a minimal file that reproduces the problem:
#+OPTIONS: ':t
#+LANGUAGE: en
This is 'within single quotes'. This is "within double quotes".
Expected behavior: from "emacs -Q", under which "M-x org-version"
reports 8.2.10, the output when exporting to UTF-8 plaintext is:
This is ‘within single quotes’. This is “within double quotes”
and the output when exporting to LaTeX is:
This is `within single quotes'. This is ``within double quotes''.
If I load the most recent version of org-mode (starting from "emacs -Q",
typing "M-x package-initialize RET", and "M-x load-library RET org
RET"), "org-version" reports 8.3.2, and the output no longer correctly
translates single quotes. In UTF-8 text, the result is:
This is ’within single quotes’. This is “within double quotes”.
In LaTeX, the result is:
This is 'within single quotes'. This is ``within double quotes''.
Thanks in advance for any advice,
Jonathan
Emacs : GNU Emacs 24.4.1 (i686-apple-darwin, NS apple-appkit-1038.36)
of 2014-10-20 on builder10-6.porkrind.org
Package: Org-mode version 8.3.2 (8.3.2-elpa @ /Users/jonathan/.emacs.d/elpa=
/org-20150929/)
current state:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
(setq
org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point
org-babel-execute-safely-maybe)
org-plantuml-jar-path "~/bin/plantuml.jar"
org-ditaa-jar-path "/opt/local/share/java/ditaa0_9.jar"
org-tab-first-hook '(org-hide-block-toggle-maybe
org-babel-hide-result-toggle-maybe
org-babel-header-arg-expand)
org-archive-hook '(org-attach-archive-delete-maybe)
org-modules '(org-bbdb org-bibtex org-docview org-gnus org-info org-jsinfo
org-irc org-mew org-mhe org-rmail org-special-blocks org-vm
org-wl org-w3m)
org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
org-cycle-show-empty-lines
org-optimize-window-after-visibility-change)
org-clocktable-defaults '(:maxlevel 2 :lang "en" :scope file :block thismo=
nth
:wstart 1 :mstart 1 :tstart nil :tend nil :step
week :stepskip0 nil :fileskip0 nil :tags nil
:emphasize nil :link nil :narrow 40! :indent t
:formula nil :timestamp nil :level nil :tcolumns
nil :formatter nil)
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-confirm-babel-evaluate nil
org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
org-babel-pre-tangle-hook '(save-buffer)
org-occur-hook '(org-first-headline-recenter)
org-latex-default-packages-alist '(("AUTO" "inputenc" t) ("T1" "fontenc" t)
("" "fixltx2e" nil) ("" "graphicx" t)
("" "longtable" nil) ("" "float" nil)
("" "wrapfig" nil) ("" "rotating" nil)
("normalem" "ulem" t) ("" "amsmath" t)
("" "textcomp" t) ("" "marvosym" t)
("" "wasysym" t) ("" "amssymb" t)
("" "hyperref" nil) ("" "oddie" t)
"\\tolerance=3D1000")
org-structure-template-alist '(("s" "#+BEGIN_SRC ?\n\n#+END_SRC"
"\n\n")
("e" "#+BEGIN_EXAMPLE\n?\n#+END_EXAMPLE"
"\n?\n")
("q" "#+BEGIN_QUOTE\n?\n#+END_QUOTE"
"\n?\n")
("v" "#+BEGIN_VERSE\n?\n#+END_VERSE"
"\n?\n")
("V" "#+BEGIN_VERBATIM\n?\n#+END_VERBATIM"
"\n?\n")
("c" "#+BEGIN_CENTER\n?\n#+END_CENTER"
"\n?\n")
("l" "#+BEGIN_LaTeX\n?\n#+END_LaTeX"
"\n?\n")
("L" "#+LaTeX: "
"?")
("h" "#+BEGIN_HTML\n?\n#+END_HTML"
"\n?\n=
")
("H" "#+HTML: "
"?")
("a" "#+BEGIN_ASCII\n?\n#+END_ASCII")
("A" "#+ASCII: ")
("i" "#+INDEX: ?" "#+INDEX: ?")
("I" "#+INCLUDE: %file ?"
"")
Re: [O] bug: latex exporter
On Thursday, 1 Oct 2015 at 15:07, Rainer M Krug wrote: > This is indeed a twisted and strange thread... "You are in a maze of twisty little passages, all alike." For the old-timers out there... :-) -- : Eric S Fraga (0xFFFCF67D), Emacs 24.5.1, Org release_8.3.1-203-g4ca3d3
Re: [O] org export outcomes differ from one attempt to the next
On Thursday, 1 Oct 2015 at 22:02, Nicolas Goaziou wrote: > It doesn't ring a bell. Wild guess: what if you set > `org-element-use-cache' to nil prior to export? Ah ha! If I set this to nil, the exported file looks good! And it is the same the first time as well as the second time which is definitely a change in behaviour from before. And this is with my settings all at the end of the file. Thanks, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 24.5.1, Org release_8.3.1-203-g4ca3d3
