Re: [O] including files and org-src-preserve-indentation

For the record, attached are the files for the ECM I used to test. -L On Fri, Feb 20, 2015 at 07:27:18PM -0800, Linus Arver wrote: > On Sun, Feb 15, 2015 at 06:36:29PM +0100, Nicolas Goaziou wrote: > > Hello, > > > > Linus Arver writes: > > > > >> When I call org-publish-current-project, the i

Re: [O] including files and org-src-preserve-indentation

On Sun, Feb 15, 2015 at 06:36:29PM +0100, Nicolas Goaziou wrote: > Hello, > > Linus Arver writes: > > >> When I call org-publish-current-project, the included file's TAB > >> characters automatically become converted into spaces. Is there an > >> orgmode way of preventing this auto-conversion? >

Re: [O] Citation syntax: a revised proposal

Hi Samuel, Samuel Wales writes: > basically, i am concerned about syntax creep in the big picture and > its downstream consequences. for example, it's more efficient to > support, and for the user to remember, a single general syntax than a > whole bunch of special syntaxes. In general, I shar

Re: [O] Org agenda time table formatting reverses when loading zenburn theme

Claudius Mueller writes: if I load a theme (such as zenburn) and then rebuild my agenda - the time table has changed: (i) the sorting of time is reversed, and (ii) tasks that were inline before are now sorted out of the time table (see arrow in both pictures). I do not use zenburn very often

Re: [O] Citation syntax: a revised proposal

hi rasmus, On 2/20/15, Rasmus wrote: > I think everybody is thinking along the lines, but some people want to not > have another link-morass :) In particular, I think we are trying hard to > avoid this situation: > > i just think the syntax we design should, if possible, be so general > t

Re: [O] Citation syntax: a revised proposal

Samuel Wales writes: > if everybody is already thinking along the same lines, great. I think everybody is thinking along the lines, but some people want to not have another link-morass :) In particular, I think we are trying hard to avoid this situation: i just think the syntax we design sh

Re: [O] Citation syntax: a revised proposal

On 2/20/15, Richard Lawrence wrote: > If there are others (John? Aaron? Samuel?) who think they really need > the {:key val} syntax *over and above* a subtype designation, please > speak up! i have no comments on citations per se. i just think the syntax we design should, if possible, be so gene

Re: [O] [ox, patch] external compilation

Nicolas Goaziou writes: > emacs --batch -Q -l conf.el --visit toexport.org -f org-latex-export-to-pdf That it hardcodes conf.el. So it doesn't toexport1.org which depends on config/conf.el. I want to specify the dependency in in toexport.org explicitly so that emacs --batch -Q --visit

Re: [O] how to get images support in Emacs on Windows?

Ben gmail.com> writes: > > You can download the corresponding dlls from ezwinports [fn:1] and put them into emacs's `bin` directory. > > There are some instructions in the "Image support" part on page [fn:2]. > > [fn:2] https://ftp.gnu.org/gnu/emacs/windows/ > Strangely, the instructions and

Re: [O] [ox, patch] external compilation

Rasmus writes: > How to I generalize this to a emacs --batch call from a random org > file? What's wrong with emacs --batch -Q -l conf.el --visit toexport.org -f org-latex-export-to-pdf Regards,

Re: [O] [ox, patch] external compilation

Nicolas Goaziou writes: >> No this has the same issue as the Makefile. "It's not as easy as latex". > > Setting up a publishing project is easy and well documented. So is Makefile. >> I want *one* coherent file with all the necessary instructions, that can >> be edited in different program fro

Re: [O] [ox, patch] external compilation

Rasmus writes: >> Can't you simply set-up a publishing project? > > No this has the same issue as the Makefile. "It's not as easy as latex". Setting up a publishing project is easy and well documented. > I want *one* coherent file with all the necessary instructions, that can > be edited in di

Re: [O] Citation syntax: a revised proposal

Hi Melanie, Melanie Bacou writes: > Just want to point out RMarkdown/Pandoc implementation of > bibliographies and citations here > http://rmarkdown.rstudio.com/authoring_bibliographies_and_citations.html Thanks for joining the discussion! Actually, the Pandoc/RMarkdown syntax was sort of the

Re: [O] What is Babel's relationship with a Lisp REPL? State or stateless?

Does this answer your question? http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-lisp.html#sec-3-2 I usually set up Scheme and R to keep a single buffer around with Racket or R running in them. I do work in there outside of org just like I do inside of org; figure stuff out and rely on

Re: [O] Citation syntax: a revised proposal

Hi Nicolas, Nicolas Goaziou writes: > AFAICT, the most advanced use of citations is Thomas', and he is > basically only using "subtype". So I'm pretty confident that 99.9% of > users will be fine with only these subtypes. > ... > Again, I don't think we need {:key val} at the moment. Also, it wo

Re: [O] [ox, patch] external compilation

Nicolas Goaziou writes: > Hello, > > Rasmus writes: > >>> Ideally, what I would like would be to specify a per-file/project init >>> file. Sort of like org-export-async-init-file, but as part of >>> org-export-options-alist to get the "init.el-dependency" inside the >>> Org-file. It would be r

Re: [O] [ox, patch] external compilation

Hello, Rasmus writes: >> Ideally, what I would like would be to specify a per-file/project init >> file. Sort of like org-export-async-init-file, but as part of >> org-export-options-alist to get the "init.el-dependency" inside the >> Org-file. It would be read when Org exports async or via ba

Re: [O] What is Babel's relationship with a Lisp REPL? State or stateless?

I think it saves state, and remembers what has been done, at least as long as emacs is open. If you close emacs, it will forget everything, and you would have to rerun each block. You could tangle (or selectively tangle) the blocks out, to get an emacs-lisp file, which might then be a library you w

[O] bug#19887: 24.4; Cannot kill buffer; Wrong type argument: overlayp, nil

> > PMJI, but at > , > > Nicolas Goaziou said "This should be fixed." > > > > Perhaps this bug report can simply be closed then ? > > If it's fixed, please close it. [Damian Nadales] Thanks for the fix. I must add that I discovered the bug by a

[O] What is Babel's relationship with a Lisp REPL? State or stateless?

If I'm creating an org file in a buffer which has source blocks for, say, Lisp, then I can "run" these blocks of Lisp code and Babel will fill in the "answer" just below in my buffer. Good. As advertised. But what is really happening to this code? Does Babel invoke a Lisp REPL once, do the code, pr

[O] bug#19887: 24.4; Cannot kill buffer; Wrong type argument: overlayp, nil

Hi Eli, > > [Damian Nadales] > > That's weird. Which buffer are you killing, the Org buffer, or the new > > buffer > that is created when pressing C-c ' inside the source block? Is the latter the > one I cannot kill. > > There was no "C-c '" in the recipe you posted. > [Damian Nadales] No, it was

[O] [ox, patch] external compilation (was: External compilation)

Rasmus writes: > I can move the call to Emacs as file variable s.t. > > # Local Variables: > # eval: (unless (or user-init-file (window-system)) (load-file > "conf.el")) > # End: A much better variable to check is `noninteractive', cf (info "(elisp) Batch mode"). > Ideally, what

[O] bug#19887: 24.4; Cannot kill buffer; Wrong type argument: overlayp, nil

> From: Nicolas Richard > Cc: Damian Nadales , 19...@debbugs.gnu.org, Nicolas > Goaziou > Date: Fri, 20 Feb 2015 12:20:15 +0100 > > Eli Zaretskii writes: > >> From: Damian Nadales > >> That's weird. Which buffer are you killing, the Org buffer, or the > >> new buffer that is created when pre

[O] bug#19887: 24.4; Cannot kill buffer; Wrong type argument: overlayp, nil

Eli Zaretskii writes: >> From: Damian Nadales >> That's weird. Which buffer are you killing, the Org buffer, or the >> new buffer that is created when pressing C-c ' inside the source >> block? Is the latter the one I cannot kill. > > There was no "C-c '" in the recipe you posted. > > What is the

Re: [O] [patch] better(?) indention for cdlatex-environment

Rasmus writes: > What is the rational behind "Org 8.3 has Emacs 23 support; Org 8.4 does > not". I'm just trying to understand. . . Easy: 8.3 ends with a 3, like Emacs 23... Org 8.3 is close from being released. It started with Emacs 23 support, a long time ago, so it would make little sense t

Re: [O] [patch] better(?) indention for cdlatex-environment

Nicolas Goaziou writes: > Org 8.4 will drop support for Emacs 23, i.e., as soon as Org 8.3 is > released, we can activate lexical binding on master. What is the rational behind "Org 8.3 has Emacs 23 support; Org 8.4 does not". I'm just trying to understand. . . —Rasmus -- Vote for proprietar

Re: [O] [patch] better(?) indention for cdlatex-environment

Rasmus writes: >>> (define-obsolete-function-alias >>> 'show-all 'outline-show-all "25.1") >> >> Ah right. That's the same idea. Functions without a namespace are being >> renamed. > > My Debian Squeeze VM has 23.4.1. ^^ Wheezy that is Actually, Debian 7.8 has a Emacs 2

Re: [O] [patch] better(?) indention for cdlatex-environment

Rasmus writes: > So when can we target Emacs 24? Jessie? My Debian Squeeze VM has 23.4.1. > CentOS 7 is already on Emacs 24.3. Org 8.4 will drop support for Emacs 23, i.e., as soon as Org 8.3 is released, we can activate lexical binding on master. Regards,

Re: [O] [patch] better(?) indention for cdlatex-environment

Nicolas Goaziou writes: > Rasmus writes: > >> The think that comes to mind is `show-all'. In my Emacs: >> >> (define-obsolete-function-alias >> 'show-all 'outline-show-all "25.1") > > Ah right. That's the same idea. Functions without a namespace are being > renamed. Good riddance.

Re: [O] [patch] better(?) indention for cdlatex-environment

Rasmus writes: > The think that comes to mind is `show-all'. In my Emacs: > > (define-obsolete-function-alias > 'show-all 'outline-show-all "25.1") Ah right. That's the same idea. Functions without a namespace are being renamed. Regards,

[O] bug#19887: 24.4; Cannot kill buffer; Wrong type argument: overlayp, nil

> From: Damian Nadales > CC: "19...@debbugs.gnu.org" <19...@debbugs.gnu.org> > Date: Fri, 20 Feb 2015 07:32:12 + > > > I cannot reproduce this. I tried both Emacs 24.4 and the pretest of 24.5. > > In > > both cases, Emacs asks me whether to kill a buffer that is modified, and > > once > >

Re: [O] [BUG] org-clock-display is partial (only some entries are counted)

Sebastien Vauban writes: > I still consider the default behavior as dangerous -- because the novice > is not aware (except if obvious) that some clock times may be dropped in > the computation, and I find that scary --, but thanks anyway for the > workaround. Would you mind testing the following

Re: [O] [patch] better(?) indention for cdlatex-environment

Nicolas Goaziou writes: > What do you mean by "outline prefixes"? The think that comes to mind is `show-all'. In my Emacs: (define-obsolete-function-alias 'show-all 'outline-show-all "25.1") —Rasmus -- There are known knowns; there are things we know that we know

Re: [O] ox-html: stand-alone export option?

Melanie Bacou writes: > You're right with Github or remote storages there's no problem (links > to images like `./fig/my_fig.png` or local CSS or JS > `./css/my_css_.css` are interpreted as usual. The problem is only on > cloud storage services like Dropbox where each resource gets a unique > (un

Re: [O] [patch] better(?) indention for cdlatex-environment

Rasmus writes: > PS: Is that also why the outline prefixes are being added? It complains > about it when you compile org. What do you mean by "outline prefixes"? Regards,

Re: [O] bug#19887: 24.4; Cannot kill buffer; Wrong type argument: overlayp, nil

On 2015-02-20T18:32:12+1100, Damian Nadales said: DN> That's weird. Which buffer are you killing, the DN> Org buffer, or the new buffer that is created when pressing C-c ' DN> inside the source block? Is the latter the one I cannot kill. DN> I've only installed packages through the emacs DN>