2014-06-10 19:54 GMT+02:00 Grant Rettke :
> On Tue, Jun 10, 2014 at 9:46 AM, Nicolas Girard
> wrote:
>>
>> - About =org-babel-use-quick-and-dirty-noweb-expansion=:
>> should it be set to 't' by default ? I'd be tempted to say yes,
>> given the dramatic performance gain
> Use Emacs to run Emacs
Nick Dokos gmail.com> writes:
> `C-c C-x c' (`org-clone-subtree-with-time-shift')
Thanks. This looks like the best solution.
Daimrod writes:
> Nicolas Goaziou writes:
>
>> Hello,
>>
>> Daimrod writes:
>>
>>> I've attached part of the traces (the whole traces are way too big) and
>>> the backtraces.
>>
>> Thanks for looking into this. However, you are running a compiled Org,
>> which renders backtraces less useful.
>
Hallo John,
On 10 June 2014 23:27, John Hendy wrote:
> More information would be helpful. There is a setup procedure from the
> Emacs/Org side, and also from the Mobile-Org side. What, for example,
> did you do for the steps described here?
- http://orgmode.org/manual/MobileOrg.html
>
I will d
Works for me, see example below
#+BEGIN_SRC python :results output :session foo
x=100
print "hello"
2
print "bye"
#+END_SRC
#+RESULTS:
:
: >>> hello
: 2
: bye
#+BEGIN_SRC python :results output :session foo
print "hello good bye"
print "Printing value from previous session", x
#+END_SRC
#+RES
I use the following to include once-off events in my Agenda:
--8<---cut here---start->8---
* Once-Off Task
<2014-06-11 Wed 09:00>
--8<---cut here---end--->8---
What is the difference (benefit) to rather doing this:
--8<
SabreWolfy writes:
> I use the following to include once-off events in my Agenda:
>
> * Once-Off Task
> <2014-06-11 Wed 09:00>
>
>
> What is the difference (benefit) to rather doing this:
>
> * TODO Once-Off Task
> <2014-06-11 Wed 09:00>
>
> The second method gives me a red "TODO" in the Agenda a
I'm on:
Emacs version: GNU Emacs 24.3.1 (x86_64-apple-darwin13.1.0, NS
apple-appkit-1265.19)
of 2014-04-24 on orion
Org version: 8.2.6
java version "1.8.0_05"
Java(TM) SE Runtime Environment (build 1.8.0_05-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.5-b02, mixed mode)
ditaa0_9.jar
And org-b
Understood.
The quick and dirty approach removes the ability for headings to
inherit the noweb properties of, and override, the properties of its
parent header.
That feature enables the true literate programming to remove it would
be a great loss.
Grant Rettke | AAAS, ACM, ASA, FSF, IEEE, SIAM, S
Nicolas Richard writes:
> David Griffiths writes:
>> Debugger entered--Lisp error: (error "`recenter'ing a window that does
>> not display current-buffer.")
>> recenter((4))
>> org-overview()
>
> So that's a duplicate of #17724. It is fixed in org-mode (upstream) master
> branch. The easy fix is
Bastien writes:
> PS: The change about throwing an error when recentering a window
> that does not display the current buffer breaks ~37 tests in Org
> master branch, even with this fix. I need to digg this further.
For me, fixing also org-fix-ellipsis-at-bol made all tests run as
expected.
--
Nicolas Richard writes:
> Bastien writes:
>> PS: The change about throwing an error when recentering a window
>> that does not display the current buffer breaks ~37 tests in Org
>> master branch, even with this fix. I need to digg this further.
>
> For me, fixing also org-fix-ellipsis-at-bol ma
> From: Bastien
> Date: Wed, 11 Jun 2014 17:50:02 +0200
> Cc: 17...@debbugs.gnu.org, David Griffiths
>
> PS: The change about throwing an error when recentering a window
> that does not display the current buffer breaks ~37 tests in Org
> master branch, even with this fix. I need to digg this f
> Say thanks to Stefan for flagging all those bugs ;-)
Now that I think about it, I should make `car' signal an error every
100th call, as well. Would flag many bugs (with some false positives,
of course, but what's a few false positives among friends?)!
Stefan
> From: Stefan Monnier
> Cc: Bastien , theonewiththeevill...@yahoo.fr,
> 17...@debbugs.gnu.org, dogriffi...@gmail.com
> Date: Wed, 11 Jun 2014 14:15:08 -0400
>
> > Say thanks to Stefan for flagging all those bugs ;-)
>
> Now that I think about it, I should make `car' signal an error every
> 100
Bastien writes:
> Nicolas Richard writes:
>
>> Bastien writes:
>>> PS: The change about throwing an error when recentering a window
>>> that does not display the current buffer breaks ~37 tests in Org
>>> master branch, even with this fix. I need to digg this further.
>>
>> For me, fixing also
hi, all.
if this is out of scope, or likely to be too much of a rat hole, please
let me know (and otherwise ignore).
occasionally, i work on something complicated enough that i feel the
need of using make to manage dependencies, allow for cleaning up working
directories (via "make clean" function
On Wed, Jun 11, 2014 at 2:24 PM, Greg Minshall wrote:
> i'm wondering if anyone else, having wrestled with these issues,
Yes.
> has any recipes for some approximation of happiness. or, some totally
> different
> approach i'm too set in my ways to see.
For me it has been the same approach defi
"Charles C. Berry" writes:
> When run with master, after the prompt for evaluating the src block,
> an error is thrown. *Messages* shows
>
> ,
> | Evaluate this emacs-lisp code block on your system? (y or n) y
> | executing Emacs-Lisp code block...
> | Code block evaluation complete.
> | con
Hello,
Daimrod writes:
> Okay, so I've found a more or less reliable way to reproduce this bug (on my
> machine at least).
>
> 1. $ emacs -Q -l debug.el test.org
> 2. Expand headline ()
> 3. go below the first headline (C-n)
> 4. press `i' a couple of seconds ~10 chars
> 5. delete the line (C-a
Hi Rainer,
Rainer M Krug writes:
> Hi
>
> I just realized (again) that tangling with variables in R contains many
> particularities.
>
> 1) it only works with non-tables, i.e. single values.
>
> When defining the following variables:
>
> #+NAME: YEARS
> | | year |
> |---+-
Nicolas Goaziou writes:
> Hello,
>
> Daimrod writes:
>
>> Okay, so I've found a more or less reliable way to reproduce this bug (on my
>> machine at least).
>>
>> 1. $ emacs -Q -l debug.el test.org
>> 2. Expand headline ()
>> 3. go below the first headline (C-n)
>> 4. press `i' a couple of secon
Bastien writes:
> Nicolas Richard writes:
>
>> David Griffiths writes:
>>> Debugger entered--Lisp error: (error "`recenter'ing a window that does
>>> not display current-buffer.")
>>> recenter((4))
>>> org-overview()
>>
>> So that's a duplicate of #17724. It is fixed in org-mode (upstream) mast
> +(defun org-recenter (&optional arg)
> + "Like `recenter' but ensure that the `current-buffer' is
> +properly set."
> + (with-current-buffer (window-buffer)
> +(recenter arg)))
This doesn't make much sense: in many case (window-buffer) can be
a buffer completely unrelated to Org.
Stefan Monnier writes:
>> +(defun org-recenter (&optional arg)
>> + "Like `recenter' but ensure that the `current-buffer' is
>> +properly set."
>> + (with-current-buffer (window-buffer)
>> +(recenter arg)))
>
> This doesn't make much sense: in many case (window-buffer) can be
> a buffer c
Hi Org Mode:
I'm trying to escape an asterisk character, i.e. "*" to use in regular
text. I.e., "The person wanted to say *BSD". And I don't want to use a
verbatim or code block because monospace is not what I need.
I've tried \* to escape the character and it doesn't work. I'm on Org 8.2.5h.
Th
If you create a link to a gnus message while in a nnvirtual group, the
link will become un-followable as soon as you exit the virtual group.
This patch checks to see if we're in a virtual group, and if so it
creates the link to the original group instead.
E
>From 2d1dbbeb071e256ff37be798e8e04689a
James Ryland Miller writes:
> Hi Org Mode:
>
> I'm trying to escape an asterisk character, i.e. "*" to use in regular
> text. I.e., "The person wanted to say *BSD". And I don't want to use a
> verbatim or code block because monospace is not what I need.
>
> I've tried \* to escape the character a
28 matches
Mail list logo
