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 =

Re: [O] Export a Subtree to an other .org file

* On Thu 03:13PM, 04 Apr 2013, Bastien (b...@altern.org) wrote: > Nicolas Goaziou 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 -- t

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 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

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 > >

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.

[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 -

[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 Seco

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 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 t

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 wrote: > > > Hi, > > > > Sorry if this has been reported -- a brief search didn't turn up anything. > >

[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 '

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 wrote: > Eric S Fraga 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 situatio

[O] Bug in selective export when selected heading follows excluded heading

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

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 wrote: > Hsiu-Khuern Tang 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: >&

[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 origi

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

[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 ent

[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}[]

[O] Re: [FIXED] Re: :latex-listings publishing option not used; minted + beamer incompatibility?

On Mon, Feb 14, 2011 at 3:15 AM, Dan Davison wrote: > Hsiu-Khuern Tang writes: > >> Hi Dan, >> >> * On Wed 09:09AM, 20 Oct 2010, Dan Davison (davi...@stats.ox.ac.uk) wrote: >>> Hsiu-Khuern Tang writes: >>> > BTW, has anyone used minted with beam

Re: [O] Re: [Orgmode] [PATCH] Allow inclusion of author's email in LaTeX export

On Tue, Mar 1, 2011 at 9:36 AM, Bastien wrote: > Hi Hsiu-Khuern, > > Hsiu-Khuern Tang 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.

[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 wrote: > Hsiu-Khuern Tang 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 or

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 A

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 wrote: > Did you try un

[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

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: * Es

[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 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

[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,

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 wrote: > This issue should now be fixed. > > Best -- Eric ___ Emacs-orgmode mailing list Please use `Re

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 (efdf78172d9f7c

[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 see

Re: [Orgmode] Wishlist: indicate language in LaTeX export of literal source examples

> > 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 writes: > >> (Resending because o

[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., #+BE

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

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 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 w

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

[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 "sy

Re: [Orgmode] dvipng: -E is not a valid option

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 >

[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-o

[Orgmode] Nitpick: Exporting/publishing to org in the same directory gives file.org-source instead of file-source.org

Hi all, The footnote at the bottom of section 13.1.4 ("Publishing action") of the Org manual says that publishing org files to the same directory using org-publish-org-to-org results in files named like file-source.org. It actually results in file.org-source, which is not as nice. I believe the

Re: [Orgmode] Re: Export to org?

* On Thu 12:41AM +, 30 Jul 2009, Bernt Hansen (be...@norang.ca) wrote: > Hsiu-Khuern Tang writes: > > > Hi, > > > > Is there an easy way to export an org file to another org file, stripping > > away > > any subtrees that are tagged "noexport&quo

[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 exampl

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 #. > > Pl

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" 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 block, which is > > ni

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 > in

[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 th

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: > > > H

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:

[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

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 "arti

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 > > > > g

[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. -- Be

[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.

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

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

Re: [Orgmode] Searching SCHEDULED/DEADLINE properties turns up spurious headings

ou can see from > the highlighted stars. When I run that search (C-c \ +DEADLINE<="<2009-01-28>" ), 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:

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 s

[Orgmode] Searching SCHEDULED/DEADLINE properties turns up spurious headings

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-

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 > "CU

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 > > current

[Orgmode] Does secondary filtering allow multiple tags?

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. I am

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: &l

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

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

[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-

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 ma

Re: [Orgmode] LaTeX export gives extra lines between table of contents and first section

* On Fri 09:13PM +, 10 Oct 2008, Carsten Dominik ([EMAIL PROTECTED]) wrote: > Hi Hsiu, > > looks like there is a bug in the LaTeX exporter when > the very first line of the file is already a headline. > I do not right now see an easy way to fix this, and Bastien > does not seem to have time.

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 > ---

[Orgmode] LaTeX export gives extra lines between table of contents and first section

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: ---