Re: [O] Displaying property values in agenda search result

Markus Heller writes: > Hello, > > how can I display property values in the agenda, more specifically, in > the results of an agenda search? > > [...] > > I search using the following in my .emacs as part of a custom agenda > command: > > ("i" "Text here" tags "CATEGORY=\"foo\"" >

Re: [O] Problem with src_ruby inline code and []

On Tue, 15 Mar 2016, William Denton wrote: I was updating and exporting a file where I use Ruby to do some basic arithmetic on tables, and noticed that inline code blocks where I reference an array aren't working. ECM: src_ruby[:var t=sampletable]{t[2][2]} #+BEGIN_SRC emacs-lisp

Re: [O] Displaying property values in agenda search result

Herbert Sitz gmail.com> writes: > > Markus Heller gmail.com> writes: > > > > > Hello, > > > > how can I display property values in the agenda, more specifically, in > > the results of an agenda search? > > > > I think the straigtforward way would be to use column view, and set up your

Re: [O] [PATCH] call_*() is not working inside #+DATE

* Nicolas Goaziou [2016-03-15 19:50]: The problem is that the documentation patch is (partly) wrong. From maint, you can try calling `org-babel-execute-buffer' in the following document #+DATE: src_emacs-lisp{(+ 1 1)} It is possible to evaluate code snippets in

Re: [O] org-agenda error

Unfortunately, that's not the case (that helm-org-in-buffer-headings) is called in a non-org buffer. It happens whenever I call it from within any org-file. I also tried calling it from within a short, minimal org-file with just a few headings of various levels, and I get the same error. The

[O] Problem in customizing org-agenda-custom-commands

Hi, list, I'm trying to customize org-agenda-custom-commands like following: (setq org-agenda-custom-commands `(("rm" "Week in review" agenda "" ((org-agenda-span 'week) (org-agenda-start-on-weekday 0) (org-agenda-overriding-header "Week in Review"))

Re: [O] org-agenda error

Update: I fixed the org-agenda problem. Turns out the problem was that I'd created my own custom defun called org-today, and it was interfering with org-agenda. The helm-org-in-buffer-headings error is still occurring. Thanks for any thoughts. On Tue, Mar 15, 2016 at 7:58 PM, Peter Salazar

Re: [O] [PATCH] call_*() is not working inside #+DATE

* Nicolas Goaziou [2016-03-14 20:41]: Rafael Laboissiere writes: * Rafael Laboissiere [2016-03-12 08:57]: [snip] I went ahead and committed the patch. I think this is a bit premature, as we're still discussing

Re: [O] org-collector - propview display problems

Many thanks, I am going to use org-collector again. It would be great if org-collector could implement kind of regular expression in the research of string. For example with the example provides for org-collector something like :conds ((string= SPENDTYPE "health|food")) to look for health or

Re: [O] PATCH: programming language indicators in HTML export

Hi Rasmus, On Tue, 15 Mar 2016 15:24:00 +0100 Rasmus wrote: [rest deleted] > Robert, do you have a copyright assignment of changes to Emacs? I > think the change is too long (in line count) for a TINYCHANGE. I signed the FSF papers in April 2015. On top of the sheet there is

[O] convert a mailbox or a vm folder to a org-mode file

Hello Does somebody know a tool which would allow to convert a (unix) mailbox or a vm folder to the org-mode format? Thanks Uwe Brauer

Re: [O] PATCH: programming language indicators in HTML export

Hi Robert, Robert Klein writes: >> The patch would make the default html header a bit longer, which may >> or may not be an issue. Perhaps more importantly, it also does not >> deal with new languages. Maybe it would be possible to add a bit of >> JS that would look up the

[O] OS X quick-access to Emacs

Hi Lists, Cross-post to Org and mu4e because Org and mu4e are my primary uses of Emacs. I've created a BitBar plugin for quick-access to Emacs, such as a new *scratch* buffer or a new "Compose Email" buffer. I thought these might be useful to others, hence this post. 1) Download and install

Re: [O] Org is exporting to tex an asterisk between "section" and "{"

Dear Eric. > [...] >> Being a total newbie I can't say that the resulting syntax is incorrect >> (is it?), but at least in the case of latex, *not expressing this >> specific option creates a non-functional latex file*. [...] > The * between section and the brace indicates an unnumbered section

Re: [O] Org is exporting to tex an asterisk between "section" and "{"

On Tuesday, 15 Mar 2016 at 13:07, Eduardo Mercovich wrote: [...] > It is exactly as you said, valid. However, and I may be getting > something else incorrectly, pdflatex has problems with those as it works > out of the box (C-c C-e l o in org), since internal links are broken and > the ToC is

Re: [O] convert a mailbox or a vm folder to a org-mode file

On Tuesday, 15 Mar 2016 at 14:27, Uwe Brauer wrote: > Hello > > > Does somebody know a tool which would allow to convert a (unix) mailbox > or a vm folder to the org-mode format? The power of org is that "it's all text"... A regex based replace would do the job if you simply want to make all

Re: [O] Displaying property values in agenda search result

Markus Heller gmail.com> writes: > > Hello, > > how can I display property values in the agenda, more specifically, in > the results of an agenda search? > I think the straigtforward way would be to use column view, and set up your column view to show, in your case, the PROJECT property.

[O] Problem with src_ruby inline code and []

I was updating and exporting a file where I use Ruby to do some basic arithmetic on tables, and noticed that inline code blocks where I reference an array aren't working. If you C-c C-c on this simple src_ruby example you get the results. src_ruby{1 + 2} {{{results(=3=)}}} But this doesn't

Re: [O] Org is exporting to tex an asterisk between "section" and "{"

Dear Nicolas. >> Being a total newbie I can't say that the resulting syntax is incorrect >> (is it?), but at least in the case of latex, *not expressing this >> specific option creates a non-functional latex file*. >> Shouldn't the exporter take care of this? Or at least, never export the >>

[O] org-show-context-detail with ispell

org-show-context-detail works pretty good with isearch, i.e., revealing context when searching in the folded section. But for ispell, it does not reveal the context when checking spelling in the folded section. Are there any ways around that, i.e., revealing temporarily the text that ispell

Re: [O] Help with writing plain list followed by description list [ox-latex]

Ah, found the solution after I RTFM :) *C-h i g (org) Plain lists* "A list ends whenever every item has ended, which means before any line less or equally indented than items at top level. It also ends before two blank lines(5)." Here's the solution:

[O] Help with writing plain list followed by description list [ox-latex]

Hi, I need help on generating a latex export correctly for the case where a description list has to immediately follow a plain list. Below is a MWE that demonstrates the problem and here is a screenshot of the generated PDF ( http://i.imgur.com/FEjN099.png ). Note how the Description list item

Re: [O] [PATCH] call_*() is not working inside #+DATE

Hello, Rafael Laboissiere writes: > Hopefully, a solution will be found soon and the documentation will be > adjusted accordingly. Notice that, in section "Evaluating code > blocks", it is written "It is also possible to evaluate named code > blocks from anywhere […]".