> Can you please try this patch out and report whether it
> works or not and whether it causes any other problems?
> I'm not sure if Bastien is around to vet it, but if it
> seems to work for you, I can push it and deal with any
> other breakage later.
Seems to work here, the error is gone, very n
Correction below...
Matt Lundin writes:
>
> #+BEGIN_SRC emacs-lisp :exports none :results none
> (save-excursion
> (goto-char (point-min))
> (while (re-search-forward "#\\+RESULTS: generate-blog-summary" nil t)
(when ...
> (beginning-of-line)
> (delete-region (point) (
Aloha Grant,
Grant Rettke writes:
> Good evening,
>
> From [org-scraps] I pasted this example into a buffer:
>
> ,—-
> ━
> #+name: square
> #+begin_src emacs-lisp :var it=0
> (* it it)
> #+end_src
>
> Here is a call_square(it=4
> Von: Karl Voit
> Organisation: www.karl-voit.at
> Antworten an: Karl Voit
> Datum: Tue, 1 Jul 2014 21:07:32 +0200
> An:
> Betreff: Re: [O] Collecting unique selling proposition (USP) of Org-mode
>
>> I think the best thing to compare different tools is making a list with
>> features and ma
Nick Dokos writes:
>>
>> In short, is there a more graceful and export-friendly way to use babel
>> to generate org headlines for export? Or is there an easy way to get the
>> export backend to delete the opening part of the drawer (i.e.,
>> :RESULTS:)?
>>
>> Any advice would be greatly appreciate
Good evening,
From [org-scraps] I pasted this example into a buffer:
,—-
━
#+name: square
#+begin_src emacs-lisp :var it=0
(* it it)
#+end_src
Here is a call_square(it=4), stuck in the middle of some prose.
Matt Lundin writes:
> I am attempting to use a babel code snippet to generate org headlines
> for export. However, I seem to be running into a corner case here.
>
> AFAICT, the only way to generate headlines safely with babel is to wrap
> them in a :RESULTS: drawer.
>
> Take the following example
I am attempting to use a babel code snippet to generate org headlines
for export. However, I seem to be running into a corner case here.
AFAICT, the only way to generate headlines safely with babel is to wrap
them in a :RESULTS: drawer.
Take the following example:
--8<---cut here
Hi,
Here's a patch to the testing/README-documentation on the interactive
part. I found that I had to do a couple of extra steps to run tests
interactively from emacs -q.
Thanks,
Rasmus
--
Hooray!
>From 1368f47b72e4a7f90888e5f3e6860afbee438cec Mon Sep 17 00:00:00 2001
From: Rasmus
Date: Fri,
Rasmus writes:
>
> Nicolas removed the "$" at the end of the regexps identifying LaTeX
> environments here:
>
>
> http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=ec0e3cf70ba353ea59a5e66235462f659c99
>
> There a current thread discussion of this behavior on this list called
> somethin
Hi Nick,
Nick Dokos writes:
> I just pulled (HEAD is 02f2d5b42aabe9e272a5967ad0483b38750a8392)
> and got this test failure:
>
> ,
> | Test test-org-element/latex-environment-parser backtrace:
> | (if (not (unwind-protect (setq value-102202 (apply fn-102200 args-10
> | (let (form-descript
Thorsten Grothe writes:
>> I believe that you'll have to live with the problem for a while: it
>> might be easy to fix or it might be difficult but until somebody takes a
>> deeper look, we won't know for sure.
>
> Of course I can live with that, we are on open source here and here are many
> peo
Can you please try this patch out and report whether it
works or not and whether it causes any other problems?
I'm not sure if Bastien is around to vet it, but if it
seems to work for you, I can push it and deal with any
other breakage later.
--8<---cut here---start---
I just pulled (HEAD is 02f2d5b42aabe9e272a5967ad0483b38750a8392)
and got this test failure:
,
| Test test-org-element/latex-environment-parser backtrace:
| (if (not (unwind-protect (setq value-102202 (apply fn-102200 args-10
| (let (form-description-102204) (if (not (unwind-protect (setq
> I believe that you'll have to live with the problem for a while: it
> might be easy to fix or it might be difficult but until somebody takes a
> deeper look, we won't know for sure.
Of course I can live with that, we are on open source here and here are many
people like you doing a great big job
Nick Dokos writes:
> Robert Klein writes:
>
>> I made some quick tests with different org versions; the first one I see
>> this issue is git commit 30220ffcdcef45c0237f80a2347d4da19877f64a
>> (release_8.2.6-77-g30220f).
>>
>> I don't see the patch causing this, yet; have to look further.
>>
>
>
Nick Dokos zgmail.com> writes:
>
> Can anybody else reproduce this?
/me raises hand.
Greetings.
This is probably a bug:
#+BEGIN_SRC lisp :results output
(format t "Hello world.")
;; comment after, causes crash when block is evaluated with C-c C-c
#+END_SRC
Debugger message:
#+BEGIN_QUOTE
end of file on #
[Condition of type END-OF-FILE]
#+END_QUOTE
org-version: Org-mode v
Nick Dokos gmail.com> writes:
> Nope - I tried to reproduce it with latest (both master and maint) and
> could not, so I suspect an error in your configuration.
>
I experience the same issue.
http://article.gmane.org/gmane.emacs.orgmode/88610
/Luke
Robert Klein writes:
> I made some quick tests with different org versions; the first one I see
> this issue is git commit 30220ffcdcef45c0237f80a2347d4da19877f64a
> (release_8.2.6-77-g30220f).
>
> I don't see the patch causing this, yet; have to look further.
>
Absolutely right, that looks like
I made some quick tests with different org versions; the first one I see
this issue is git commit 30220ffcdcef45c0237f80a2347d4da19877f64a
(release_8.2.6-77-g30220f).
I don't see the patch causing this, yet; have to look further.
Best regards
Robert
On 07/22/2014 09:01 PM, Nick Dokos wrote:
> N
Nick Dokos writes:
> Thorsten Grothe writes:
>
>>> If the frame is bigger than about 50 lines (so that after C-c ', it's
>>> big enough to show the whole table, including the formula and the empty
>>> line underneath it) then I don't see the problem.
>>
>> Thank you very much for your instructio
Hi, I'm looking to develop an agenda or even a list that will report the
following for a buffer
Or for agenda-files:
All headlines with time clocked for the specified time range, or without time
clocked for specified time range
IE by day or week
Must include headlines without a TODO status
The
Hello all,
org-narrow-to-subtree is very nice, and I now have C-x n s hard-wired
into my fingers, but it doesn't work when outline-regexp is too
different from org-outline-regexp in Outline-but-non-Org mode buffers.
It looked pretty easy to fix, so here is my suggestion, below. It should
be rathe
Thorsten Grothe writes:
>> If the frame is bigger than about 50 lines (so that after C-c ', it's
>> big enough to show the whole table, including the formula and the empty
>> line underneath it) then I don't see the problem.
>
> Thank you very much for your instructions!
>
> yes you are right for
Nick Dokos writes:
>>> Are you getting an extraneous comma with the #+attr_latex line?
>>>
>>> All the best,
>>> Tom
>>>
>>
>> I do not get any extraneous comma. When using the #+attr_latex line
>> there is just nothing in the latex output.
>>
>
> Same here.
Then none of us gets the result not
> If the frame is bigger than about 50 lines (so that after C-c ', it's
> big enough to show the whole table, including the formula and the empty
> line underneath it) then I don't see the problem.
Thank you very much for your instructions!
yes you are right for the org file. I tested Roberts exa
Alan Schmitt writes:
> On 2014-07-21 19:45, Peter Davis writes:
>
>> Alas, despite years of emacs abuse, I have not managed to master even
>> the rudiments of emacs lisp, and don't even know how to edebug.
>
> To get you started, you could try the following.
>
> - set up two emacs frames
> - in
On 2014-07-21 19:45, Peter Davis writes:
> Alas, despite years of emacs abuse, I have not managed to master even
> the rudiments of emacs lisp, and don't even know how to edebug.
To get you started, you could try the following.
- set up two emacs frames
- in one frame, do a "M-x describe-functi
Brett Viren writes:
> Nick Dokos writes:
>
>> I think you'd be better off with the tip that Rick Frankel posted in
>> the same thread:
>>
>> #+BEGIN_SRC emacs-lisp
>> (add-hook 'org-babel-after-execute-hook
>> (lambda () (org-display-inline-images nil t)))
>> #+END_SRC
>
> Thanks Nick (and Rick)
Nick Dokos writes:
> I think you'd be better off with the tip that Rick Frankel posted in
> the same thread:
>
> #+BEGIN_SRC emacs-lisp
> (add-hook 'org-babel-after-execute-hook
> (lambda () (org-display-inline-images nil t)))
> #+END_SRC
Thanks Nick (and Rick). I changed this to use the "re" v
Hi,
Nicolas Goaziou writes:
>> +(defconst org-element--latex-begin-environment
>> + "^[ \t]*begin{\\([A-Za-z0-9*]+\\)}"
>
> I overlooked this in the previous patch. This regexp is not correct, as
> it matches, e.g.
>
> \begin{ab*cd}
>
> A more accurate regexp is
>
> "^[ \t]*begin{\\
Nicolas, thank you for reply. Due to some health issues I’m only
responding now.
On So, 2014-07-06 at 21:28 +0200, Nicolas Goaziou wrote:
> Tobias Getzner writes:
>
> > If there is some strong reason for a hard-coded limit, would it be
> > possible to expose the limit as a user-definable variabl
Thorsten Jolitz writes:
> Rasmus writes:
>
>> Nick Dokos writes:
>>
>>> I just found out that François Pinard (author of org grep among other
>>> tools and frequent contributor to this list) died recently:
>
> This is sad news.
>
> Somehow, whenever I had an idea for a *brandnew*, cool&useful
Rasmus writes:
> Nick Dokos writes:
>
>> I just found out that François Pinard (author of org grep among other
>> tools and frequent contributor to this list) died recently:
This is sad news.
Somehow, whenever I had an idea for a *brandnew*, cool&useful little Org
library and went ahead imple
Rasmus writes:
> The attached patch hopefully addresses all of the issues you pointed
> out. Sorry about those typos before!
Thanks for the update. Some more comments below.
> +(defconst org-element--latex-begin-environment
> + "^[ \t]*begin{\\([A-Za-z0-9*]+\\)}"
I overlooked this in the
On 2014-07-21 11:32, Thorsten Jolitz writes:
> These message-drafts are really redundant and a bit annoying, but I have
> no idea about the inner workings of gnus and doing
>
> ,
> | C-h f gnus-draft- TAB
> | C-h v gnus-draft- TAB
> `
>
> did not enlighten me any further. So I will ask
Nicolas Goaziou writes:
> Hello,
>
> Rainer M Krug writes:
>
>> THis patch adds out-of-the-box fontification of makefile source code
>> blocks when using the package listings. As the makefile code blocks are
>> named =makefile= and the name of the language definition in the package
>> =listings=
Is there a way to show time effort estimates in the org-clock-report?
I found only that :properties ("Effort") could be specified, but it does
not work
neither for one level, nor for summing children nodes' estimations.
--
Alexander Artemenko (a.k.a. Svetlyak 40wt)
Blog: http://dev.svetlyak.ru
Ja
SabreWolfy writes:
> This repeats an event on the first of the month forever:
>
> * Attend Monthly Meeting
><2014-05-01 +1m>
>
> How do I indicate that the event should be repeated monthly for 6 months
> only? Time-shift?
I think so: C-c C-x c (org-clone-subtree-with-time-shift)
Nick
Hi,
Nicolas Goaziou writes:
> IMO, the way to go would be to define regexps as constants everywhere in
> "org-element.el", but that would introduce duplicates with some
> constants in "org.el". IOW, there's no clear design about it. Situation
> may change when the parser gets more integrated int
Thorsten Grothe writes:
>> Now, when I go down to the first formula whose referenced field(s) are
>> not visible, the cursor in the org file jumps to the end of the file
>> which is then displayed at the upper end of the tabletest.org buffer window.
>>
>>
>>
>> In "sufficient" long org files t
This repeats an event on the first of the month forever:
--8<---cut here---start->8---
* Attend Monthly Meeting
<2014-05-01 +1m>
--8<---cut here---end--->8---
How do I indicate that the event should be repeated monthly for
Robert Klein writes:
>
> I confirm at least some variant of this.
>
> I start emacs using the command line "emacs -Q -l .e2" with .e2 being:
>
> #+begin_src elisp
> (setq load-path (cons "~/.emacs.d/org-mode/lisp" load-path))
> (add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\|txt\\
> Now, when I go down to the first formula whose referenced field(s) are
> not visible, the cursor in the org file jumps to the end of the file
> which is then displayed at the upper end of the tabletest.org buffer window.
>
>
>
> In "sufficient" long org files the visible cursor jumps to the en
Manfred Lotz writes:
> Hi Thomas,
>
> On Mon, 21 Jul 2014 10:48:14 -1000
> t...@tsdye.com (Thomas S. Dye) wrote:
>
>> Hi Manfred,
>>
>> Manfred Lotz writes:
>>
>> > Hi Tom,
>> >
>> > On Mon, 21 Jul 2014 09:53:41 -1000
>> > t...@tsdye.com (Thomas S. Dye) wrote:
>> >
>> >> Aloha Manfred,
>> >>
Nick Dokos writes:
> I just found out that François Pinard (author of org grep among other
> tools and frequent contributor to this list) died recently:
>
> https://plus.google.com/118038589019918324505/posts/DFuvYBrh4th
>From his interaction with this list François seemed like a great guy.
RIP.
Hello,
Rasmus writes:
Thanks for your patch.
> Turns out that I also had to modify the regexp in
> org-element--current-element as this kicks off
> org-element-latex-environment-parser (correct me if I am wrong).
Correct.
> In the patch I define new regexps and use them everywhere.
> Org-elem
48 matches
Mail list logo
