Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
-
Hi,
I'm having trouble getting clean output from org 8.2.5 when I combine
session based evaluation and capturing results from standard out. (See
first example below)
This is on Emacs 24.3 with the default python mode settings and
nothing relevant in my init.el except for activating python support
On Tue, Mar 4, 2014 at 3:45 PM, Simon Thum wrote:
> This seems to be a question of objective. Do you want to encode, i.e.
> maintain some reversible original in an url no matter what, or do you want
> to fix url's which wouldn't otherwise be legal? In the latter case, the
> question mark should pr
Hello,
I'm creating a new org file today and I'm using work estimates that use
day(d) and week(w) modifiers. Specifically, I have the following defined:
#+PROPERTY: Effort_ALL 0 1:00 4:00 1d 2d 1w 2w
#+COLUMNS: %40ITEM(Task) %17Effort(Estimated Effort){:} %CLOCKSUM
The problem I'm having is with
Thanks Aaron:
http://orgmode.org/manual/noweb_002dref.html
On Wed, Mar 5, 2014 at 4:41 PM, Aaron Ecay wrote:
> Hi Grant,
>
> I think you can do this with the noweb-ref property/header arg. There’s
> an example very similar (if not identical) to your use case in the info
> manual, node “(org)
Aha, I see you found it too. I should run fetchmail more
frequently...sorry for the noise.
2014ko martxoak 5an, Aaron Ecay-ek idatzi zuen:
>
> Hi Grant,
>
> I think you can do this with the noweb-ref property/header arg. There’s
> an example very similar (if not identical) to your use case in th
Hi Grant,
I think you can do this with the noweb-ref property/header arg. There’s
an example very similar (if not identical) to your use case in the info
manual, node “(org) noweb-ref”
--
Aaron Ecay
Here is what I was looking for:
http://orgmode.org/manual/noweb_002dref.html
*** Windows [fn:39]
:PROPERTIES:
:noweb-ref: uxo-decision
:END:
Menu bars are not required [fn:38]
#+BEGIN_SRC emacs-lisp
(menu-bar-mode 0)
#+END_SRC
On Wed, Mar 5, 2014 at 4:24 PM, Grant Rettke wrote:
> E
Exactly I'm doing a
#+BEGIN_SRC emacs-lisp :tangle .emacs.el :noweb tangle
What I'm aiming for is the case where you have lots of code blocks
interspersed
with written language... and want them to accumulate under a single
identifier. I will keep
digging.
On Wed, Mar 5, 2014 at 3:39 PM, Thomas
Yup I'm using noweb references.
On Wed, Mar 5, 2014 at 3:35 PM, Samuel Wales wrote:
> noweb?
>
> --
> The Kafka Pandemic: http://thekafkapandemic.blogspot.com
>
> The disease DOES progress. MANY people have died from it. And
> ANYBODY can get it.
>
> Denmark: free Karina Hansen NOW.
>
--
Nicolas Richard writes:
> I don't know if speed is terribly important here, but since my suggested
> approach uses a loop instead of recursion, it ends up being faster for
> nested headlines (more than 5 levels). This obviously could be fixed in
> the initial approach too.
>
> Since we know where
Hi Nicolas,
Nicolas Goaziou writes:
> Of course, `org-element-at-point' can parse headlines, but if speed is
> a factor, since headline syntax is not context-dependent, it is often
> worth considering using regexps.
I don't know if speed is terribly important here, but since my suggested
approac
Hi Nicolas,
Nicolas Goaziou writes:
> Of course, `org-element-at-point' can parse headlines, but if speed is
> a factor, since headline syntax is not context-dependent, it is often
> worth considering using regexps.
I don't know if speed is terribly important here, but since my suggested
approac
Sharon Kimble writes:
> Can the google calendar work with org-mode agenda please? I haven't
> seen any indication that it can be done when I've been googling around.
> But I thought that I would ask anyway.
Synchronization is not seamless, but it can be accomplished with some
setup. See:
http:
Aloha Grant,
I'm not certain what you're after.
>From the Org mode manual:
* outline header
:PROPERTIES:
:header-args::cache yes
:END:
Perhaps
:header-args: :tangle myfile.el
All the best,
Tom
Grant Rettke writes:
> Hi,
>
> My goal is to intersperse code blo
noweb?
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
The disease DOES progress. MANY people have died from it. And
ANYBODY can get it.
Denmark: free Karina Hansen NOW.
Some questions about inline source code blocks:
- They're not fontified even when org-src-fontify-natively is true
-- correct?
- They're not included in tangled code; is that intended behavior?
The manual does not seem to say they're different from normal code
blocks, except for syntax.
T
Hi,
My goal is to intersperse code blocks with comments about them like this:
==
Menu bars are not required [fn:38]
#+NAME: uxo-decision1
#+BEGIN_SRC emacs-lisp
(menu-bar-mode 0)
#+END_SRC
Don't need auto-save
#+NAME: uxo-decision2
#+BEGIN_SRC emacs-lisp
(disable-
Bastien writes:
> Hi Stefan,
>
> Stefan Huchler writes:
>
>> The Problem is that that org-mode seems to auto-format the salary column
>> as a number.
>
> That a problem here, but I guess this is handy in many circumstances.
>
> Why don't use just turn the number into a string in your code?
if I
Can the google calendar work with org-mode agenda please? I haven't
seen any indication that it can be done when I've been googling around.
But I thought that I would ask anyway.
And on the same tack, can google tasks work with org-modes TODO lists
please?
Thanks
Sharon.
--
A taste of linux =
Hi Nicolas
On Wed, Mar 5, 2014 at 8:11 PM, Nicolas Goaziou wrote:
> This should be fixed. Thanks to both of you for reporting it.
It works, thank you.
Michael
Hello,
Michael Brand writes:
> On Tue, Mar 4, 2014 at 8:58 PM, Matt Lundin wrote:
>> I suspect this is related the bug I reported earlier today:
>>
>> http://permalink.gmane.org/gmane.emacs.orgmode/82979
>
> I guess the same bug. I have overseen your report.
This should be fixed. Thanks to bot
Hello,
Nicolas Richard writes:
> I take the opportuinty to ask if we should try and make this function
> use org-element instead.
>
> My naïve approach doesn't work:
>
> #+begin_src emacs-lisp
> (save-excursion
> (org-back-to-heading t)
> (let ((elt (org-element-at-point)))
> (wh
Bastien writes:
> Hi Nicolas,
>
> Nicolas Richard writes:
>
>> OTOH, I find it a bad idea that some arguments are ignored in
>> non-interactive uses, it'd be better to have a function which fully
>> obeys its arguments, and has an interactive spec which sets the
>> argument. If you're interested
Hi Nicolas,
Nicolas Richard writes:
> OTOH, I find it a bad idea that some arguments are ignored in
> non-interactive uses, it'd be better to have a function which fully
> obeys its arguments, and has an interactive spec which sets the
> argument. If you're interested I can do that.
Of course I
Hi Rasmus
Have you tried ox-koma-letter.el?
>
>
not yet, I just started recently switching back to latex and g-brief did
what I needed for a formal german letter and I just need it once per month
so far.
> #+TITLE: title
>
> #+BEGIN_g-brief
> ... here comes text
> #+END_g-brief
>
OK thanks, I t
Hello,
"elisp" (vs "emacs-lisp") code blocks are supported via an entry
"org-src-lang-modes" but not in org-babel-tangle-lang-exts.
The patch below is to fix that.
From: Nicolas Richard
Date: Wed, 5 Mar 2014 16:49:30 +0100
Subject: [PATCH] lisp/ob-tangle.el: "elisp" should get tangled to ".el"
Hi,
Trying to tangle code blocks in a headline line like:
#+begin_src org
,* Comment retrouver
#+end_src
I struggled to understand what I was doing wrong because it didn't
tangle anything. In fact, the french word "Comment" was mistakenly
parsed as the org-comment-string, and so the headline
Bastien writes:
> Daimrod writes:
>
>> Awww that's tricky, M-x org-version doesn't have the same behavior than
>> M-: (org-version)
>
> That's on purpose: (org-version) is what you want to call in a
> program, hence the short version, while M-x org-version RET is what
> you want to call interact
Nicolas Goaziou writes:
> I always do:
>
> make && org-reload
>
> from Eshell. That doesn't change anything.
Please do
~$ git fetch --tags
to update all your tags, and make again.
>> I always add the release tag on maint, that's where both minor and
>> major releases are made from (expect t
Bastien writes:
> Daimrod writes:
>
>> Awww that's tricky, M-x org-version doesn't have the same behavior than
>> M-: (org-version)
>
> That's on purpose: (org-version) is what you want to call in a
> program, hence the short version, while M-x org-version RET is what
> you want to call interact
Bastien writes:
> Well, make sure you did a ~$ make or ~$ make autoloads so that
> lisp/org-version.el is correct.
I always do:
make && org-reload
from Eshell. That doesn't change anything.
> I always add the release tag on maint, that's where both minor and
> major releases are made from (
Hi Stefan,
Stefan Huchler writes:
> The Problem is that that org-mode seems to auto-format the salary column
> as a number.
That a problem here, but I guess this is handy in many circumstances.
Why don't use just turn the number into a string in your code?
--
Bastien
Daimrod writes:
> Awww that's tricky, M-x org-version doesn't have the same behavior than
> M-: (org-version)
That's on purpose: (org-version) is what you want to call in a
program, hence the short version, while M-x org-version RET is what
you want to call interactively (hence the longer one.)
Hi Nicolas,
Nicolas Goaziou writes:
> Good question. I have absolutely no clue. OTOH, my tree looks
> up-to-date, and my .git/config reports:
>
> [remote "origin"]
> fetch = +refs/heads/*:refs/remotes/origin/*
> url = orgm...@orgmode.org:org-mode.git
>
Daimrod writes:
> Nicolas Goaziou writes:
>
>> Daimrod writes:
>>
>>> I had forgotten to rerun make after I pulled the latest version.
>>> `org-version' now returns "8.2.5h".
>>
>> This is still not right. 8.2.5h refers to "maint" branch, where cache
>> doesn't exist.
>>
>> When I compile the l
Hello,
Bastien writes:
> Mhh... now *I* am confused. The latest release on master is
>
> Org-mode version 8.2.5h (release_8.2.5h-676-gfb8a04)
>
> How can it be 8.2.5e for you?
Good question. I have absolutely no clue. OTOH, my tree looks
up-to-date, and my .git/config reports:
[remo
Bastien writes:
> Hi Nicolas and Greg,
>
> Nicolas Goaziou writes:
>
>> Daimrod writes:
>>
>>> I had forgotten to rerun make after I pulled the latest version.
>>> `org-version' now returns "8.2.5h".
>>
>> This is still not right. 8.2.5h refers to "maint" branch, where cache
>> doesn't exist.
>
Nicolas Goaziou writes:
> Daimrod writes:
>
>> I had forgotten to rerun make after I pulled the latest version.
>> `org-version' now returns "8.2.5h".
>
> This is still not right. 8.2.5h refers to "maint" branch, where cache
> doesn't exist.
>
> When I compile the latest release on "master", I g
Hello Nicolas
On 5 March 2014 09:25, Nicolas Goaziou wrote:
> Daimrod writes:
>
> > I had forgotten to rerun make after I pulled the latest version.
> > `org-version' now returns "8.2.5h".
>
> This is still not right. 8.2.5h refers to "maint" branch, where cache
> doesn't exist.
>
> When I comp
Hi Nicolas and Greg,
Nicolas Goaziou writes:
> Daimrod writes:
>
>> I had forgotten to rerun make after I pulled the latest version.
>> `org-version' now returns "8.2.5h".
>
> This is still not right. 8.2.5h refers to "maint" branch, where cache
> doesn't exist.
I think Greg did C-h v org-vers
Daimrod writes:
> I had forgotten to rerun make after I pulled the latest version.
> `org-version' now returns "8.2.5h".
This is still not right. 8.2.5h refers to "maint" branch, where cache
doesn't exist.
When I compile the latest release on "master", I get:
Org-mode version 8.2.5e (release
Nicolas Goaziou writes:
> Hello,
>
> Daimrod writes:
>
>> I use org-mode version release_8.0.2-101-gce5988 (I follow the git
>> upstream) and I tried it with `org-element-use-cache' set to nil.
>
> There was no `org-element-use-cache' in Org 8.0. Could you update Org
> and try again?
I had forg
Hello,
Daimrod writes:
> I use org-mode version release_8.0.2-101-gce5988 (I follow the git
> upstream) and I tried it with `org-element-use-cache' set to nil.
There was no `org-element-use-cache' in Org 8.0. Could you update Org
and try again?
Regards,
--
Nicolas Goaziou
Nicolas Goaziou writes:
> Hello,
>
> Daimrod writes:
>
>> I think that there is a bug in `org-element-context' because it doesn't
>> seem to parse link with spaces consistently.
>>
>> For example:
>>
>> #+BEGIN_EXAMPLE
>> v
>> [[file:test 1 2 3]]
>> ^
>> #+END_EXAMPLE
>>
Nicolas Goaziou writes:
> Hello,
>
> Daimrod writes:
>
>> I think that since its recent rewrite, `org-open-at-point' adds 'file+'
>> before the name of the application before trying to find the correct
>> application.
>>
>> For example the following link:
>>
>> #+BEGIN_EXAMPLE
>> [[docview:foo.p
On Wed, 05 Mar 2014 07:15:07 -0500
Nick Dokos wrote:
> Sharon Kimble writes:
>
> > After spending some time on it, I've just exported the article to my
> > blog using 'org2blog' and looking at the preview of the post, I see
> > that what I know of as 'references', headed that in the original, i
Hello,
Daimrod writes:
> I think that there is a bug in `org-element-context' because it doesn't
> seem to parse link with spaces consistently.
>
> For example:
>
> #+BEGIN_EXAMPLE
> v
> [[file:test 1 2 3]]
> ^
> #+END_EXAMPLE
>
> If the cursor is before the '1', then `or
Hello,
Daimrod writes:
> I think that since its recent rewrite, `org-open-at-point' adds 'file+'
> before the name of the application before trying to find the correct
> application.
>
> For example the following link:
>
> #+BEGIN_EXAMPLE
> [[docview:foo.pdf]]
> #+END_EXAMPLE
>
> won't trigger t
Very interesting... thank you, Rasmus!
Indeed Consolas, the font I was using, doesn't have the check mark unicode
character (U+2713). Switching to DejaVu Sans Mono solved the problem.
Giacomo
On Wed, Mar 5, 2014 at 1:01 PM, Rasmus wrote:
> Giacomo M writes:
>
> > Dear all,
> > nothing of cruc
Sharon Kimble writes:
> After spending some time on it, I've just exported the article to my
> blog using 'org2blog' and looking at the preview of the post, I see
> that what I know of as 'references', headed that in the original, is
> showing as 'Footnotes', although there is already a section [
Michael Brand writes:
> On Wed, Mar 5, 2014 at 4:39 AM, Nick Dokos wrote:
>> Since this is the third time in as many weeks that somebody brings this
>> exact problem up, this probably qualifies as a FAQ. But before going
>> there, is there *any* reason to forbid quotes in the border? IOW, maybe
Giacomo M writes:
> Dear all,
> nothing of crucial importance for the sake of humanity, but when I realign
> (C-c C-c) the following table:
>
> | entry1 | \check |
> | entry2 | X |
>
> with pretty-entities toggled (C-c C-x \), columns are not perfectly aligned.
Probably you are using different f
Dear all,
nothing of crucial importance for the sake of humanity, but when I realign
(C-c C-c) the following table:
| entry1 | \check |
| entry2 | X |
with pretty-entities toggled (C-c C-x \), columns are not perfectly aligned.
My setup:
Emacs 24.3.1 (i386-mingw-nt6.1.7601)
Org-mode 8.2.5h (8.2.
On Sat, 01 Mar 2014 15:03:55 -0500
Nick Dokos wrote:
> Sharon Kimble writes:
>
> > On Sat, 01 Mar 2014 13:22:45 -0500
> > Nick Dokos wrote:
> >
> >> Sharon Kimble writes:
> >>
> >> > I'm using [fn:1] to reference articles in an academic article,
> >> > but how should I reference it back from
Hi Nick
On Wed, Mar 5, 2014 at 4:39 AM, Nick Dokos wrote:
> Since this is the third time in as many weeks that somebody brings this
> exact problem up, this probably qualifies as a FAQ. But before going
> there, is there *any* reason to forbid quotes in the border? IOW, maybe
> it's a better idea
LanX writes:
> Hi
>
> Im using a latex class called g-brief to create formal german letters (see
> e.g. http://vimpy.org/wp/archives/47) and I'm trying to add an exporter to
> org-mode.
Have you tried ox-koma-letter.el?
> my problem is that I need to enclose the text within
>
> \begin{document
Hi Nick,
Nick Dokos writes:
> Since this is the third time in as many weeks that somebody brings this
> exact problem up, this probably qualifies as a FAQ. But before going
> there, is there *any* reason to forbid quotes in the border? IOW, maybe
> it's a better idea to change the default value
58 matches
Mail list logo
