updated. thanks guys and gals :)
https://gist.github.com/4343164
tony day
tonyday...@gmail.com
On 7 Jan 2013, at 18:16, Achim Gratz strom...@nexgo.de wrote:
Yasushi SHOJI writes:
+ (org-agenda-buffer (if (buffer-live-p org-agenda-buffer)
+ org
On 7 Jan 2013, at 04:41, Alan Schmitt alan.schm...@polytechnique.org wrote:
The bare minimum one can do is:
- rename the current init.el into myinit.org
- add the lines #+begin_src emacs-lisp as the first line, and
+end_src as the last line
- adapt the init.el from emacs-starter-kit as
Bastien b...@altern.org writes:
I would first ask myself what is the new org format for?
Is it worth implementing this?
Best,
My motivation is to have an ability to create a virtual org file. My
workflow involves sharing bits and pieces of plain text with non-org
users and, right now,
Julian Burgos jul...@hafro.is writes:
- Is there a better way to have a non-org mode use to edit/correct a
org-mode document and then bring back the corrections to an org-mode
document?
If MS Word users can't tolerate plain text org-mode files then I can't
think of many shortcuts. This works
Bastien b...@altern.org writes:
In other words, we could then /apply/ org-mode
on a document rather than transforming a document into an org
document.
What we may think about is a Org readable exchange format (oref?),
which would take the output of Nicolas' parser, export it in Org-mode
I have exactly 386 TODO entries and may as well introduce some
randomness to get to them.
org-random-entry: select and goto a random todo entry. Prefix allows you
to select which todo keyword.
https://gist.github.com/4343164
On 18 Dec 2012, at 22:55, Bastien b...@altern.org wrote:
Hi Tony,
Hi Bastien,
Thanks for the flurry of activity :)
Tony Day tonyday...@gmail.com writes:
Is there an easy way to preserve indentation for a source block taking
into account previous blocks?
No. Besides, I don't
Is there an easy way to preserve indentation for a source block taking
into account previous blocks? For (a silly) example:
* foo
:PROPERTIES:
:tangle: yes
:END:
#+begin_src emacs-lisp
(defun foo ()
#+end_src
#+begin_src emacs-lisp
(bar)
#+end_src
#+begin_src emacs-lisp
)
#+end_src
On 9 Dec 2012, at 02:24, Nick Dokos nicholas.do...@hp.com wrote:
Is there a method where you can use
#+INCLUDE without overwriting the current buffer?
You can do what org-export-preprocess-string does: create a temp
buffer, insert the contents of the original buffer and call
Hi Vikas,
On 6 Dec 2012, at 11:49, Vikas Rawal vikasli...@agrarianresearch.org wrote:
I would like to have a section in the index.html that shows links to
recently changed/added html pages. It would be nice if I could show
titles of such pages, and create links from these titles to the
Hi,
I would like to add a class to a list on html export. So, this:
#+BEGIN_EXAMPLE
- [[#][Home]]
- [[#about][About]]
- [[#contact][Contact]]
#+END_EXAMPLE
becomes this:
#+BEGIN_EXAMPLE
ul class=nav
lia href=#Home/a
/li
lia href=#aboutAbout/a
/li
lia href=#contactContact/a
/li
/ul
In the current buffer, org-export-handle-include-file overwrites:
#+INCLUDE: ./some-other-file.org
with contents of the other file. For example,
#+BEGIN_EXAMPLE
* other file header
:PROPERTIES:
:OTHER_PROPS: yes
:END:
Contents of the other file.
#+END_EXAMPLE
Is this the intended behaviour?
Hi,
I've been thinking about a patch for org-mode that would give an
option to place various org concepts in a drawer rather than
automatically in the body of the document. The overall idea is that
for some use cases, it makes sense to disturb the underlying content
as little as possible. In
Esben Stien b...@esben-stien.name writes:
Is there some way to go directly to a node?
F.ex, I have:
* foo
** bar..
** baz..
** hukarz..
I do C-c a s to search for baz, which brings up a buffer with baz
somewhere in there and I have to move down the list to hit TAB on baz.
Inserting a yas snippet consisting of a code block is a very common occurence
in my work flow. Now I have the right yas settings to make it all happen I
think.
#+begin_src emacs-lisp
(setq yas/also-auto-indent-first-line t)
(setq yas/indent-line t)
#+end_src
But on insertion, it isnt
On 18 Oct 2012, at 22:50, Rasmus ras...@gmx.us wrote:
Perhaps something like fold mode of AUCTex would be useful. I.e. all
deadline markers would be replace by a [d] which folds out when the
cursor is on [d]. It might even be possible with the magic which
replaces \delta with δ in org
I've been catching up on the mailing list, and thinking about my
personal use case versus other typical patterns. I thought I would
share a thought with the group.
I would divide use cases into three main cohorts:
- /org-planning/: org files consist mostly of planning and
tracking content
, I'm not sure to agree with you: it /is/ meaningful to have
user-defined link abbrevs before default types.
Excellent advice (yes, even the nitpicks :)
From 31c9855ca6db95d10ca09611f749d74074b19b08 Mon Sep 17 00:00:00 2001
From: Tony Day zygom...@gmail.com
Date: Fri, 12 Oct 2012 14:39:53 +1100
Hi Sam,
On 12 Oct 2012, at 07:17, Samuel Wales samolog...@gmail.com wrote:
Slighly different from this, I wonder if anybody has anything similar:
I have blog entries with a :Live-URL: property. What I'd like is to
use ido to complete on the header that contains that property, and
create a
On 11 Oct 2012, at 23:23, Nicolas Goaziou n.goaz...@gmail.com wrote:
Thanks for submitting a patch. Here are a few comments.
Hi Nicolas, thanks for taking the time to go through the code. I will resubmit
the patch in a separate mail (I didn't know whether I could respond to your
org.el (org-insert-link): removed a list within the list of link
creation that was causing a bug when using ido. Removed the hard coded
iswitch and ido switches. Changed the order of prefixes so http came
up first.
(org-iread-file-name): created a function that can use
ido-read-file-name if
From a8f301277e15bc786fa63bbcce3ba1afb85c46aa Mon Sep 17 00:00:00 2001
From: Tony Day zygom...@gmail.com
Date: Mon, 10 Sep 2012 13:54:38 +1000
Subject: [PATCH 41/41] org-insert-link: allow ido usage when inserting links
* lisp/org.el (org-insert-link): added all-links to cleanly create prefix+st
I had written this:
,
| #+MACRO: testdir ~/working
| #+begin_src sh
| cd {{{testdir}}}
| #+end_src
`
Thinking it would do this:
,
| #+begin_src sh
| cd ~/working
| #+end_src
`
Alas, #+Macro acts on export only.
Is there a quick way to effect general text substitution on
I had a look through and couldn't see an obvious reason why you can't use ido
with org-insert-link, so here's a patch to enable it.
I haven't looked at using ido for editing links yet, but I figure org-capture
would be a good pattern to do this. The other thought here is to add an 'org:'
link
This time with patch inlined.
I had a look through and couldn't see an obvious reason why you can't use ido
with org-insert-link, so here's a patch to enable it.
I haven't looked at using ido for editing links yet, but I figure org-capture
would be a good pattern to do this. The other thought
25 matches
Mail list logo
