Re: [O] Exporting Agenda
On 21 December 2013 09:58, Bastien wrote: > Hi Johann, > > Johann Spies writes: > > > On 19/12/2013 22:45, Nicolas Goaziou wrote: > >> You may need to tweak `org-icalendar-use-scheduled' (for VEVENT) and > >> `org-icalendar-include-todo' (for VTODO). > > > > Thanks. > > > > I have search a little bit on how to do this and found something that > > works for me. > > If the solution is generic enough, maybe it's worth sharing it on the > list? > > It was this message that helped me to get mine working(You also took part in that thread): https://lists.gnu.org/archive/html/emacs-orgmode/2009-07/msg00839.html Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3)
Re: [O] #+TEXT: disappeared
Hi Bastien, On Mon, 23 Dec 2013 00:05:39 +0100 Bastien wrote: > Hi Manfred, > > Manfred Lotz writes: > > > Yes, this works. I simply didn't know about #+BEGIN_ABSTACT aso. > > I guess this is a quite common need for the LaTeX exporter, > so I explicitely used #+BEGIN_ABSTACT as an example of special > block in the manual. > > This will be in the next release. > Yes, it is good to have #+BEGIN_ABSTACT available. I discovered that even a #+BEGIN_BLABLA would work if I only would export to LaTeX (if there is an environment blabla is LaTeX). Other exporters wouldn't know blabla, of course. -- Manfred
Re: [O] Beamer title is (incorrectly?) outside of a frame
On Sunday, December 22, 2013 9:36:34 PM HKT, Nicolas Goaziou wrote:
Oh, I think I see the issue... there's only one org-latex-title-command.
;; 10. Title command.
(org-element-normalize-string
(cond ((string= "" title) nil)
((not (stringp org-latex-title-command)) nil)
...
I don't think the variable is problematic as you can wrap a frame around
it. Anyway, patch welcome.
Sure, I can work on a patch. I'll need this in another month or so.
One question, though: How would I determine the LaTeX document class
programmatically?
"Beamerarticle" uses the article class, with \usepackage{beamerarticle} in
the preamble. This package redefines beamer commands so that they print
somewhat reasonably well in article format. So, org needs to generate
beamer-style commands, and that's done by the beamer backend.
That is:
Exporting as presentation (normal)
- Backend = beamer
- Document class = beamer
Exporting as article
- Backend = beamer
- Document class = article
In the former case, the title command should be wrapped in a frame. In the
latter, it should not.
Currently, I'm working around it by #+bind'ing org-latex-title-command, but
I'd like that to be automatic.
hjh
Re: [O] re-export using same options
> > > > Can I re-export using the last settings? > > C-u C-c C-e Thanks, that makes it faster, but you need to be in the same subtree. Is there something that also remembers which subtree was exported?
Re: [O] Global TODO: display more than the TODO heading line?
Bastien writes: > Hi Zebee, > > Zebee Johnstone writes: > >> was afraid of that. I've experimented with using columns but it was >> too much faffing about to really bother with. > > Maybe you can use `org-after-todo-state-change-hook' to store a note > in a property, then display the content of this property in the column > view -- but this is a bit hackish anyway. I've wanted this too -- if we're logging into a drawer (ie LOGBOOK), shouldn't there be a relatively simple way of getting the drawer contents, and taking the top (or bottom) log entry? On the other hand, looking at `org-add-log-setup', maybe it wouldn't be all that easy, either. E
Re: [O] Colorizing 'emacs-lisp' when it is exported?
On Sun, 22 Dec 2013 23:49:04 + "Sean O'Halpin" wrote: > On Sun, Dec 22, 2013 at 4:03 PM, Sharon Kimble > wrote: > > Thanks to auntie google I've found out how to keep the formatting of > > elisp on export to html using '#+BEGIN_SRC emacs-lisp' at the > > beginning of the code block, and '#+END_SRC' at the end. Whilst its > > in .emacs its nicely colorized, but how do I colorize the output > > when its been exported please? For once, google has drawn a blank, > > unfortunately! > > > > Sharon. > > Have you set this? > > (setq org-src-fontify-natively t) No I haven't, but I have now. I'll have a further play with it tomorrow I think. Thanks :) Sharon. -- A taste of linux = http://www.sharons.org.uk efever = http://www.efever.blogspot.com/ efever = http://sharon04.livejournal.com/ my git repo = https://bitbucket.org/boudiccas/dots Debian testing, Fluxbox 1.3.5, LibreOffice 4.1.3.2 Registered Linux user 561944 signature.asc Description: PGP signature
Re: [O] Colorizing 'emacs-lisp' when it is exported?
On Sun, Dec 22, 2013 at 4:03 PM, Sharon Kimble wrote: > Thanks to auntie google I've found out how to keep the formatting of > elisp on export to html using '#+BEGIN_SRC emacs-lisp' at the beginning > of the code block, and '#+END_SRC' at the end. Whilst its in .emacs its > nicely colorized, but how do I colorize the output when its been > exported please? For once, google has drawn a blank, unfortunately! > > Sharon. Have you set this? (setq org-src-fontify-natively t) Regards, Sean
Re: [O] Show Only Diary Entries in Agenda
Hi Kenneth, Kenneth Jacker writes: > I'd like to toggle (hide/show) the *non*-diary entries in the agenda > view ... to basically get a quick view of my diary/calender. > > 'org-agenda-toggle-diary', toggles the Diary entries. Maybe something > like 'org-agenda-toggle-nondiary'? > > I tried to configure a custom agenda view, but failed ... I'm not sure > that's the way to go anyway ... Maybe you can use a custom agenda that skips all entries by using `org-agenda-skip-regexp' and includes the Diary? Sounds weird but might actually work (not tested.) -- Bastien
Re: [O] Yet another Jekyll Org mode setup
Hi Waldemar, Waldemar Quevedo writes: > This is just to share my setup for using Jekyll and Org mode in case > someone finds it useful... > https://github.com/wallyqs/yet-another-jekyll-org-template As a user of github pages, yes, I can imagine how useful this is! Thanks for sharing it, -- Bastien
Re: [O] Makefile: switch to a specific Git branch before update
Achim Gratz writes: > In a number of recent discussions it transpired that some people expect > to automatically be switched to a specific Git branch when updating. > > I've added this as an option to the standard Makefile. Thanks! -- Bastien
Re: [O] [PATCH] updated patch to org-habit DONE keywords
Hi Ted, Ted Wiles writes: > Take care of all DONE keywords, not just the last one. > > * lisp/org-habit.el > > This fixed a hard-coded TODO keyword > in the org-habit code. Updated to apply to all DONE keywords, as per > Aaron Ecay > > TINYCHANGE Applied, with a tiny rewrite of the commit message. Thanks! -- Bastien
Re: [O] #+TEXT: disappeared
Hi Manfred, Manfred Lotz writes: > Yes, this works. I simply didn't know about #+BEGIN_ABSTACT aso. I guess this is a quite common need for the LaTeX exporter, so I explicitely used #+BEGIN_ABSTACT as an example of special block in the manual. This will be in the next release. -- Bastien
Re: [O] Force blank line above level 1 heading
Sebastian Fischmeister writes: > Yes, but this inserts a blank line before every entry. I would like to > have a blank line only before level 1 headings. Ah, then clearly this option is not enough. Sorry, I'm short of ideas here. -- Bastien
Re: [O] #+TEXT: disappeared
On Thu, 19 Dec 2013 21:42:47 +0100 Nicolas Goaziou wrote: > Hello, > > Manfred Lotz writes: > > > Actually I want to have an abstract between title/author and the > > first chapter. > > Isn't the following sufficient? > > #+title: My title > #+author: Me > > #+begin_abstract > ... > #+end_abstract > > * First section > > Contents > > Yes, this works. I simply didn't know about #+BEGIN_ABSTACT aso. -- Thanks, Manfred
[O] possible org-refile bug fix
Dear maintainers, I may have found a bug relate to org-refile function,though I have not push privileges,I submit a patch using git format-patch. Wait for your review, awesome Org mode!! From 866b7be3536d92eb7d7b04cdd48a8b806b9b7253 Mon Sep 17 00:00:00 2001 From: Vacker Date: Sun, 22 Dec 2013 16:33:28 +0800 Subject: [PATCH] check refile position when the position is not nil # background when use ido-mode to refile,type a unexist heading always trigger error 'Please indicate a target file in the refile path' even after set org-refile-allow-creating-parent-nodes to 'confirm or 'file. # debugging result see the code comments --- lisp/org.el | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/lisp/org.el b/lisp/org.el index 1f20bfd..84f2a60 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -11801,12 +11801,16 @@ this is used for the GOTO interface." (concat " (default " cbnex ")"))) ": ")) pa answ parent-target child parent old-hist) (setq old-hist org-refile-history) +;;answ will be the new (not exist) heading you type through org-icompleting-read (setq answ (funcall cfunc prompt tbl nil (not new-nodes) nil 'org-refile-history (or cdef (car org-refile-history +;;but tbl is fixed not containing the new heading, +;;so pa is always nil +;;we could let org-refile-check-position work when pa is not nil (setq pa (or (assoc answ tbl) (assoc (concat answ "/") tbl))) -(org-refile-check-position pa) (if pa (progn + (org-refile-check-position pa) (when (or (not org-refile-history) (not (eq old-hist org-refile-history)) (not (equal (car pa) (car org-refile-history -- 1.8.5.2
Re: [O] re-export using same options
Daniel Clemente gmail.com> writes: > > > Hi, after exporting a subtree to HTML, I do some change and want to export again. I find that I have to do a long > process to get there: > C-spaceC-c C-u C-c C-e C-s h HC-u space > [snip] > > Can I re-export using the last settings? [snip] C-u C-c C-e See the manual (org) The export dispatcher
[O] re-export using same options
Hi, after exporting a subtree to HTML, I do some change and want to export again. I find that I have to do a long process to get there: C-spaceC-c C-u C-c C-e C-s h HC-u space This works, but for every little change I do I have to select again which subtree and which format I want. Can I re-export using the last settings? If there's a function for that that can be invoked with M-x, then only M-x up RET will be needed for successive reexports. Thanks
Re: [O] [PATCH] Table continuation strings
Hi Nicolas, At Sun, 22 Dec 2013 09:20:57 +0100, Nicolas Goaziou wrote: > > Yasushi SHOJI writes: > > > Ah, OK. Those coding keys are for the back-ends to select proper > > strings, not for the string encoding. > > This is also related to string encoding. You will get garbage if you > insert a string containing characters outside the encoding you use to > save the file, won't you? Right. However, as you described below, the output file's encoding is not determined by the language option, but by the current buffer coding system, org-export-coding-system, or back-end specific variable, ie org-html-coding-system. That means that whenever your-choice-of-coding-system can handle the "characters" for the translation string, meaning that the coding system has code points for all of the characters of the translation string and Emacs can convert between them, it is free to use any character for the output, right? If one wants to use French, she sets the current buffer coding system to any coding system which can handle French and set the language option as "fr". In that case, her/his org buffer should already have French characters in it, there is no need for translation string to be strictly ASCII only when you export with plain / ascii, no? I just don't see any use case. I must have missed something here. Please enlighten me. BTW, Here is a part of quick test I've done. source lang exporter o-e-c-s o-h-c-s target buffer target file --- euc-jp japlain/ascii nil -euc-jp euc-jp euc-jp japlain/utf-8 nil -euc-jp euc-jp euc-jp japlain/ascii utf-8-euc-jp utf-8 euc-jp japlain/utf-8 utf-8-euc-jp utf-8 euc-jp jahtml nil utf-8euc-jp w/ charset=utf-8 utf-8 euc-jp jahtml nil euc-jp euc-jp w/ charset=euc-jp euc-jp w/ charset=euc-jp --- euc-jp frplain/ascii nil -euc-jp w/ fr trans euc-jp w/ fr translation euc-jp frplain/utf-8 nil -euc-jp w/ fr trans & utf-8 decoration euc-jp w/ fr trans & utf-8 decoration All major encoding for Japanese, euc-jp, iso2022, shift-jis, and utf-8 can handle the current translation string without problem. So I'm assuming that encoding for other language must have some problem. > > Then, is there any restriction with HTML back-ends? Why does it need > > numeric character reference instead of just plain characters, if the > > coding system is not a concern? > > See above. You may want to save your html file in a different encoding > than UTF-8. IIUC, numeric character reference are more generic. I agree that numeric reference is more generic. As I've just checked, HTML even allows us to put characters outside of the current content charset with numeric reference! # italian text exported as html with "ja" language option. even if # html has iso-8859-1 as charset, web browser shows japanese chars. > > If my understanding is ok, all entries of Japanese translation should > > have :default instead of :utf-8. > > :default instead of :utf-8 means Org will use these translations also > for LaTeX, HTML and ASCII export. If you think that is correct, then we > can switch to :default, indeed. Since I don't use LaTeX, I have no idea about it. I hope some LaTeX user help me here. I'm checking exporters I use, including plain text and html, but it doesn't seems to go wrong. But I really needs some help for other back-ends. I'll post a patch for testing if anyone's interested in. Thanks, -- yashi
[O] Colorizing 'emacs-lisp' when it is exported?
Thanks to auntie google I've found out how to keep the formatting of elisp on export to html using '#+BEGIN_SRC emacs-lisp' at the beginning of the code block, and '#+END_SRC' at the end. Whilst its in .emacs its nicely colorized, but how do I colorize the output when its been exported please? For once, google has drawn a blank, unfortunately! Sharon. -- A taste of linux = http://www.sharons.org.uk efever = http://www.efever.blogspot.com/ efever = http://sharon04.livejournal.com/ my git repo = https://bitbucket.org/boudiccas/dots Debian testing, Fluxbox 1.3.5, LibreOffice 4.1.3.2 Registered Linux user 561944 signature.asc Description: PGP signature
Re: [O] date next year
Samuel Wales gmail.com> writes:
>
> +1y?
>
> On 12/20/13, Rene yahoo.com> wrote:
> > How can I set org-agenda-custom-commands so that I can get the tasks past a
> > date in the coming year?
> >
> > Suppose I'm interested in things past next september. This
> >
> > ("y"
> > "Next year's appointments"
> > tags "TIMESTAMP>=\"<2014-09-01>\"")
Actually, I want the "y" custom command to get me the tasks scheduled past a
coming date. How to define a date like "the next september 1st"?
Is it possible to do so?
Re: [O] Force blank line above level 1 heading
>> Is there a way to always force a blank line above a level 1 >> heading. When I enter them manually, orgmode somethings things it >> belongs to the level 2 (or so) item above it and hides it. > > Check `org-blank-before-new-entry'. Yes, but this inserts a blank line before every entry. I would like to have a blank line only before level 1 headings. Sebastian
[O] Loss of formatting when code is exported.
When using 'org2blog' to post to my wordpress blog, I can have the code for e.g., .emacs showing nicely formatted in emacs24, but when it is uploaded it converts itself all to one long continuous line! How can I keep the Emacs formatting please when it is exported? Sharon. -- A taste of linux = http://www.sharons.org.uk efever = http://www.efever.blogspot.com/ efever = http://sharon04.livejournal.com/ my git repo = https://bitbucket.org/boudiccas/dots Debian testing, Fluxbox 1.3.5, LibreOffice 4.1.3.2 Registered Linux user 561944 signature.asc Description: PGP signature
Re: [O] [PATCH] Re: \newpage in HTML export
Nicolas Goaziou writes: > Hello, > > Andreas Leha writes: > >> Just for me to understand: >> The recommended way now > > Note that the recommended way hasn't really changed. There was no > recommended way before, nor there is one now. > ;-) >> is to have a filter and write (say) \mypersonalnewline in my orgmode >> files? Even if \mypersonalnewline won't work for anyone except myself? >> Or did I miss something? > > You can write ^L in your files, as long as you transform it into > something useful, through a filter. > I am not interested in ^L in particular. I am interested in a pagebreak, that works across backends. My filter will not use '^L' but rather '\newpage'. > It will work for anyone with whom you share your Org configuration, or, > at least, anyone using an equivalent filter. Ok. So be it. Regards, Andreas
Re: [O] [PATCH] Re: \newpage in HTML export
Hello, Andreas Leha writes: > Just for me to understand: > The recommended way now Note that the recommended way hasn't really changed. There was no recommended way before, nor there is one now. > is to have a filter and write (say) \mypersonalnewline in my orgmode > files? Even if \mypersonalnewline won't work for anyone except myself? > Or did I miss something? You can write ^L in your files, as long as you transform it into something useful, through a filter. It will work for anyone with whom you share your Org configuration, or, at least, anyone using an equivalent filter. Regards, -- Nicolas Goaziou
Re: [O] [PATCH] Re: \newpage in HTML export
Hi Nicolas, Nicolas Goaziou writes: > Hello, > > Andreas Leha writes: > >> So in short: If page breaks are not in org directly many people will >> end up with inferior and/or less portable org files. > > For the record, after thinking about it, I'd rather stay away from > invisible characters in Org syntax, would it be page breaks or > non-breaking spaces. I agree about the invisible characters. > > Porting an Org file requires to also to port Org configuration. A filter > is enough to support these characters. Added support would just be, IMO, > "coolishness". Just for me to understand: The recommended way now is to have a filter and write (say) \mypersonalnewline in my orgmode files? Even if \mypersonalnewline won't work for anyone except myself? Or did I miss something? Regards, Andreas
Re: [O] [PATCH] Re: \newpage in HTML export
Hello, Andreas Leha writes: > So in short: If page breaks are not in org directly many people will > end up with inferior and/or less portable org files. For the record, after thinking about it, I'd rather stay away from invisible characters in Org syntax, would it be page breaks or non-breaking spaces. Porting an Org file requires to also to port Org configuration. A filter is enough to support these characters. Added support would just be, IMO, "coolishness". Regards, -- Nicolas Goaziou
Re: [O] Beamer title is (incorrectly?) outside of a frame
Hello,
James Harkins writes:
>> The beamer user guide (I.3.4) specifies the following:
>>
>> \begin{frame}
>> \titlepage
>> \end{frame}
>>
>> But org-mode simply writes "\maketitle" outside of a frame.
>
> Oh, I think I see the issue... there's only one org-latex-title-command.
>
> ;; 10. Title command.
> (org-element-normalize-string
> (cond ((string= "" title) nil)
> ((not (stringp org-latex-title-command)) nil)
> ((string-match "\\(?:[^%]\\|^\\)%s"
> org-latex-title-command)
>(format org-latex-title-command title))
> (t org-latex-title-command)))
>
> An isolated \maketitle is ok for articles, but not for Beamer. So
> I suppose it's incorrect to press the same variable into service for
> both.
I don't think the variable is problematic as you can wrap a frame around
it. Anyway, patch welcome.
Regards,
--
Nicolas Goaziou
Re: [O] Global TODO: display more than the TODO heading line?
Hi Zebee, Zebee Johnstone writes: > was afraid of that. I've experimented with using columns but it was > too much faffing about to really bother with. Maybe you can use `org-after-todo-state-change-hook' to store a note in a property, then display the content of this property in the column view -- but this is a bit hackish anyway. -- Bastien
Re: [O] Beamer title is (incorrectly?) outside of a frame
On Sunday, December 22, 2013 6:38:02 PM HKT, James Harkins wrote:
Hi,
Is there a reason why Beamer export does not place "\maketitle" in a
frame?
The beamer user guide (I.3.4) specifies the following:
\begin{frame}
\titlepage
\end{frame}
But org-mode simply writes "\maketitle" outside of a frame.
Oh, I think I see the issue... there's only one org-latex-title-command.
;; 10. Title command.
(org-element-normalize-string
(cond ((string= "" title) nil)
((not (stringp org-latex-title-command)) nil)
((string-match "\\(?:[^%]\\|^\\)%s"
org-latex-title-command)
(format org-latex-title-command title))
(t org-latex-title-command)))
An isolated \maketitle is ok for articles, but not for Beamer. So I suppose
it's incorrect to press the same variable into service for both.
hjh
[O] Beamer title is (incorrectly?) outside of a frame
Hi,
Is there a reason why Beamer export does not place "\maketitle" in a frame?
The beamer user guide (I.3.4) specifies the following:
\begin{frame}
\titlepage
\end{frame}
But org-mode simply writes "\maketitle" outside of a frame.
This is important when you are using the same source to produce both a
beamer presentation and a beamerarticle print version. For the
presentation, you should use the ignorenonframetext class option, which
omits everything that is not between \begin{frame} and \end{frame}. Since
org doesn't write a frame for the title, then the title disappears.
Bug? I suspect so, as Beamer export is not following the format described
in the beamer manual.
See also
http://tex.stackexchange.com/questions/80277/beamer-with-ignorenonframetext-ignores-maketitle-command-too-why
hjh
Re: [O] tricky odt export needs
Jambunathan K writes: > When we are typesetting a xref in a backend - I can authoritatively > speak for the ODT backend - we need not be resticted to "ONE-OF" but can > have "ANY-COMBINATION-OF" descriptors. What I mean is this: > > In the pdf version of Emacs info manuals one typically sees all three of > a Section number AND a Description AND a Page number, something like: > > See Section 3.1 [Tropical Storms], page 24. > > In Org context, I am wondering whether there is such a need. Two thoughts: 1. Assuming my suggestion for dedicated links to be typeset as page number references, one partly achieve this by multiple links. e.g. See Section [[*Tropical Storms]], page [[tropstorms]]. * Tropical Storms Bla bla bla... <> Bla bla bla.. -- 2. Maybe, instead of trying to make simple cross-reference links do everything for everyone, it would be better to think in terms of creating several link types? e.g. something like See Section [[*Tropical Storms]], [[textref:*Tropical Storms]], [[pageref:tropstorms]]. Yours, Christian Moe
Re: [O] Global TODO: display more than the TODO heading line?
On Sun, Dec 22, 2013 at 7:54 PM, Bastien wrote: > Hi Zebee, > > sadly no, this is not currently possible. The notes attached to a > TODO state change are not really stored in a structure way, so it's > not possible to retrieve this information and to display it. Bastien, was afraid of that. I've experimented with using columns but it was too much faffing about to really bother with. Zebee
Re: [O] Get the maximum date within a list of dates
Thanks Bastien, it's what I am expecting :) > From: b...@gnu.org > To: truonghat...@outlook.com > CC: emacs-orgmode@gnu.org > Subject: Re: Get the maximum date within a list of dates > Date: Sun, 22 Dec 2013 08:27:08 +0100 > > Bastien writes: > > > Put your cursor in @2$2 then C-c ^ T to sort by "reversed" date > > (oldest last). > > Also remember you can use ELisp in formulas: > > | Date 1 | Date 2 | Duration | > |-+-+--| > | [2013-12-21 sam. 00:00] | [2013-12-22 dim. 00:00] | 86400.0 | > #+TBLFM: $3='(- (org-time-string-to-seconds "$2") (org-time-string-to-seconds > "$1"));L > > PS: note the quotes around "$2" and "$1", they are necessary so > that the date is not literally inserted in the formulas when Org > is computing it. > > HTH, > > -- > Bastien
Re: [O] Not all table formulas are updated when swapping columns
Hi Daniel, Daniel Gerber writes: > A minor bug with spreadsheets: when swapping two columns in a table > (alt+left), column formulas are updated only when defined in the first > #+TBLFM: line. this is now fixed in the git repository, thanks for reporting this bug. Best, -- Bastien
Re: [O] Global TODO: display more than the TODO heading line?
Hi Zebee, sadly no, this is not currently possible. The notes attached to a TODO state change are not really stored in a structure way, so it's not possible to retrieve this information and to display it. Sorry, -- Bastien
Re: [O] Missing patch from Eric Schulte from 2013-10-09
Hi Francesco, "Francesco Pizzolante" writes: > I noticed that I miss the following patch from Eric Schulte (from 2 > months ago): > http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=15847336c39e7219e1c51c55d487f99956a06e34 > > I have Org-mode version 8.2.4 (8.2.4-8-gf1b933-elpaplus @ > c:/Users/fpz/Documents/home/.emacs.d/elpa/org-plus-contrib-20131216/) > taken from elpa. > > When I download the current stable release of Org-mode (version 8.2.4 > from http://orgmode.org/) I see that this patch is missing too (the > org-babel-tangle-use-relative-file-links variable is missing). > > Any chance to get this patch in elpa (without having to clone the git > master branch)? The patch is in the master branch only, your best move is to clone org-mode and follow that branch -- or wait until we make another major release. Thanks, -- Bastien
Re: [O] Missing contrib packages
Hi Francesco, "Francesco Pizzolante" writes: > I have Org-mode version 8.2.4 (8.2.4-8-gf1b933-elpaplus @ > c:/Users/fpz/Documents/home/.emacs.d/elpa/org-plus-contrib-20131216/). > > I notice that I miss several packages like htmlize (important) and > org-effectiveness. > > My questions are: > > - why, in the org-plus-contrib from elpa, I miss these packages (present > in the master branch)? org-plus-contrib is created from maint. org-effectiveness.el is only in master so far. htmlize.el was not included so far when packaging the org-plus-contrib ELPA package, I fixed this, thanks. > - why, in the release version 8.2.4 downloaded from http://orgmode.org/, > I have htmlize but not org-effectiveness? Because it is packaged from maint. All releases are packaged from the maint branch, not the master branch. Hope this clarifies, -- Bastien
Re: [O] [PATCH] Table continuation strings
Hello, Yasushi SHOJI writes: > Ah, OK. Those coding keys are for the back-ends to select proper > strings, not for the string encoding. This is also related to string encoding. You will get garbage if you insert a string containing characters outside the encoding you use to save the file, won't you? > Then, is there any restriction with HTML back-ends? Why does it need > numeric character reference instead of just plain characters, if the > coding system is not a concern? See above. You may want to save your html file in a different encoding than UTF-8. IIUC, numeric character reference are more generic. > Correct me if I'm wrong. My understainding is as follows: All > translation strings is in `emacs-internal' coding system, since it is > defined in .el. A org file ready to be exported has a coding system > specific to the buffer, ie. utf-8, iso-latin-1, euc-jp, etc. Correct. > Org export back-ends get a strings for the back-ends from the > translation table when appropriate. At that time Emacs converts the > strings encoding system to match the buffer encoding system (or does > Emacs convert all encoding when it writes to file?). The latter. The output in concatenated into a single string, which is then inserted in the target buffer (and saved to a file, if needed). > Back-ends uses `org-export-coding-system' if set, otherwise use the > current buffer coding system. Some back-ends also use their own variable (e.g. `org-html-coding-system'). > If my understanding is ok, all entries of Japanese translation should > have :default instead of :utf-8. :default instead of :utf-8 means Org will use these translations also for LaTeX, HTML and ASCII export. If you think that is correct, then we can switch to :default, indeed. Regards, -- Nicolas Goaziou
Re: [O] Org-mac-link misplaced quotes?
Hi Alexander, Alexander Poslavsky writes: > I regularly use org-mac-link from contrib/. It works fine, but > somehow my links are a bit mangled, I get: > > [["http://orgmode.org/worg/org-contribute.html#sec-4][How to > contribute to Org?"]] > > Instead of: > > [[http://orgmode.org/worg/org-contribute.html#sec-4][How to > contribute to Org?]] > > (Notice the quotation-marks, it's how applescript returns the string) > > This small patch fixes that. I hope the patch is done correctly. Applied, thanks. I slightly edited your commit message, please check the changes: http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=22af33 -- Bastien
Re: [O] Force blank line above level 1 heading
Hi Sebastian, Sebastian Fischmeister writes: > Is there a way to always force a blank line above a level 1 > heading. When I enter them manually, orgmode somethings things it > belongs to the level 2 (or so) item above it and hides it. Check `org-blank-before-new-entry'. HTH, -- Bastien
