Re: [O] Export a Subtree to an other .org file
Hi Nicolas, For the org-org-export-to-org function, if the input is * test #+BEGIN_SRC R -n :var a=1 a #+END_SRC the output is * test #+BEGIN_SRC R -n a #+END_SRC That is, the :var a=1 header argument is stripped (but the -n switch is preserved). Is this intentional? I think /everything/ in the #+BEGIN_SRC line should be preserved. What do you think? Thanks! -- Best, Hsiu-Khuern.
Re: [O] Export a Subtree to an other .org file
* On Thu 03:13PM, 04 Apr 2013, Bastien (b...@altern.org) wrote: Nicolas Goaziou n.goaz...@gmail.com writes: What about the following? Looks gret! Feel free to apply it, -- Bastien Hi Nicolas and Bastien, I've updated to the latest git version and tested this. Works like a charm -- thank you! -- Best, Hsiu-Khuern.
Re: [O] Export a Subtree to an other .org file
* On Wed 03:35PM, 03 Apr 2013, John Hendy (jw.he...@gmail.com) wrote: On Wed, Apr 3, 2013 at 2:31 PM, Steve Prud'Homme sprud...@gmail.com wrote: Message : No command associated with key ^S Bastien's response was for the new exporter and your C-e 1 command indicates you're not using that version yet. I'm on the new exporter, so I can't recall what old options looked like, but from the manual could you try ASCII? - http://orgmode.org/manual/ASCII_002fLatin_002d1_002fUTF_002d8-export.html#ASCII_002fLatin_002d1_002fUTF_002d8-export Perhaps you could just export that to a buffer and then save as *.org instead of the default export format of .txt? I think the ascii export does not produce a file in Org format. The old exporter function org-export-as-org may do the trick for Steve. I too find it useful to export to org, and would love to see this implemented in the new exporter. I rely on this together with the SELECT_TAGS and EXCLUDE_TAGS keywords to create an Org file with a subset of the headings, not just a subtree. Is there a new exporter function that does this? -- Best, Hsiu-Khuern.
[O] (new exporter) itemized lists converted from deep headlines should not be numbered
Hi all, Under the new exporter, if I export this to ascii: -- #+TITLE: #+AUTHOR: #+OPTIONS: H:1 num:t toc:nil * First level ** Second level Something -- I get -- 1 First level = * 1.1 Second level Something -- I'd prefer * Second level without the 1.1 label, just like with the old exporter. Thanks! -- Best, Hsiu-Khuern.
[O] Bug in new exporter: source block messes up list hierarchy
Hi all, Under the new exporter, if I export this to ascii: -- #+TITLE: #+AUTHOR: #+OPTIONS: toc:nil * A 1. this 1. something #+begin_src r a - 1 #+end_src 2. other -- I get -- 1 A === 1. this 1. something , | a - 1 ` 1. other -- Org seems to think that the source block does not belong to the inner or outer list. Strangely enough, I don't get this problem in either of these cases: - if the source block is in the outer list - if I use an example block instead of a source block Thanks! -- Best, Hsiu-Khuern.
Re: [O] Bug in new exporter: source block messes up list hierarchy
Please ignore this, the problem does not occur using the latest git source. -- Best, Hsiu-Khuern.
Re: [O] (new exporter) itemized lists converted from deep headlines should not be numbered
* On Fri 11:22AM, 02 Nov 2012, Hsiu-Khuern Tang (tan...@gmail.com) wrote: I get -- 1 First level = * 1.1 Second level Something -- I'd prefer * Second level without the 1.1 label, just like with the old exporter. Using the latest git source, headlines deeper than the H: export setting is converted to an ordered list item, e.g., 1.1 Second level for the above example, and this is also fine with me. Sorry for the noise. -- Best, Hsiu-Khuern.
Re: [O] Bug: source code editing using C-c ' (org-edit-special) eats characters
Hi Bastien, * On Thu 10:53AM, 25 Oct 2012, Bastien (b...@altern.org) wrote: Hsiu-Khuern Tang tan...@gmail.com writes: Sorry if this has been reported -- a brief search didn't turn up anything. this is now fixed -- thanks for reporting this! Thanks for working on this. It's better than before, but there's still a problem, e.g., when I start with the three lines #+begin_example #+end_example and do C-c ' on the empty line, type test, and C-c ' again, I get #+begin_example test#+end_example If I type test + newline, I get #+begin_example test #+end_example BTW, is C-c ' on the #+begin_example or #+end_example lines supposed to work? If I start with the two lines #+begin_example #+end_example and do C-c ' on either line, type test (without a newline), and C-c ' again, I get #+begin_example test +end_example (The # of #+end_example gets dropped.) -- Best, Hsiu-Khuern.
[O] Bug: source code editing using C-c ' (org-edit-special) eats characters
Hi, Sorry if this has been reported -- a brief search didn't turn up anything. Start with this 3-line org file: -- #+begin_example #+end_example -- Do these steps: - go to the 2nd line - type C-c ' to edit the source example - type some text in the new buffer, such as test - type C-c ' to exit What I get is this: -- #+begin_example test#+end_example -- Anyone else able to reproduce this? -- Thanks, Hsiu-Khuern.
Re: [O] Bug: source code editing using C-c ' (org-edit-special) eats characters
* On Tue 04:31PM, 23 Oct 2012, Nick Dokos (nicholas.do...@hp.com) wrote: Hsiu-Khuern Tang tan...@gmail.com wrote: Hi, Sorry if this has been reported -- a brief search didn't turn up anything. Start with this 3-line org file: -- #+begin_example #+end_example -- Do these steps: - go to the 2nd line - type C-c ' to edit the source example - type some text in the new buffer, such as test - type C-c ' to exit What I get is this: -- #+begin_example test#+end_example -- Anyone else able to reproduce this? ... It depends on what you type exactly: typing test with no extra newlines produces the result above for me. If I add newlines, I get funny-looking results with the #+END_EXAMPLE indented some. Since it does not know a language, the buffer is in fundamental mode and you get (modulo funny indentation perhaps) whatever you type. Nick Thanks for checking. The problem also shows up if I replace begin_example by begin_src r (say), so it's not just because Org doesn't know the language. Also, if I start with -- #+begin_example #+end_example -- and repeat the above steps (but typing C-c ' on the /first/ line), the output becomes -- #+begin_exampl test +end_example -- Note that the last e of begin_example got dropped! -- Best, Hsiu-Khuern.
Re: [O] bug in selective export when selected heading follows excluded heading
Hi Eric, On Thu, May 31, 2012 at 11:10 PM, Eric S Fraga e.fr...@ucl.ac.uk wrote: Eric S Fraga e.fr...@ucl.ac.uk writes: Confirmed with up to date org. Thanks for confirming the bug. ... There is still a bug but whether sec2 should be output at all or not, given that chap1 has no tag, is unclear! Undefined situation basically. The Selective export section of the manual does say, If a selected tree is a subtree, the heading hierarchy above it will also be selected for export, but not the text below those headings. I find this behavior useful to avoid having too many tags. HTH, eric -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1 : using Org release_7.8.10-630-g4144c5.dirty - Hsiu-Khuern.
[O] Bug in selective export when selected heading follows excluded heading
(Adding the [O] tag to the subject line -- sorry for the re-post) Hi, Here's an input file, a.org: #+OPTIONS: toc:nil #+EXPORT_EXCLUDE_TAGS: exclude #+EXPORT_SELECT_TAGS: include * chap1 ** sec1:exclude: ** sec2:include: If I export this file, the heading gets mangled. E.g., the ascii export is: a = Author: Hsiu-Khuern Tang Date: 2012-05-26 00:31:10 PDT 1 chap1** sec2 :include: I'm using the latest Org. Thanks, - Hsiu-Khuern.
[O] bug in selective export when selected heading follows excluded heading
Hi, Here's an input file, a.org: #+OPTIONS: toc:nil #+EXPORT_EXCLUDE_TAGS: exclude #+EXPORT_SELECT_TAGS: include * chap1 ** sec1 :exclude: ** sec2 :include: If I export this file, the heading gets mangled. E.g., the ascii export is: a = Author: Hsiu-Khuern Tang Date: 2012-05-26 00:31:10 PDT 1 chap1** sec2 :include: I'm using the latest Org. Thanks, - Hsiu-Khuern.
Re: [O] Non-leading commas removed from src blocks
On Tue, Sep 6, 2011 at 9:00 PM, Eric Schulte schulte.e...@gmail.com wrote: Hsiu-Khuern Tang tan...@gmail.com writes: Hi Eric, I think your commit 20044297 caused non-leading commas to be removed from src blocks. Example: ... My original email about this is here: http://article.gmane.org/gmane.emacs.orgmode/44977. Hi Hsiu-Khuern, Thanks for pointing out this behavior. I've just pushed up a change to the git repository which should fix this behavior. Please let me know if the problem persists. Best -- Eric I tested the latest version and it now works as I would like it to -- thanks for the change! Best, Hsiu-Khuern.
[O] Non-leading commas removed from src blocks
Hi Eric, I think your commit 20044297 caused non-leading commas to be removed from src blocks. Example: = * test #+begin_src r a - c(1 , 2 , 3) #+end_src = But I could be misunderstanding what non-leading means. My original email about this is here: http://article.gmane.org/gmane.emacs.orgmode/44977. Thanks! Hsiu-Khuern.
Re: [O] org-open-at-point (C-c C-o) doesn't work anymore
Hi John and Achim, Thanks for your replies. I tried your suggestions, and here are the results: - Achim's suggestions: I normally install org-mode from a .deb that I create using a debian/rules file copied from the debian org-mode package, so I believe I'm using the correct org-install.elc file. I also tried uninstalling the deb package and installing org-mode under /usr/local via make install and got the same results. - John's suggestions: On Sat, Jul 30, 2011 at 2:23 PM, John Hendy jw.he...@gmail.com wrote: I experienced this as well, but with a different issue. See this thread of mine from today: --- http://www.mail-archive.com/emacs-orgmode@gnu.org/msg44887.html The following both (well, using either one) fixed my issue as well as the C-c C-o issue: 1) make clean 2) git reset --hard release_7.7 It looks like that commit might be an issue after all. Running git reset --hard release_7.7 does solve my C-c C-o problem -- this suggests to me that some patch since release_7.7 is responsible? I do see a patch -- commit 9ff7f80f51a15c -- that seems related, but I'm not familiar enough with elisp/git to diagnose this. - Hsiu-Khuern.
[O] org-open-at-point (C-c C-o) doesn't work anymore
Hi all, When I try C-c C-o to open a link in an Org buffer, e.g., http://www.google.com, I get: org-babel-open-src-block-result: Symbol's value as variable is void: org-babel-inline-src-block-regexp This is the backtrace: Debugger entered--Lisp error: (void-variable org-babel-inline-src-block-regexp) org-babel-get-src-block-info() org-babel-open-src-block-result(nil) call-interactively(org-babel-open-src-block-result t nil) execute-extended-command(nil) call-interactively(execute-extended-command nil nil) Trying to search for org-babel-inline-src-block-regexp in the source led me to this commit commit 6da29f151915fd86f40b51cbb999d3b2792aff0e Author: Eric Schulte schulte.e...@gmail.com Date: Wed Jun 23 11:24:33 2010 -0700 integrating org-babel into org.el I haven't found a similar report on the mailing list. Since C-c C-o is quite basic and many people must use it, I'm guessing I'm doing something wrong. Help please? Thanks! Hsiu-Khuern.
[O] Too liberal stripping of commas in export? commit 20044297 strip protective commas from literal code blocks
Hi,
Eric Schulte's commit 20044297 introduced a change whereby the code
block in this Org file
=
* test
#+begin_src r
a - c(1
, 2
, 3)
#+end_src
=
is exported into this LaTeX fragment:
=
\begin{minted}[]{r}
a - c(1
2
3)
\end{minted}
=
The leading commas are removed! I think these commas shouldn't be
treated as protective (and hence shouldn't be removed), since they are
not in the leftmost column inside the block. org-edit-special does
the right thing for me in this example.
Thanks,
Hsiu-Khuern.
[O] Re: [FIXED] Re: :latex-listings publishing option not used; minted + beamer incompatibility?
On Mon, Feb 14, 2011 at 3:15 AM, Dan Davison dandavis...@gmail.com wrote:
Hsiu-Khuern Tang tan...@gmail.com writes:
Hi Dan,
* On Wed 09:09AM, 20 Oct 2010, Dan Davison (davi...@stats.ox.ac.uk) wrote:
Hsiu-Khuern Tang tan...@gmail.com writes:
BTW, has anyone used minted with beamer? I get errors like
Runaway argument?
int main(int argc, char **argv) { \ETC.
! Paragraph ended before \FV@BeginScanning was complete.
This problem is now fixed in Org. The problem was that frames using
minted needed to be marked as fragile; Org was only doing this for
verbatim and lstlisting.
...
I can confirm this fix. Thanks, Dan!
--
Best,
Hsiu-Khuern.
Re: [O] Re: [Orgmode] [PATCH] Allow inclusion of author's email in LaTeX export
On Tue, Mar 1, 2011 at 9:36 AM, Bastien b...@altern.org wrote:
Hi Hsiu-Khuern,
Hsiu-Khuern Tang tan...@gmail.com writes:
I updated to the latest git version, but I'm still getting unescaped
underscores in the \thanks{} argument.
I pushed another fix, please check again.
--
Bastien
Yes, works now, thanks!
--
Hsiu-Khuern.
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[O] Re: [Orgmode] [PATCH] Allow inclusion of author's email in LaTeX export
Hi Bastien,
On Sat, Feb 26, 2011 at 8:31 AM, Bastien b...@altern.org wrote:
Hsiu-Khuern Tang tan...@gmail.com writes:
I noticed that special characters in the email, such as an underscore,
are not escaped. This causes LaTeX errors.
To reproduce, put this line at the top of an org file and try to
export to PDF via LaTeX:
#+EMAIL: first_l...@example.com
Fixed, thanks.
--
Bastien
I updated to the latest git version, but I'm still getting unescaped
underscores in the \thanks{} argument. From the output of git log,
I think the change was supposed to be in commit
0c7d8e615a931e6db222cf7667c1a8d6968b2007, but I couldn't find the code
change that affects this.
Best,
Hsiu-Khuern.
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [PATCH] Allow inclusion of author's email in LaTeX export
Hi, I noticed that special characters in the email, such as an underscore, are not escaped. This causes LaTeX errors. To reproduce, put this line at the top of an org file and try to export to PDF via LaTeX: #+EMAIL: first_l...@example.com Thanks, Hsiu-Khuern. On Mon, Jan 17, 2011 at 11:21 AM, Bastien bastien.gue...@wikimedia.fr wrote: Hi Lawrence, Lawrence Mitchell we...@gmx.li writes: * org-latex.el (org-export-latex-make-header): Export email in author line if `org-export-email-info' is non-nil. Thanks a lot - I just applied a slightly modified version of your patch. The trick is to use (plist-get opt-plist :email-info) instead of `org-export-email-info' so that in-buffer options are taken into account. Thanks for submitting this! -- Bastien ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Wishlist: let org-refile find buffers that have been renamed
Hi, I have a perhaps unusual way of organizing my agenda files like this: project1/notes.org project2/notes.org ... and I use rename-buffer in each notes.org to make sure I can tell them apart, e.g., - In project1/notes.org, I have (rename-buffer project1.org) - In project2/notes.org, I have (rename-buffer project2.org) This works fine with commands like C-c b (org-iswitchb), which displays the renamed buffers ( project1.org and project2.org) in the minibuffer prompt. However, C-c w (org-refile) does not find these targets --- it would be nice if it did! I think the problem is in the function org-get-refile-targets in org.el, but I'm not good at hacking elisp. I am using ido completion (org-completion-use-ido is non-nil). Thanks! Hsiu-Khuern. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Wishlist: let org-refile find buffers that have been renamed
Hi Samuel, Thanks for the suggestion. I just tried it, and it does a nice job choosing easy-to-identify buffer names. But those buffer names again do not come up for selection by C-c C-w (org-refile). -- Best, Hsiu-Khuern. On Wed, Dec 22, 2010 at 4:58 PM, Samuel Wales samolog...@gmail.com wrote: Did you try uniquify? ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Omit top level heading in latex export?
Hi all, Even though this problem has been solved by exporting a region consisting of a single subtree ... I've always thought that it would be nice to be able to get the same behavior using org-publish, so that it can be used more easily in scripts. To be concrete: if I have this structure: * Essays:export: ** Essay One ** Essay Two I'd like to be able to use a publishing option to export Essays and get output like Section 1 Essay One Section 2 Essay Two (which is what we get when we select the subtree Essays as the active region before exporting) instead of Section 1 Essays Section 1.1 Essay One Section 1.2 Essay Two -- Best, Hsiu-Khuern. On Sun, Oct 3, 2010 at 8:27 AM, suvayu ali fatkasuvayu+li...@gmail.com wrote: On 3 October 2010 06:31, Indraneel Majumdar indran...@indraneel.info wrote: Hi, I'm running into a problem with latex export. I have several essays under a top level heading Essays. How can I export say only one essay without the top level heading Essays also showing up in the output as a Section? I want the heading of my essay to be displayed as a latex section. Is this possible in any simple way? The manual describes some option to define my own class in the .emacs file, but I couldn't understand that very well. eg. * Essays ** Essay One ** Essay Two I want to export only Essay Two (eg with a :export: tag) and don't want Essays to show up. What about just exporting the subtree you want? I believe the way to do that is to go to the subtree and while exporting limit the export with `1'. Hope this helps. Thanks in advance, Indraneel -- Suvayu Open source is the future. It sets us free. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: :latex-listings publishing option not used; minted + beamer incompatibility?
Hi Dan,
* On Wed 09:09AM, 20 Oct 2010, Dan Davison (davi...@stats.ox.ac.uk) wrote:
Hsiu-Khuern Tang tan...@gmail.com writes:
BTW, has anyone used minted with beamer? I get errors like
Yes, I exported Eric Fraga's babel/beamer slides example using minted
last week and it worked fine. However,
Runaway argument?
int main(int argc, char **argv) { \ETC.
! Paragraph ended before \...@beginscanning was complete.
yes, I now get that error. So something has changed recently. I'm using
fully updated ubuntu 10.10. What system are you using?
I'm using Debian unstable. My texlive package is version 2009-8; the
current version in Debian unstable is 2009-11.
A search on Google shows lots of reports related to beamer and Sweave.
So perhaps we're seeing the effects of a recent change in the tex/latex
stack, rather than an emacs/org/minted/pygments problem??
Some of the Google results go back quite a long time, e.g.,
http://tolstoy.newcastle.edu.au/R/help/04/12/9454.html. I'm staying
with listings for now.
--
Best,
Hsiu-Khuern.
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] :latex-listings publishing option not used; minted + beamer incompatibility?
Hi,
The :latex-listings option appears to be unused at the present. It
would be great to activate this as an alternative to the
org-export-latex-listings variable. (Same thing for :latex-minted.)
BTW, has anyone used minted with beamer? I get errors like
Runaway argument?
int main(int argc, char **argv) { \ETC.
! Paragraph ended before \...@beginscanning was complete.
A search on Google shows lots of reports related to beamer and Sweave.
Thanks,
--
Hsiu-Khuern.
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: No link found error during export of source block when headline has link
Hi Eric, I also confirm that the issue in my original post has been fixed. Thanks! -- Hsiu-Khuern. On Wed, Oct 6, 2010 at 7:52 AM, Eric Schulte schulte.e...@gmail.com wrote: This issue should now be fixed. Best -- Eric ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] bug: babel: Export of temporary buffers fails
Hi Eric, Are you also seeing the problem reported at http://thread.gmane.org/gmane.emacs.orgmode/30855? I checked out the latest git version and that problem still exists. I don't know how closely it is related to the problem in this thread, but it was caused by the same commit (efdf78172d9f7c0070c781d136a9b49a2a56fcc4) -- hoping you can shed some light on this. Thanks! -- Best, Hsiu-Khuern. On Mon, Oct 4, 2010 at 7:39 AM, Eric Schulte schulte.e...@gmail.com wrote: Ok, Thanks for your persistence in explaining this to me. I've just pushed up a change which should fix this issue. Best -- Eric Puneeth puncha...@gmail.com writes: Hi Eric, On Mon, Oct 4, 2010 at 6:43 PM, Eric Schulte schulte.e...@gmail.com I've just tried exporting an org-mode buffer containing babel code blocks to a temporary file using C-c C-e H, and it worked without problem. Could you send me an example org-mode file that throws the error your described? Have you exported from a temporary buffer? or a buffer visiting a file? To reproduce the error that I get, 1. Switch to scratch buffer (or a new temporary buffer) 2. M-x org-mode to change the mode to Org-mode 3. Yank the following text into it - * Hello World #+begin_src python print Hello, World #+end_src - 4. C-c C-e H You should get the error set-buffer: Wrong type argument: stringp, nil HTH, Puneeth ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] No link found error during export of source block when headline has link
Hi all, When I export this file to HTML * [[http://www.example.com][example]] #+BEGIN_SRC R 1 #+END_SRC I get a No link found error. The responsible function seems to be org-open-link-from-string(#([[/tmp/a.org::%5B%5Bhttp://www.example.com%5D%5Bexample%5D%5D][/tmp/a.org::[[http://www.example.com][example]]] ...) Please see the attached backtrace. I am using the latest version from git. I used git bisect and found that the first bad commit is efdf78172d9f7c0070c781d136a9b49a2a56fcc4. -- Best, Hsiu-Khuern. Debugger entered--Lisp error: (error No link found) signal(error (No link found)) error(No link found) org-open-at-point(nil #buffer a.org) org-open-link-from-string(#([[/tmp/a.org::%5B%5Bhttp://www.example.com%5D%5Bexample%5D%5D][/tmp/a.org::[[http://www.example.com][example; 2 14 (org-attr nil) 20 42 (org-attr nil) 48 55 (org-attr nil) 63 110 (org-attr nil))) org-babel-exp-src-blocks(#(1 0 1 (font-lock-fontified t fontified t)) #(R 0 1 (fontified t font-lock-fontified t))) apply(org-babel-exp-src-blocks #(1 0 1 (font-lock-fontified t fontified t)) #(R 0 1 (fontified t font-lock-fontified t))) byte-code(\306\307\211\211\211\211\211\211\211\211 % ' (\310\311!\211 )\205# \311K *\312\216\311\313M\210eb\210`\314\315\307\306#\203\326 \316\317!G\320\316\321!\227!%\322 +\323\216\324\316\325!\326\*\316\327!,\206` \330\n\235\211\204p \322 +\331\216\332 !*%'\204 %'B'\322 +\333\216\311\f\334\224\\210*\335%-\\211 .A@)\211\203\320 \322 +\336\216%/\203\257 \337\202\264 \340 \n#*\211 0\203\317 \3410\306\211#\210 \204\317 \342\334\224\334\225#\210)\334\225\2020 \311\fd\\210\343\344!. \207 [progress-marker preserve-indent headers body start func t nil fboundp interblock ((byte-code \203 \302M\210\202 \303\302!\210\302\207 [--cl-letf-bound-- --cl-letf-save-- interblock fmakunbound] 2)) #[(start end) \301\302\\207 [org-export-interblocks mapcar #[... \211A@)\n \\207 [pair x start end] 4]] 3] re-search-forward ^\\([ ]*\\)#\\+begin_\\(\\S-+\\)[ ]*\\(.*\\)?[ \n]\\([^ ]*?\\)[ \n][]*#\\+end_\\S-+.*[ \n]? match-string 1 intern 2 match-data ((byte-code \301\302\\207 [save-match-data-internal set-match-data evaporate] 3)) org-split-string 3 [ ]+ 4 -i ((byte-code \301\302\\207 [save-match-data-internal set-match-data evaporate] 3)) org-remove-indentation ((byte-code \301\302\\207 [save-match-data-internal set-match-data evaporate] 3)) 0 assoc ((byte-code \301\302\\207 [save-match-data-internal set-match-data evaporate] 3)) apply replace-match indent-code-rigidly run-hooks org-export-blocks-postblock-hook type indentation types case-fold-search --cl-letf-bound-- --cl-letf-save-- save-match-data-internal org-src-preserve-indentation org-export-blocks x org-export-blocks-witheld replacement] 11) org-export-blocks-preprocess() run-hooks(org-export-preprocess-after-include-files-hook) org-export-preprocess-string(#(* [[http://www.example.com][example]]\n\n #+BEGIN_SRC R\n1\n #+END_SRC\n 0 2 (fontified t face org-level-1) 2 4 (fontified t face org-link org-no-flyspell t invisible org-link keymap (keymap ... ... ...) mouse-face highlight font-lock-multiline t help-echo LINK: http://www.example.com;) 4 27 (fontified t face org-link org-no-flyspell t mouse-face highlight keymap (keymap ... ... ...) invisible org-link font-lock-multiline t help-echo LINK: http://www.example.com;) 27 28 (fontified t face org-link org-no-flyspell t mouse-face highlight keymap (keymap ... ... ...) invisible org-link font-lock-multiline t help-echo LINK: http://www.example.com; rear-nonsticky (mouse-face highlight keymap invisible intangible help-echo org-linked-text)) 28 34 (fontified t face org-link org-no-flyspell t mouse-face highlight keymap (keymap ... ... ...) font-lock-multiline t help-echo LINK: http://www.example.com;) 34 35 (fontified t face org-link org-no-flyspell t mouse-face highlight keymap (keymap ... ... ...) rear-nonsticky (mouse-face highlight keymap invisible intangible help-echo org-linked-text) font-lock-multiline t help-echo LINK: http://www.example.com;) 35 36 (fontified t face org-link org-no-flyspell t invisible org-link keymap (keymap ... ... ...) mouse-face highlight font-lock-multiline t help-echo LINK: http://www.example.com;) 36 37 (fontified t face org-link org-no-flyspell t invisible org-link keymap (keymap ... ... ...) mouse-face highlight font-lock-multiline t help-echo LINK: http://www.example.com; rear-nonsticky (mouse-face highlight keymap invisible intangible help-echo org-linked-text)) 37 38 (fontified t) 38 39 (fontified t) 39 41 (fontified t font-lock-fontified t font-lock-multiline t face org-meta-line) 41 43 (font-lock-fontified t fontified t font-lock-multiline t face org-meta-line) 43 49 (font-lock-fontified t fontified t
Re: [Orgmode] Wishlist: indicate language in LaTeX export of literal source examples
Hi Eric,
Thanks for telling me about this solution. It is somewhat of an
overkill, but I'll take it :) The listings documentation is also
quite impressive.
-- Hsiu-Khuern.
On Mon, Feb 8, 2010 at 6:11 PM, Eric Schulte schulte.e...@gmail.com wrote:
Hi Hsiu-Khuern,
This may be overkill, but you could try the following which will
indicate the source-code language in the generated .tex
;; tell org to use listings
(setq org-export-latex-listings t)
If you actually want to use the listings package you can also include
the following
;; you must include the listings package
(add-to-list 'org-export-latex-packages-alist '( listings))
;; if you want colored source code then you need to include the color package
(add-to-list 'org-export-latex-packages-alist '( color))
in either case a block such as
#+begin_src R
...
#+end_src
will export to
\lstset{language=R}
\begin{lstlisting}
...
\end{lstlisting}
Best -- Eric
Hsiu-Khuern Tang tan...@gmail.com writes:
(Resending because of earlier problems -- my apologies if this is a
duplicate!)
Hi,
Currently, literal examples (#+BEGIN_EXAMPLE and #+BEGIN_SRC) are exported to
\begin{verbatim}
...
\end{verbatim}
in LaTeX. For #+BEGIN_SRC blocks, could we indicate the language in a
LaTeX comment, e.g.,
#+BEGIN_SRC R
...
#+END_SRC
becomes
% R
\begin{verbatim}
...
\end{verbatim}
I'm trying to post-process the LaTeX output, and knowing the language would
help me.
Thanks!
--
Best,
Hsiu-Khuern.
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Wishlist: indicate language in LaTeX export of literal source examples
(Resending because of earlier problems -- my apologies if this is a duplicate!)
Hi,
Currently, literal examples (#+BEGIN_EXAMPLE and #+BEGIN_SRC) are exported to
\begin{verbatim}
...
\end{verbatim}
in LaTeX. For #+BEGIN_SRC blocks, could we indicate the language in a
LaTeX comment, e.g.,
#+BEGIN_SRC R
...
#+END_SRC
becomes
% R
\begin{verbatim}
...
\end{verbatim}
I'm trying to post-process the LaTeX output, and knowing the language would
help me.
Thanks!
--
Best,
Hsiu-Khuern.
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Unnecessary comma escapes in HTML export of #+INCLUDE files
* On Wed 09:33AM +, 02 Sep 2009, Carsten Dominik (carsten.domi...@gmail.com) wrote: Ah, yes, thank you for that detail. Fixed now. Yes, it works now, thank you very much! -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Unnecessary comma escapes in HTML export of #+INCLUDE files
* On Fri 05:45AM +, 24 Jul 2009, Tang, Hsiu-Khuern (hsiu-khuern.t...@hp.com) wrote: * On Fri 01:22AM +, 24 Jul 2009, Bastien (bastiengue...@googlemail.com) wrote: Hi Hsiu-Khuern, I've just pushed a fix for this: when the src switch is present, including a file won't escape org-like lines. With a bare #+include we still escape lines starting with * or #. Please test it and report any problem. It works beautifully now. Thank you very much for the fix! It looks Org has reverted to the old behavior: inserting a comma at a beginning of every line in the #INCLUDE'd file that starts with whitespace followed by #. For example, if you export this as ascii (see http://article.gmane.org/gmane.emacs.orgmode/15718): File 1: a.org == * test #+INCLUDE: a.sh src sh == File 2: a.sh == #!/bin/sh ## shell comment echo This is a test == the output contains the line , ## shell comment. Related question: what git commands does one use to obtain all the commits that changed a particular range of lines in a file? I'm quite lost with git. -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Unnecessary comma escapes in HTML export of #+INCLUDE files
* On Tue 10:47PM +, 01 Sep 2009, Dokos, Nicholas (nicholas.do...@hp.com) wrote: Hsiu-Khuern Tang hsiu-khuern.t...@hp.com wrote: It looks Org has reverted to the old behavior: inserting a comma at a beginning of every line in the #INCLUDE'd file that starts with whitespace followed by #. For example, if you export this as ascii (see http://article.gmane.org/gmane.emacs.orgmode/15718): File 1: a.org == * test #+INCLUDE: a.sh src sh == File 2: a.sh == #!/bin/sh ## shell comment echo This is a test == the output contains the line , ## shell comment. Related question: what git commands does one use to obtain all the commits that changed a particular range of lines in a file? I'm quite lost with git. There was some churn for this particular functionality, but since I don't really understand what is *supposed* to happen, I'll just refer you (and Carsten and Bastien, both of whom made -possibly conflicting- changes to this functionality) to the following exchange in the archive, hoping it will shed some light and lead to a satisfactory resolution for all involved: http://thread.gmane.org/gmane.emacs.orgmode/16244/focus=16259 The relevant commits are 68b65e8f480c17cfe1024001c236eb4065893f4d and dfd3749a273cc9f9a1d954363ea6de87049d17a7 Thanks, Nick Thanks for pointing me to the relevant commits, both of which changed the org-get-file-contents function. I'm not sure what the correct behavior for that function is, since it may ultimately be used for different purposes, e.g., to generate an agenda and for exporting. For exporting to various formats, is there any reason to escape Org-like lines -- headers and comments -- of an #INCLUDE'd file, since the file contents are indented in the output anyway and so there can be no confusion? I'm not sure that the indentation occurs for all export formats, but it seems to be the case for ASCII and HTML export. At any rate, the docstring of org-get-file-contents is inconsistent with the behavior: If MARKUP, don't protect org-like lines, the exporter will take care of the block they are in. It is actually protecting org-like lines when the markup is src or example. -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Use of \w Emacs regexp in org-export-bibtex.el excludes BiBTeX filenames with underscore
Hi Taru, In contrib/lisp/org-export-bibtex.el, the BiBTeX file has to match the Emacs regexp \w+. So a line like #+BIBLIOGRAPHY: mybib_new will not work because of the underscore character in the filename. (I suppose the actual behavior depends on the local Emacs settings that affect the syntax table.) May I propose changing the regexp to [[:alnum:]_]+? Initially, I was stumped by this because I thought \w was a regular regexp :), such as defined in sed, and would match underscores as well. -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] dvipng: -E is not a valid option
* On Wed 03:13PM +, 05 Aug 2009, Carsten Dominik (carsten.domi...@gmail.com) wrote: Actually, I have no idea, this was copied from latex2png.el. If you remove the -E, does it still work? It works with and without the -E. dvipng appears to discard invalid options (with a warning). The dvipng Texinfo manual does not list the -E option, I think it is safe to take it out. - Carsten On Aug 5, 2009, at 3:15 AM, Hsiu-Khuern Tang wrote: Hi all, In org.el, dvipng is called with the -E option, but I can't find out what this option does. If I call dvipng -E ... directly from the Linux shell, I get /usr/bin/dvipng warning: -E is not a valid option [1] -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] dvipng: -E is not a valid option
Hi all, In org.el, dvipng is called with the -E option, but I can't find out what this option does. If I call dvipng -E ... directly from the Linux shell, I get /usr/bin/dvipng warning: -E is not a valid option [1] -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Export to org?
Hi, Is there an easy way to export an org file to another org file, stripping away any subtrees that are tagged noexport or marked as comments? The idea is to discard anything that is also ignored by the other export formats, such as HTML. I would find this a useful feature to have, for example, for distributing Org files to other people without showing subtrees that are still works-in-progress. -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Export to org?
* On Thu 12:41AM +, 30 Jul 2009, Bernt Hansen (be...@norang.ca) wrote: Hsiu-Khuern Tang hsiu-khuern.t...@hp.com writes: Hi, Is there an easy way to export an org file to another org file, stripping away any subtrees that are tagged noexport or marked as comments? The idea is to discard anything that is also ignored by the other export formats, such as HTML. I would find this a useful feature to have, for example, for distributing Org files to other people without showing subtrees that are still works-in-progress. Hi, org-publish handles this now. An entry like this: :publishing-function (org-publish-org-to-html org-publish-org-to-org) in my org-publish-project-alist. This produces both a .html and a .org file from the original .org file. Any comments and subtrees marked with a noexport tag will not be included in the exported org file. More details on my complete setup is here: http://doc.norang.ca/org-mode.html#PublishingProjects HTH, Bernt This is exactly what I was looking for. I must have skipped the chapter on publishing in the Org manual. Thanks a lot for the pointers! -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Unnecessary comma escapes in HTML export of #+INCLUDE files
* On Fri 01:22AM +, 24 Jul 2009, Bastien (bastiengue...@googlemail.com) wrote: Hi Hsiu-Khuern, I've just pushed a fix for this: when the src switch is present, including a file won't escape org-like lines. With a bare #+include we still escape lines starting with * or #. Please test it and report any problem. It works beautifully now. Thank you very much for the fix! -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Unnecessary comma escapes in HTML export of #+INCLUDE files
* On Wed 07:50AM +, 22 Jul 2009, Bastien (bastiengue...@googlemail.com) wrote: Hi, Tang, Hsiu-Khuern hsiu-khuern.t...@hp.com writes: If I include a file in my Org file, say using #+INCLUDE: script.sh src sh and export to HTML, the included file shows up as a pre block, which is nice. However, a leading comma is put in front of every line that starts with a #, even those with leading whitespace. I understand that a comma is used to escape # in the first column of literal examples, to distinguish from Org comment lines. (This escaping is no longer strictly necessary, since the #+BEGIN_EXAMPLE block can now be indented.) I cannot reproduce this. Which version of Org are you using? I'm using 6.28trans. Can you try to reproduce this using these two files: File 1: a.org == * test #+INCLUDE: a.sh src sh == File 2: a.sh == #!/bin/sh ## shell comment echo This is a test == If I export a.org to HTML, the output has a comma before ## shell comment (but none before #!/bin/sh, so maybe only lines with leading whitespace before a # are affected). Actually, the problem shows up even when exporting to ascii: == Author: ht...@localhost Date: 2009-07-22 10:31:37 PDT Table of Contents = 1 test 1 test ~~~ #!/bin/sh , ## shell comment echo This is a test == Thanks for looking into this! -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] cannot edit two source code examples simultaneously
* On Sat 05:39PM +, 16 May 2009, Carsten Dominik (carsten.domi...@gmail.com) wrote: Hi Hsiu-Khuern, On May 15, 2009, at 7:38 AM, Hsiu-Khuern Tang wrote: Hi Carsten, You recently changed org-edit-src-code to use a separate buffer instead of an indirect buffer. One side effect of this is that I can no longer edit several code examples at the same time: opening the second buffer will silently discard any changes made in the first. I would prefer this behavior: when opening the second edit source buffer, write any changes in the first buffer to the originating Org buffer (but don't save it, of course). Another approach is to use different buffer names. I think the second idea is better, provided that a mechanism ensures that not two editing instances of the same region are created. This is what I have implemented now. Thank you for your report. Thanks for implementing this and the subsequent refinements based on Dan's and Taru's inputs! -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] cannot edit two source code examples simultaneously
Hi Carsten, You recently changed org-edit-src-code to use a separate buffer instead of an indirect buffer. One side effect of this is that I can no longer edit several code examples at the same time: opening the second buffer will silently discard any changes made in the first. I would prefer this behavior: when opening the second edit source buffer, write any changes in the first buffer to the originating Org buffer (but don't save it, of course). Another approach is to use different buffer names. Thank you for your consideration! -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] greek letters in subscripts with the export option ^:{}
* On Wed 09:13AM +, 11 Mar 2009, Carsten Dominik (domi...@science.uva.nl)
wrote:
Fixed, thanks.
There are still problems with the in LaTeX export, but it does work
OK now in HTML.
I can confirm that it works. Thanks!
On Mar 11, 2009, at 1:42 AM, Tang, Hsiu-Khuern wrote:
Hi all,
If I export the file
--
#+OPTIONS: ^:{}
* test
a_{\alpha}
a_{foo}
--
as HTML, I get a_{alpha;} but asubfoo/sub: \alpha is not
subscripted
but foo is. I was expecting both to be subscripted, since they are
in {}.
--
Best,
Hsiu-Khuern.
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
--
Best,
Hsiu-Khuern.
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Sorting a column of inactive dates
* On Fri 03:53PM +, 06 Feb 2009, Carsten Dominik (domi...@science.uva.nl) wrote: On Feb 3, 2009, at 1:06 AM, Hsiu-Khuern Tang wrote: Hi all, I have a table where one column consists of inactive dates, such as this: | Date | OK? | |--+-| | [2009-01-30 Fri] | x | | [2009-01-27 Tue] | x | | [2009-01-28 Wed] | x | I can't sort the table by that column. If I change the dates to active, then sorting (by time) works fine. Is this behavior intentional? Yes, intentional, because the same routine also does sorting of entries and should prefer active time stamps. However, I realize that we can still look for an inactive time stamp when no active one can be found. I just pushed this change. Thank you for this change; it works great! -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Wishlist: drop a4paper option from the default LaTeX class
* On Sat 09:44PM +, 31 Jan 2009, Carsten Dominik (domi...@science.uva.nl)
wrote:
I have removed the a4paper from the default classes.
Thanks.
That's great, thank you!
On Jan 29, 2009, at 8:53 PM, Hsiu-Khuern Tang wrote:
The default class article in the variable org-export-latex-classes
(which
Emacs can't find anymore -- I have just filed a report) is
\documentclass[11pt,a4paper]{article}
I suggest dropping the a4paper option and letting the local TeX
customization
determine the default papersize.
--
Best,
Hsiu-Khuern.
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
--
Best,
Hsiu-Khuern.
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Sorting a column of inactive dates
Hi all, I have a table where one column consists of inactive dates, such as this: | Date | OK? | |--+-| | [2009-01-30 Fri] | x | | [2009-01-27 Tue] | x | | [2009-01-28 Wed] | x | I can't sort the table by that column. If I change the dates to active, then sorting (by time) works fine. Is this behavior intentional? -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] POLL: the 40 variables project
* On Thu 08:49AM +, 29 Jan 2009, Carsten Dominik (domi...@science.uva.nl) wrote: Hi, yesterday I did this command in my org-mode git repo: grep defcustom lisp/*el |wc -l and got 378 as an answer. 378 user-customizable variables, no kidding. However, I bet that only about 10% of these are really used by more that one user :-). So when a new users starts digging into Org-mode, they simply must be confused by the amount of variables that can be set. So here is the idea: I would like to find out which variables users actually customize. This could be the basis for a great article on Worg, describing just these selected variables. In addition, I could make a special customization group which only contains those variables (Emacs allows to put a variable into several groups). It would be awesome to have, and a much easier start into customizing Org. So here is my question to all of you. Could you, in reply to this message, list all the Org-related variables that you have customized, along with the values you used? If you want to do more, I'd also love to see comments on - why you set the variable like this - if you feel that the default value of that variable should be different - Any other comments you might what to give. (custom-set-variables ;; ;; non-Org customizations omitted ... ;; ;; ;; some customized agenda commands, probably not widely useful: ;; '(org-agenda-custom-commands (quote ((A Agenda + NEXT + STARTED ((agenda nil) (tags-todo NEXT nil) (todo STARTED nil)) nil) (S TODO list, skip unscheduled and :waiting: alltodo ((org-agenda-skip-function (quote (org-agenda-skip-entry-if (quote unscheduled) (quote regexp) :waiting:) (U TODO list, skip scheduled and :waiting: alltodo ((org-agenda-skip-function (quote (org-agenda-skip-entry-if (quote scheduled) (quote regexp) :waiting: ;; '(org-agenda-log-mode-items (quote (closed state))) '(org-agenda-sorting-strategy (quote ((agenda time-up category-up priority-down) (todo category-up tag-up) (tags category-keep priority-down) (search category-keep '(org-completion-use-ido t) '(org-export-latex-remove-from-headlines (quote (:todo nil :priority t :tags t))) '(org-export-with-LaTeX-fragments t) '(org-log-done (quote time)) '(org-todo-state-tags-triggers (quote ((STARTED (NEXT) ) I also added a new class myarticle to org-export-latex-classes that is the same as article without the a4paper option. I would vote for dropping the a4paper option from the default class, and let the papersize be handled by the local TeX customization. -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Can't customize org-export-latex-classes
In Org-mode 6.19b, running M-x customize-variable org-export-latex-classes gives an error No match. -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Wishlist: drop a4paper option from the default LaTeX class
The default class article in the variable org-export-latex-classes (which
Emacs can't find anymore -- I have just filed a report) is
\documentclass[11pt,a4paper]{article}
I suggest dropping the a4paper option and letting the local TeX customization
determine the default papersize.
--
Best,
Hsiu-Khuern.
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Can't customize org-export-latex-classes
* On Thu 08:15PM +, 29 Jan 2009, Christopher Suckling (suckling.l...@googlemail.com) wrote: On 29 Jan 2009, at 19:48, Hsiu-Khuern Tang wrote: In Org-mode 6.19b, running M-x customize-variable org-export-latex-classes gives an error No match. Have you (require 'org-export-latex) in your .emacs? That fixed it, thanks! I never had to load this feature before. Maybe this is because it was automatically loaded by the LaTeX export functions? -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Searching SCHEDULED/DEADLINE properties turns up spurious headings
* On Tue 09:35AM +, 13 Jan 2009, Carsten Dominik (domi...@science.uva.nl) wrote: On Jan 12, 2009, at 6:50 PM, Hsiu-Khuern Tang wrote: * On Sat 08:54PM +, 10 Jan 2009, Carsten Dominik (domi...@science.uva.nl ) wrote: Hi Hsiu, I believe this is a misunderstanding. You are constructing a sparse tree. Sparse tree always show all top-level headlines. The search really only matches the second one, as you can see from the highlighted stars. When I run that search (C-c \ +DEADLINE=2009-01-28 RET), all the three headlines have highlighted stars. (I am running Org-mode 6.17trans.) Hi Hsiu, thanks for insisting. You are right, there was a bug. Fixed now. - Carsten It does work now! Thank you very much for fixing this! -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Does secondary filtering allow multiple tags?
* On Sat 11:12AM +, 10 Jan 2009, Carsten Dominik (domi...@science.uva.nl) wrote: Hi Hsiu, nice hack. But I am still wondering why you do not use primary filtering for this, i.e. a tags search for project1|project2 C-c a m project1|project2 RET I couldn't get such a search to work with a daily/weekly/monthly agenda view. I was trying to restrict the weekly (say) agenda view to just two projects (identified by tags), which seems like a nice view for scheduling tasks. I would love a simple way to do this. If different projects were in different files, then one can modify org-agenda-files temporarily to achieve this, but my projects are not always cleanly separated that way. -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Searching SCHEDULED/DEADLINE properties turns up spurious headings
* On Sat 08:54PM +, 10 Jan 2009, Carsten Dominik (domi...@science.uva.nl) wrote: Hi Hsiu, I believe this is a misunderstanding. You are constructing a sparse tree. Sparse tree always show all top-level headlines. The search really only matches the second one, as you can see from the highlighted stars. When I run that search (C-c \ +DEADLINE=2009-01-28 RET), all the three headlines have highlighted stars. (I am running Org-mode 6.17trans.) - Carsten On Jan 10, 2009, at 12:32 AM, Hsiu-Khuern Tang wrote: I find that doing a tags search for SCHEDULED or DEADLINE turns up headings that do not have any schedule or deadlines. Using the example from http://article.gmane.org/gmane.emacs.orgmode/10274 : , | #+SEQ_TODO: NEXT WAITING | DONE | #+STARTUP: overview | | * DONE Test1 |CLOSED: [2009-01-07 Wed 12:26] | | * NEXT Test2 |DEADLINE: 2009-01-28 Wed | | * Test3 ` If I type C-c \ +DEADLINE=2009-01-28 RET all three headlines are selected! I expected to match the second headline only. -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Does secondary filtering allow multiple tags?
* On Fri 07:38AM +, 09 Jan 2009, Carsten Dominik (domi...@science.uva.nl)
wrote:
On Jan 9, 2009, at 2:55 AM, Hsiu-Khuern Tang wrote:
Hi all,
Suppose I have tagged some of my TODO headings. In an agenda view,
is it
currently possible to filter (using org-agenda-filter-by-tag) all
entries that
are tagged with (say) either project1 _or_ project2? One can
certainly do
project1 _and_ project2 by narrowing the filter.
No.
- Carsten
Here's a workaround. I use org-map-entries to select all headlines directly
tagged with project1 or project2 and tag them with something unique, say
CUR. Then I can use the ordinary filter mechanism in an agenda view to
restrict to headlines tagged with CUR.
,
| (setq cur_tags '(project1 project2))
|
| ;; Unbind the variable
| ;; (makunbound 'cur_tags)
|
| (setq match_string (concat +TAGS={ (mapconcat (lambda (x) x)
| cur_tags \|) }))
|
| ;; Remove the CUR tag:
| (org-map-entries '(org-toggle-tag CUR) CUR 'agenda)
|
| ;; Turn on the CUR tag for all headlines (directly) tagged with
| ;; any member of cur_tags
| (org-map-entries '(org-toggle-tag CUR 'on) match_string 'agenda)
|
| ;; Count the number of headlines (directly) tagged with any member of
| ;; cur_tags:
| (length (org-map-entries t match_string 'agenda))
`
Maybe someone will find this useful, or think of a more elegant solution.
--
Best,
Hsiu-Khuern.
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Does secondary filtering allow multiple tags?
* On Fri 07:18PM +, 09 Jan 2009, Hsiu-Khuern Tang (hsiu-khuern.t...@hp.com)
wrote:
Here's a workaround. I use org-map-entries to select all headlines directly
tagged with project1 or project2 and tag them with something unique, say
CUR. Then I can use the ordinary filter mechanism in an agenda view to
restrict to headlines tagged with CUR.
,
| (setq cur_tags '(project1 project2))
|
| ;; Unbind the variable
| ;; (makunbound 'cur_tags)
|
| (setq match_string (concat +TAGS={ (mapconcat (lambda (x) x)
| cur_tags \|) }))
Correction: the above should have an extra \:
,
| (setq match_string (concat +TAGS={ (mapconcat (lambda (x) x)
| cur_tags \\|) }))
`
| ;; Remove the CUR tag:
| (org-map-entries '(org-toggle-tag CUR) CUR 'agenda)
|
| ;; Turn on the CUR tag for all headlines (directly) tagged with
| ;; any member of cur_tags
| (org-map-entries '(org-toggle-tag CUR 'on) match_string 'agenda)
|
| ;; Count the number of headlines (directly) tagged with any member of
| ;; cur_tags:
| (length (org-map-entries t match_string 'agenda))
`
--
Best,
Hsiu-Khuern.
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Including state-changed headings in the agenda
* On Thu 08:04AM +, 06 Nov 2008, Carsten Dominik ([EMAIL PROTECTED]) wrote: On Oct 29, 2008, at 8:17 PM, Hsiu-Khuern Tang wrote: Hi, Let's say I have a repeating task like this: ** TODO Do this SCHEDULED: 2008-10-29 Wed +1w Cycling to a done state will track the done time and increment the scheduled time according to the repeater: ** TODO Do this - State DONE [2008-10-29 Wed 10:44] SCHEDULED: 2008-11-05 Wed +1w How can I display such items in the daily agenda? Turning on log mode will only display CLOSED items, but since the above task is not closed, it doesn't show up. This is now possible. To do it just for a single view, press `C-u l' instead of `l' in the daily/weekly agenda. If you like what you see and want this always to be present when you turn on log mode, customize the variable `org-agenda-log-mode-items'. Now, if you finish only ones task during a day, but with several state changes, you can feel very productive already :-) HTH Yes, it does help! I tested this using the development version, and things work just as described. I now have org-agenda-log-mode-items configured to (closed state). Thank you very much for implementing this! -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Including state-changed headings in the agenda
* On Tue 08:47AM +, 04 Nov 2008, Carsten Dominik ([EMAIL PROTECTED]) wrote: Are there people who would find it useful if log-mode in the agenda showed all logged state changes? Might get crowded - but it is certainly possible to implement that. Since I started this thread, you can count me as a yes vote :) I'm still experimenting with different ways of organizing using Org-mode, so I can't say for sure I'll use this feature in the end. I think it's nice to be able to see state changes without using full-blown clocking. Personally, my daily agenda won't get too crowded with these entries since I don't get that many tasks done in a day, but that's no fault of Org-mode :) Thanks for being so receptive to users' wishlists! -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Including state-changed headings in the agenda
* On Fri 07:29PM +, 31 Oct 2008, [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: Bernt Hansen [EMAIL PROTECTED] writes: However I think what Hsiu-Khuern Tang is asking is that _completed_ logs show up in the agenda (ie the fact that it was marked DONE yesterday). As far as I know you can't do that. When you mark a repeating task done it just reschedules to the future and there is no viewable log in the agenda that you did it previously (unless you clock time against it) -Bernt Sorry, I misunderstood the question. Yes, as far as I'm aware, the DONE lines don't show up in the log. Yes, that's what I meant. As Bernt suggested, I imagine you could write a function to clock the items when you switch them to done. That way they'd show up in the log. Thanks for both of you for suggesting the use of clocked tasks. I did briefly consider it, but I think it is too heavy-duty for my current use of Org-mode. I suppose I can always use a keyword search for such lines. It shouldn't be too hard to find a regexp that matches both DONE and the timestamp. -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Including state-changed headings in the agenda
Hi, Let's say I have a repeating task like this: ** TODO Do this SCHEDULED: 2008-10-29 Wed +1w Cycling to a done state will track the done time and increment the scheduled time according to the repeater: ** TODO Do this - State DONE [2008-10-29 Wed 10:44] SCHEDULED: 2008-11-05 Wed +1w How can I display such items in the daily agenda? Turning on log mode will only display CLOSED items, but since the above task is not closed, it doesn't show up. Thanks! -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] possible bug in org-export (LaTeX), again
* On Sun 09:24PM +, 26 Oct 2008, Rainer Thiel ([EMAIL PROTECTED]) wrote: 2008/10/26 Sebastian Rose [EMAIL PROTECTED]: I can reproduce thit here. Text is inserted into the LaTeX file (`C-c C-e l') or buffer (`C-c C-e L') twice. Thank you for confirming it, Sebastian. You may already have figured out a work-around, but here's I do: - use org-narrow-to-subtree (C-x n s) - put an blank first line in the narrowed view - export Since there is no active region, this bug is not triggered. I am sure Carsten Dominik will take care of it when he finds the time. Carsten made an appeal for someone else to take over the org-export-latex.el module, since the original author Bastien doesn't have time to work on it. I appreciate the LaTeX functionality in Org-mode, and I sure wish I could contribute to that module directly, but I am more knowledgeable in TeX/LaTeX than elisp. Thanks again Rainer -- Prof. Dr. Rainer Thiel Institut für Altertumswissenschaften 07737 Jena, Germany (EU) [EMAIL PROTECTED] ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode -- Best, Hsiu-Khuern. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] LaTeX export gives extra lines between table of contents and first section
* On Fri 01:04AM +, 03 Oct 2008, Tang, Hsiu-Khuern ([EMAIL PROTECTED])
wrote:
I'm new to Org-Mode, and I'm getting to like it a lot!
I am running Org 6.07b. I have this simple Org file:
* top level
** second level
test
If I run M-x org-export-region-as-latex, I get this output:
Sorry, I meant M-x org-export-as-latex here. I've narrowed this down to
the following behavior: with the above input file, the exported LaTeX is:
% standard preamble
\title{* top level}
\author{Tang Hsiu Khuern}
\date{03 October 2008}
\begin{document}
\maketitle
\setcounter{tocdepth}{3}
\tableofcontents
** second level
test
\section{second level}
test
\end{document}
Here, the first heading is used for the title, as documented in 12.7.1
LaTeX export command. (That description is perhaps inaccurate, since
it suggests that this only happens if there is an active region.)
If I suppress this by add the option #+TITLE: my title, I get this
output, without the extra lines:
% standard preamble
\title{my title}
\author{Tang Hsiu Khuern}
\date{03 October 2008}
\begin{document}
\maketitle
\setcounter{tocdepth}{3}
\tableofcontents
\section{top level}
\subsection{second level}
test
\end{document}
I also get output without extra lines if, instead of setting #+TITLE
explicitly, I give a dummy heading to be used as the title:
* my title
* something else
** second level
test
* top level
** second level
test
So it seems like something undesirable happens when org-export-as-latex
needs to use the heading name as the title, _and_ the next section is a
subheading.
--
Best,
Hsiu-Khuern.
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
