Sorry, sorry - my bad.
My browser/client was rendering a lower case L to look just like a pipe.
So I was trying to do C-c C-
All is well. Everything's working as it should. Cancel red alert.
Cheers.
Fil
On 14 January 2011 00:17, David Maus wrote:
> At Thu, 13 Jan 2011 20:06:07 -0500,
> Filipp
At Thu, 13 Jan 2011 23:00:30 +0100,
Vincent Belaïche wrote:
>
> Hello,
>
> I have made some invesitgation, and I found that the problem happens in
> the call of function org-export-as-html. On line 522 of this function,
> this is the following line:
>
> (while (string-match org-bracket-link-anal
At Thu, 13 Jan 2011 20:06:07 -0500,
Filippo A. Salustri wrote:
> Consider this example:
> [[http://some.site.com][text text]]
> It seems that the spaces in the label part (between, say, the 2 "text"s)
> stops the link from forming.
Which Org mode and Emacs version are you using?
M-x emacs-version
When in an *org-mode buffer*, =C-h k C-c C-l= says
,
| ^C ^L runs the command org-insert-link, which is an interactive
| compiled Lisp function in `org.el'.
`
Org-mode version 7.4 (release_7.4.165.gca0e6.dirty)
On Thu, Jan 13, 2011 at 11:04 PM, Filippo A. Salustri
wrote:
> Hmm. On my i
Hmm. On my installation, =C-c C-l= isn't bound to anything. I haven't
mucked with that.
To what should =C-c C-l= be bound?
Cheers.
Fil
On 13 January 2011 20:22, Jeff Horn wrote:
> I noticed fontification was weird on my end, as well. Now, I only use
> =C-c C-l= to create and edit links. Haven'
This is now applied.
Thanks for the patch, and for the motivating usage example. -- Eric
niels giesen writes:
> Hi Eric,
>
> Please see the patch below, it adds property inheritance for all
> MAIL_* properties, based on the value of
> `org-use-property-inheritance'.
>
> #+begin_src diff
> dif
I noticed fontification was weird on my end, as well. Now, I only use
=C-c C-l= to create and edit links. Haven't had issues since making
the change.
On Thu, Jan 13, 2011 at 8:06 PM, Filippo A. Salustri
wrote:
> Consider this example:
> [[http://some.site.com][text text]]
> It seems that the spac
Consider this example:
[[http://some.site.com][text text]]
It seems that the spaces in the label part (between, say, the 2 "text"s)
stops the link from forming.
My current workaround is to use single word labels, including WikiWords.
Is this how it's supposed to work? I would have thought I could
>As for how to trace back through noweb links, the best option seem to be
>using the existing jump function to navigate from raw source to the
>embedded block, keeping track of the point's offset form the beginning
>of the block, then using `org-babel-expand-src-block' to expand the body
>of the em
I rely heavily on org-cycling/org-global-cycling to see an outline
view of the document. It would help if I could use #+begin_src and
#+results blocks, and possibly some others, in this outline view.
Specifically, I would like to be able to do the following:
(a) When cycling with S-Tab, between
Hi Eric,
Please see the patch below, it adds property inheritance for all
MAIL_* properties, based on the value of
`org-use-property-inheritance'.
#+begin_src diff
diff --git a/contrib/lisp/org-mime.el b/contrib/lisp/org-mime.el
index 68a3498..ae430fb 100644
--- a/contrib/lisp/org-mime.el
In agenda todo lists, currently it is possible to ignore scheduled
items according to when they are scheduled, using the variable
'org-agenda-todo-ignore-scheduled'. This can take one of three
values - all, future (ignore if scheduled after today), or past
(ignore if scheduled TODAY or in the past
Eric Schulte gmail.com> writes:
>
> The following function could be bound to a key, and should do the job if
> called with the point on the src_lang portion of the inline code block.
>
[snip - gmane web-thingy won't let me quote the function]
Thanks Eric!
I will try to come up with a minimal e
Hello,
I have made some invesitgation, and I found that the problem happens in
the call of function org-export-as-html. On line 522 of this function,
this is the following line:
(while (string-match org-bracket-link-analytic-regexp++ line start)
When the line containing the link is processed, th
Paul Sexton writes:
> I have an org-mode document that uses a lot of R code (via babel). I have
> found
> that using inline code blocks, ie src_R{...}, within org tables works
> "erratically", often either causing emacs to hang during latex export, or
> producing a table where random cells conta
I briefly mentioned the approach you describe below earlier in this
thread [1], and while I see the appeal of this approach, I think that
the second approach I described in that same message (using offsets
instead of comments) is preferable -- although I am of course open to
being persuaded otherwi
I've pushed up a fix for this issue,
Instead of using language-specific comment regexps ob-jump-to-org now
keep looking for a block-start comment until it find one which has a
matching block-end comment.
Thanks for pointing out this error case -- Eric
Seth Burleigh writes:
> Ive attached the f
On Thu, Jan 13, 2011 at 12:04 PM, Nick Dokos wrote:
> Matt Lundin wrote:
>
>> > So, how many of you here also use Vim? :)
>>
>> For quick editing (e.g., config files), I use vi(m). For anything else,
>> I use emacs. Both are fantastic tools.
>>
>
> For quick editing of config files, I use "sudo e
Hello,
when using babel with octave code, passing variables with the =:var=
header argument creates octave code whose results are echoed onto
standard out. This is not necessarily wanted. The default behaviour, I
believe, should be to not echo anything out as the user can always
simply print out
Matt Lundin wrote:
> > So, how many of you here also use Vim? :)
>
> For quick editing (e.g., config files), I use vi(m). For anything else,
> I use emacs. Both are fantastic tools.
>
For quick editing of config files, I use "sudo ed" - from an Emacs shell :-)
Nick
__
Marcelo de Moraes Serpa writes:
>
> However, I've got hooked. Vim (in my case, MacVim) has conquered my
> hands. I know I'm risking myself a lot by saying it on an
> emacs-related mailing list, but the Vim navigation and the vim model
> in general is much more efficient for editing text.
Empirica
I have an org-mode document that uses a lot of R code (via babel). I have found
that using inline code blocks, ie src_R{...}, within org tables works
"erratically", often either causing emacs to hang during latex export, or
producing a table where random cells containing 'nil' instead of the result
Hi Eric and Carl,
"Eric Schulte" wrote:
> Carl Bolduc writes:
>> Where I work, we have a powerful search engine that indexes all kinds of
>> files. It detects the converter to use based on the file extension. It does
>> not understand the .org extension.
>>
>> I would like to know how I could per
All,
I have written org-table-comment.el (at
http://www.emacswiki.org/emacs/download/org-table-comment.el) which should
allows you to create org-tables in languages that do not have
block comments. For example in elisp:
;; |--+++---|
;; | |||
Note: run using emacs -q as the bug was reproducible, and this will
produce less settings that may complicate the report.
Note: only a few months of unix and emacs usage
When using org-indent-mode and linum-mode simultaneously, clicking on
any line in an org-mode file will cause the cursor and
well, exporting to txt gives a better result for reading in other text
editors, I should have mentioned that those files will be accessible by
others who do not use Emacs...
Carl
2011/1/13 Eric Schulte
> Since Org-mode files are plain text, I don't think you would need to
> export them at all,
Nice!
I think that the classic flame wars, while unavoidable at certain
levels, just end up sucking energy. Why not embrace and use the best
of both worlds to your benefit?
Emacs and Vim are without any doubt the best two piece of software in
what comes to text editing/surgery. Emacs has orgmode
Since Org-mode files are plain text, I don't think you would need to
export them at all, rather I would imagine an easier solution would be
to either
1. teach the search engine that .org means .txt
2. symlink all of your .org files to .txt file, e.g. on a linux, unix,
OSX system the following
Hi all
What do you think about having _outline path in links_ as described in
the following?
I have seen that an outline path like `Bach/Prelude' can be used to
refile notes into a heading `Prelude' that has a parent heading named
`Bach'. An outline path like `Chopin/Prelude' refiles into a diffe
Where I work, we have a powerful search engine that indexes all kinds of
files. It detects the converter to use based on the file extension. It does
not understand the .org extension.
I would like to know how I could periodically export my org files to txt,
maybe through a command, to a specific l
Jason Dunsmore writes:
> I'd be interested to hear about other workflows or how mine might be
> improved.
I'd say whatever works for you works. :-)
I've set up all but one of my various git clones up to rebase by default
instead of merging when doing a pull. That way I can float my local
change
Ive attached the file it fails on. Notice that it fails below the constants
macro, but if you're above it, it will succeed since it wont find the [[name
val]]
general.clj
Description: Binary data
___
Emacs-orgmode mailing list
Please use `Reply All' to
Marcelo de Moraes Serpa writes:
> Hey list,
[...]
> However, I've got hooked. Vim (in my case, MacVim) has conquered my
> hands. I know I'm risking myself a lot by saying it on an
> emacs-related mailing list, but the Vim navigation and the vim model
> in general is much more efficient for edit
Julien Danjou writes:
> Hi there,
>
> I'm sending a set of patches from my current `jd/agenda-format-2' branch
> visible at [1].
>
> The ultimate goal of this is to replace `org-agenda-prefix-format' by
> `org-agenda-format' which controls the whole agenda line format and not
> only its prefix. T
Rafael Villarroel writes:
> Sébastien Vauban writes:
>
>> Erik Iverson wrote:
>>> According to http://orgmode.org/worg/org-tutorials/org-beamer/tutorial.html
>>>
>>> the following markup should work when exporting to PDF from an org-beamer
>>> document.
>>>
>>> - the first, very @important@, poi
thanks. also, when trying to detangle my code, i found another bug.
In the functions org-babel-tangle-jump-to--org and org-babel-detangle, it
uses org-bracket-link-analytic-regexp to search for the [[file:]] links.
However, it does not include the comment in the regex (";;" in clojure), so
someho
Thanks for pointing this out, I've just pushed up your change.
Cheers -- Eric
Seth Burleigh writes:
> (defun org-babel-update-block-body (new-body)
> "Update the body of the current code block to NEW-BODY."
> (if (not (org-babel-where-is-src-block-head))
> (error "not in source block"
Francesco Pizzolante writes:
> Dear Eric,
>
> Thanks for your answer.
>
>> In your example the cv source block only seems to have a single variable
>> specified with a :var header argument (namely v-jobtitle), e.g.
>>
>> #+srcname: cv
>> #+begin_src latex :noweb yes :var v-jobtitle="Software Engi
(defun org-babel-update-block-body (new-body)
"Update the body of the current code block to NEW-BODY."
(if (not (org-babel-where-is-src-block-head))
(error "not in source block")
(save-match-data
(replace-match (concat (org-babel-trim new-body) "\n") nil t nil 5))
(indent-ri
I would just like to throw in a quick idea.
The easiest way to support noweb tangling is to get org-babel-tangle to
create nested tags and change detangle to take these into account.
for example, i have the forex_user source block that is tangled.
;; [[file:~/Dropbox/.rep/clj-forex/clj-forex.org:
The decision for when to add email and author information to an
exported document seems to be treated somewhat inconsistently
between export backends.
The intent appears to be that the global default for exporting
the author's name is controlled by org-export-author-info, and
the email by org-expo
Hi Andrew
On Thu, Jan 13, 2011 at 13:27, Andrew J. Korty wrote:
> I've tried several times to use Viper, but I always give up. The usual
> showstopper is read-only Emacs modes with single-character key bindings,
> like MH-E. The d key deletes a message in an MH folder, but in vi, d
> deletes te
* org-latex.el (org-export-latex-make-header): Export email in
author line if `org-export-email-info' is non-nil.
Previously exporting to LaTeX would not include the document author's
email address when org-export-email-info was set. This patch corrects
this oversight using the \thanks command to
Carsten Dominik writes:
Hi Carsten,
> Patch 533 (http://patchwork.newartisans.com/patch/533/) is now "Accepted".
The patch below was wrong. The patch in the next mail that used
`ignore-errors' instead of `condition-case' is the right one.
Bye,
Tassilo
>> diff --git a/lisp/org-gnus.el b/lisp/
On 8/18/10 Aug 18 -5:01 AM, Erwin Panen wrote:
> Hi Juan,
>
> I hope you don't mind me mailing you directly. I copied orgmode list in cc.
>
> Do you have a way to copy / paste between say Firefox and Emacs / orgmode?
>
> It doesn't seem to work, and I've found some posts googling, but no
> appar
"Eric Schulte" writes:
> Eric S Fraga writes:
[...]
>> management issue: I find it difficult (a) to remember what all my source
>> code snippets are called and (b) to navigate to any given snippet. I
>> would love to see a babel table of contents popup (a la the table of
>> contents popup wit
Not that I want to (or even could) undermine the justifiable popularity of
emacs,
but there is a ongoing effort to port org to vim: vimorganizer 9
http://www.vim.org/scripts/script.php?script_id=3342)
Cheers.
Fil
On 13 January 2011 03:34, Michael Brand wrote:
> Hi Detlef
>
> On Thu, Jan 13, 2011
I've tried several times to use Viper, but I always give up. The
usual showstopper is read-only Emacs modes with single-character key
bindings, like MH-E. The d key deletes a message in an MH folder, but
in vi, d deletes text to a target. So the obvious thing to do is turn
Viper mode off in
On Jan 9, 2011, at 3:02 PM, David Maus wrote:
At Mon, 20 Dec 2010 19:12:33 + (UTC),
Rasmus wrote:
Hi,
I think there might be a bug when using #+INCLUDE and the LaTeX
exporter. The
content of the included file is exported twice, although slightly
different in
each case. I experience th
Patch 533 (http://patchwork.newartisans.com/patch/533/) is now "Accepted".
Maintainer comment: No comment
This relates to the following submission:
http://mid.gmane.org/%3C87bp3moyua.fsf%40member.fsf.org%3E
Here is the original message containing the patch:
> Content-Type: text/plain; charset=
Hi Tommy,
Tommy Stanton wrote:
> I would guess that the simple use of 'g' for refreshing was inspired by the
> Emacs buffer list (induced by C-c C-b; you enter "Buffer Menu" mode while in
> that *Buffer List* buffer's window).
>
> Discovering 'g' for the buffer list took me a long time, but I was
Hi Eric,
Eric S Fraga wrote:
> Tassilo Horn writes:
>> this patch should do the trick. I think the issue was a malformed Date:
>> header that couldn't be converted to a timestamp.
>
> Actually, I am curious about this. What is the point of extracting the date
> in any case? It's used to store lin
Hi Detlef
On Thu, Jan 13, 2011 at 08:32, Detlef Steuer wrote:
> I would be interested to hear about difficulties you face when using
> org-mode together with viper. Or aren't there any?
If not programming I use Org together with viper almost all the time
when in Emacs and I know only of two smal
Dear Eric,
Thanks for your answer.
> In your example the cv source block only seems to have a single variable
> specified with a :var header argument (namely v-jobtitle), e.g.
>
> #+srcname: cv
> #+begin_src latex :noweb yes :var v-jobtitle="Software Engineer"
> ...
> #+end_src
>
> however your e
54 matches
Mail list logo
