Hi,
I started using the new odt export feature of org mode, and it turns out
to be very useful, and I am very pleased with the results. I am using
the latest version available with the package manager of emacs-snapshot
in debian (20120216).
There, the export of documents with footnotes seems to b
cbe...@tajo.ucsd.edu writes:
> I sometimes create large documents with many dozens of src blocks and
> associated #+RESULTS.
>
> I'd like to be able to grab some of these results blocks and export them
> into a document. Since revisions of the src blocks can change the
> results, I do not want to
I sometimes create large documents with many dozens of src blocks and
associated #+RESULTS.
I'd like to be able to grab some of these results blocks and export them
into a document. Since revisions of the src blocks can change the
results, I do not want to just and to copy and paste the results i
Colin Fraizer writes:
> Wow, I think I'm an org pariah. Did my email violate some org cultural
> norm? :-)
Not that I'm aware of :)
>
> If so, I apologize.
>
> Anyone have strong feelings about whether a change like this is
> advisable?
This should probably go to Carsten and Nicolas since they
Andreas Leha writes:
> Hi all,
>
> attached is a patch that enhances org-babel-goto-named-src-block (bound
> to C-c C-v g by default). Included are two enhancements:
>
> 1. the point is pushed to the org-mark-ring, such that returning with
> C-c & becomes possible
> 2. the target src block
Herbert Sitz gmail.com> writes:
>
> (define-minor-mode evil-org-mode
> "minor mode to add evil keymappings to Org-mode."
> :keymap (make-sparse-keymap)
> (evil-local-mode t))
>
Whoops, I left out the earlier lines to load and enable Evil. They are
below. I commented out the (evil-mode 1), whi
I was playing around with Evil and like it quite a bit. It feels better than
the previous Viper/Vimpulse package I was using, plus documentation is good,
clear, and it seems easy to customize.
One problem with Org for me has been keybindings. Even with a Vim emulator that
does a decent job of vi
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.
--
Wow, I think I'm an org pariah. Did my email violate some org cultural norm? :-)
If so, I apologize.
Anyone have strong feelings about whether a change like this is advisable?
On Feb 27, 2012, at 12:32 PM, "Colin Fraizer" wrote:
> The variable org-latex-regexps has an element
>
>("$" "\\
g.kettleboro...@uea.ac.uk writes:
> Attached is a patch that gives the option to show the clock and timer
> information in the frame title as well as the mode line (or both or
> neither). I find this useful as there is often not enough room in the
> mode line but there is enough in the frame titl
Karl Fogel wrote:
> [please keep me CC'd, as I'm a digest subscriber on this list]
>
> Suddenly "C-c a a" (`org-agenda-list') has started giving me this error:
>
>args-out-of-range #(" ots:" 0 14 (org-category ...
>
> Backtrace attached. This is with today's bleeding edge Org Mod
[please keep me CC'd, as I'm a digest subscriber on this list]
Suddenly "C-c a a" (`org-agenda-list') has started giving me this error:
args-out-of-range #(" ots:" 0 14 (org-category ...
Backtrace attached. This is with today's bleeding edge Org Mode code,
pulled from git://orgmode.
Attached is a patch that gives the option to show the clock and timer
information in the frame title as well as the mode line (or both or
neither). I find this useful as there is often not enough room in the
mode line but there is enough in the frame title.
I am in the process of assigning my cop
Peter Salazar wrote:
> Ah perfect! I followed your steps and tracked the problem down to one
> of my agenda files. Not sure why org didn't like it, but when I
> removed that file from my agenda list, it worked like a charm.
>
Did you get a backtrace? That (in combination with the file itself)
Ah perfect! I followed your steps and tracked the problem down to one of my
agenda files. Not sure why org didn't like it, but when I removed that file
from my agenda list, it worked like a charm.
Thank you!
On Sat, Feb 25, 2012 at 12:52 AM, Nick Dokos wrote:
> Peter Salazar wrote:
>
> > Mayb
On lun. 27/févr. (09:52), Eric Schulte wrote:
> Simon Castellan writes:
>
> > On lun. 27/févr. (15:27), Alan Schmitt wrote:
> >> On 26 févr. 2012, at 17:41, Simon Castellan wrote:
> >>
> >> > I have been writing a parser for mlorg files in OCaml. This started as an
> >> > experiment to see if th
I use a few tags and usually two or three will apply to all entries in a
particular file, e.g. :work:Client:OpenFile: or :Personal:Home:
All my tags are in my .emacs using the org-tag-alist and I want to use
these consistently.
Is there a way to access org-tag-alist from the in-buffer setting
On Thu, Oct 6, 2011 at 5:15 PM, John Hendy wrote:
> Is there a way to create a date-tree in my current file, or is the
> only way to use a capture template pre-set to use a date-tree for the
> headline? For projects I have a setup something like this:
>
> ---
> * Tracking
> Stores todos and such
>
Anyway, I can't emphasize enough how useful this feature is. Having
different agenda filtered views at the same time is a timesaver. This
should be in the main org branch!
Thanks for that, Max.
Cheers,
Marcelo.
On Tue, Feb 28, 2012 at 10:55 AM, Marcelo de Moraes Serpa <
celose...@gmail.com> wro
Thanks guys, que quickfix worked. I'll see if I can rebase to org's HEAD
myself, let's see if conflicts don't scare me away. Or perhaps just apply
the fix manually.
- Marcelo.
On Tue, Feb 28, 2012 at 3:49 AM, Max Mikhanosha wrote:
> At Mon, 27 Feb 2012 18:52:09 -0600,
> Marcelo de Moraes Serp
Hello to all,
I have a question, I could not find an answer myself using the
org-manual or googling. Mayby someone can help.
I have several org-files with headings and subheadings similar to this:
File #1:
* Literatur, Quellen :Bib:
** AuthorSirName-1 ...
** AuthorSirName-2 ...
** AuthorSirN
On 28/02/12 08:58, Ian Barton wrote:
I have just found this very useful function in org hacks. Unfortunately,
it doesn't seem to work with the latest org-mode. I get the following
error:
Function definition void org-in-regexps-block-p
Grepping the org source code, it seems that this function no
Hello,
I don't know if this is correct and sufficient, so please amend if not...
>From 8754d92bc954ccc9d1c2178ffcae5144b83b2af2 Mon Sep 17 00:00:00 2001
From: Sebastien Vauban
Date: Tue, 28 Feb 2012 14:26:37 +0100
Subject: [PATCH 4/4] Add autoload instruction before org-version
---
lisp/org.e
Bernt Hansen wrote:
> Nick Dokos writes:
>
> > ...
> > but I cannot find the previous deletion.
>
> From
> git log -Sdefun\ org-publish-validate-link
>
> ,
> | commit b05bc10e6794c902df679b906d8bd6ec3f5633a9
> | Author: Bastien Guerry
> | Date: Sun Mar 2 14:14:52 2008 +
> |
> |
Nick Dokos writes:
> François Pinard wrote:
>
>
>> The manual, in [[info:org#Publishing%20links][Publishing links]],
>> speaks about an *org-publish-validate-link* function which does not seem
>> to exist in Org mode sources. Is the function missing, or the
>> documentation misleading? :-)
>>
Hi Thomas,
t...@tsdye.com (Thomas S. Dye) writes:
> The "Show Org source" button on Worg is a great addition. Thanks!
I added this a few days ago -- this will be on all new/updated
worg pages, so don't worry if they are still some pages not showing
this button.
Best,
--
Bastien
At Mon, 27 Feb 2012 18:52:09 -0600,
Marcelo de Moraes Serpa wrote:
> Although everything else is working great, I'm getting the following
> error message when trying to follow links to org files:
>
> "cond: Symbol's function definition is void: org-in-clocktable-p [11 times]"
My branch is probab
I have just found this very useful function in org hacks. Unfortunately,
it doesn't seem to work with the latest org-mode. I get the following error:
Function definition void org-in-regexps-block-p
Grepping the org source code, it seems that this function no longer
exists. What has it been rep
28 matches
Mail list logo