Hi Rainer,
This patch looks very promising. (I have not had a chance to test the
implementation yet). One issue might be the name of the “org” variable
– maybe this should instead be “.org” or “_org” to lessen the chance of
stomping on pre-existing variables named “org” in people’s code.
Thanks
Hi,
Here's one way to do it, applied to an example that takes less space:
With ten rows, say we want to count down from 365 to 358 in the middle
of the middle column ($2), leaving an empty row on top and bottom (@1
and @10).
Set the value of @2$2 to 365, either manually or (as below) in the tabl
Sorry, the code in last source block in my attachment got a little bit
messed up. I corrected it in this attachment.
On 21 March 2014 12:23, Bastien wrote:
> Hi Michael,
>
> thanks for the patch.
>
> Pontus Michael writes:
>
> > Primary reason for this change is to fix the problem which I desc
Source block fontification is achieved by copying source block contents
into temporary buffer under appropriate major mode and mirroring face
text-properties into original buffer.
Problem is that this procedure doesn't account for user option
`org-edit-src-content-indentation'. This option adds de
Achim Gratz writes:
> Bastien writes:
>> Achim, feel free to apply the patch when you have time for this,
>
> Done on maint.
Thanks!
--
Bastien
Hello,
When I attempt to run M-x org-bibtex on a .org file with non-standard
bibtex types that have a tag, they fail to export if
org-bibtex-tags-are-keywords is set to t. This persists even if I add the
bibtex type to org-bibtex-types. I checked, and this problem persists with
a minimal init fil
Hi Matt,
Matt Lundin writes:
> The only minor issue with the fix is that move-beginning-of-line (lines
> 9195-6 of org-agenda.el) is slower than beginning-of-line. It's not so
> bad when you push an item one day forward, but it creates significant
> lag when calling org-agenda-do-date-late sever
Nick Dokos writes:
> Sharon Kimble writes:
>
>> I have a document of helpful emacs hints and tips saved under headings one,
>> like
>> ,
>> | * foobar
>> | ipsum lorens
>> `
>> and they are scattered over the whole document with no sensible pattern to
>> them. Is it possible to be abl
Nick Dokos writes:
> One more (half-)possibility is as follows: produce the tex file and
> compile it not with pdflatex, but with plain latex, producing a DVI
> file. Passing the -src option to the latex invocation inserts "source
> specials" into the DVI file that some DVI viewers (in particular
Sharon Kimble writes:
> I have a document of helpful emacs hints and tips saved under headings one,
> like
> ,
> | * foobar
> | ipsum lorens
> `
> and they are scattered over the whole document with no sensible pattern to
> them. Is it possible to be able to sort them alphabetically? A
I have a document of helpful emacs hints and tips saved under headings one, like
,
| * foobar
| ipsum lorens
`
and they are scattered over the whole document with no sensible pattern to
them. Is it possible to be able to sort them alphabetically? And if so, how
please?
Thanks
Sharon.
--
Hello
In most spreadsheets I know, it is possible to generate easily a column
say starting in 365 ending in 23.[1]
Is there any way to do this in the org spreadsheet, without a loop?
thanks
Uwe Brauer
Footnotes:
[1] (Or in matlab without a loop)
Rainer M Krug writes:
> Hi
>
> I am working on a longish document which will be converted to pdf, and I
> am doing debugging of scripts at the moment.
>
> Therefore I export the document to pdf, and look for errors there. Now I
> have to find the corresponding section in the org file - possible,
Alan Schmitt writes:
> It's working great, thanks a lot!
Applied, then.
Regards,
--
Nicolas Goaziou
Pere Quintana Seguí writes:
> I log most of my work with org-mode. Some of my tasks are repetitive,
> this is, I do them weekly or daily (i.e. empty mail inbox). After many
> years, the logs are very long. As a consequence, marking these tasks as
> done is *very* slow.
>
> Is there a workaround tha
Eric Schulte writes:
> This looks great. Please go ahead and apply this patch to ob-sh.
I just see that this was still sitting in my local branch… pushed to
master.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional
Hi Bastien,
Matt Lundin writes:
> Bastien writes:
>
>> Hi Matt and all,
>>
>> thanks a lot for the detailed investigation -- I revisited the
>> related problems and applied a fix. Please let me know if you
>> encoutner some glitches.
>
> Seems to work fine now. Thanks!
The only minor issue wi
Dnia 2014-03-25, o godz. 16:00:01
Pere Quintana Seguí napisał(a):
> I log most of my work with org-mode. Some of my tasks are repetitive,
> this is, I do them weekly or daily (i.e. empty mail inbox). After many
> years, the logs are very long. As a consequence, marking these tasks
> as done is *v
Achim Gratz writes:
> I've fixed that in master quite some time ago together with some other
> things. I'm not sure how easily it would backport to maint, but IIRC
> that particular bug was just a wrongly quoted macro definition.
Cherry-picked to maint.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#
Bastien writes:
> Achim, feel free to apply the patch when you have time for this,
Done on maint.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada
Rainer M Krug krugs.de> writes:
>
>
> The subject says it all - when I set
>
> #+PROPERTY: eval never-export
>
> the interactive evaluation of R code blocks is disabled. Message:
>
> Evaluation of this R code-block is disabled.
>
[rest deleted]
It works as advertised for me. I copy and p
Rainer M Krug writes:
> Therefore I export the document to pdf, and look for errors there. Now I
> have to find the corresponding section in the org file - possible, but
> tedious.
Not quite what you have in mind and maybe only a half-measure but when I
produce draft latex documents I like to tu
Hi Sébastien,
Sebastien Vauban
writes:
> I do that with:
>
> (add-hook 'text-mode-hook
> (lambda ()
> (message "Turning on Flyspell in buffer `%s'" (buffer-name))
> (flyspell-mode 1)))
>
> Though, as you can see, that has the perverse impact th
Hello,
I use Flyspell in all my text-mode and prog-mode buffers, hence as well
in my Org mode buffers -- as they ultimately derive from Text mode.
I do that with:
--8<---cut here---start->8---
(add-hook 'text-mode-hook
(lambda ()
Nicolas Goaziou writes:
> Hello,
>
> Alan Schmitt writes:
>
>> Using attr_latex would be great.
>
> Here is the patch. WDYT?
It's working great, thanks a lot!
Alan
Rick Frankel writes:
> P.S. Attached for review...
Looks useful indeed, thanks in advance for pushing this!
--
Bastien
On 2014-03-25 08:29, Kelvin Hu wrote:
2014-03-25 16:25 GMT+08:00 Bastien :
I'd try to set `org-html-htmlize-output-type' to nil but I didn't
test. If it does not work, this is a bug.
Thanks for your reply, I have tried this approach, but it reports
"error: (void function nil)".
Per the definit
Thanks for improving the link grabber!
-Anthony
On Sat, Mar 22, 2014 at 8:23 PM, Muchenxuan Tong wrote:
> * contrib/lisp/org-mac-link.el (org-as-mac-chrome-get-frontmost-url):
> Improve AppleScript used for grabbing information from Chrome. Now
> it's shorter and doesn't require switchin
steckerhalter writes:
> I still get an error:
>
> Debugger entered--Lisp error: (args-out-of-range # org-mode-blog/posts/blogging-with-org-mode.org> 0 33)
> match-string(1)
>
> I think you need to provide the original string to match-string, so either
> "let" it or like so:
>
> @@ -1171,7 +1171
I log most of my work with org-mode. Some of my tasks are repetitive,
this is, I do them weekly or daily (i.e. empty mail inbox). After many
years, the logs are very long. As a consequence, marking these tasks as
done is *very* slow.
Is there a workaround that does not involver deleting the logs?
Hello,
Alan Schmitt writes:
> Using attr_latex would be great.
Here is the patch. WDYT?
Regards,
--
Nicolas Goaziou
>From c56bd2754030fd999d50d349ee5282a6c16ba832 Mon Sep 17 00:00:00 2001
From: Nicolas Goaziou
Date: Tue, 25 Mar 2014 15:58:41 +0100
Subject: [PATCH] ox-latex: Allow :options
Hi Nicolas
On Tue, Mar 25, 2014 at 10:08 AM, Nicolas Goaziou wrote:
> Good catch. This should be fixed. Thank you for reporting it.
>
>
I still get an error:
Debugger entered--Lisp error: (args-out-of-range # 0 33)
match-string(1)
I think you need to provide the original string to match-stri
The subject says it all - when I set
#+PROPERTY: eval never-export
the interactive evaluation of R code blocks is disabled. Message:
Evaluation of this R code-block is disabled.
#+PROPERTY: eval always
enables it again.
Let me know if you need more info.
Cheers,
Rainer
Remember to cove
Hi Aaron,
Aaron Ecay writes:
> Hi Alan,
>
> I installed the attached file with M-x package-install-file to avoid
> getting org pulled in via (M)ELPA. The large version number means that
> new versions of org don’t look like upgrades, preventing them from
> overwriting this package. Obviously,
On 2014-03-25 09:31, Dov Grobgeld wrote:
Rick Frankel's ox-slidy.el from:
http://lists.gnu.org/archive/html/emacs-orgmode/2013-10/msg00781.html
[3]
also works really well for me. He is just to modest to let you know
himself. :-)
Actually, i forgot i did the slidy port (it was a quick hack
Hi Anders,
2014ko martxoak 25an, Anders Johansson-ek idatzi zuen:
>
> (I continue in the same thread as this is related)
>
> org-entities has: ("slash" "/" nil "/" "/" "/" "/")
>
> A LaTeX user entering \slash would probably expect to have this exported
> as \slash (which produces a breaking "/",
Rick Frankel's ox-slidy.el from:
http://lists.gnu.org/archive/html/emacs-orgmode/2013-10/msg00781.html
also works really well for me. He is just to modest to let you know
himself. :-)
Regards,
Dov
On Tue, Mar 25, 2014 at 2:28 PM, Rustom Mody wrote:
> On Tue, Mar 25, 2014 at 1:55 PM, Bastien
(I continue in the same thread as this is related)
org-entities has: ("slash" "/" nil "/" "/" "/" "/")
A LaTeX user entering \slash would probably expect to have this exported
as \slash (which produces a breaking "/", not the same thing as just
entering "/" in LaTeX).
So it should rather be
On Tue, Mar 25, 2014 at 11:07:54AM +0100, Rainer M Krug wrote:
> Hi
>
> I am working on a longish document which will be converted to pdf, and I
> am doing debugging of scripts at the moment.
>
> Therefore I export the document to pdf, and look for errors there. Now I
> have to find the correspon
On Tue, Mar 25, 2014 at 1:55 PM, Bastien wrote:
> Rustom Mody writes:
>
>> Bastien: Ive written to Takumi Kinjo
>
> Thanks!
>
> --
> Bastien
Well I should mention that the link mentions Carsten as the author
and Takumi (good deal lower) for 'modifications'.
I let common sense (I have a modest s
[forwarding to mailing-list]
-- Forwarded message --
From: Kelvin Hu
Date: 2014-03-25 18:07 GMT+08:00
Subject: Re: Question: how to disable htmlize during exporting?
To: Bastien
Hi Bastien,
2014-03-25 16:25 GMT+08:00 Bastien :
> I'd try to set `org-html-htmlize-output-type' t
Samuel Wales writes:
> ===
> * org-shiftmetaright on the following folded header will fail to shift
> headline 3
> * bug
> *** 2
> * [[http://www.google.com][google]]
> *** 3
> ===
>
> this is in maint.
Fixed again, thanks and sorry for this regression.
There is still one glitch: the tag in
Nicolas Goaziou writes:
> OK, let's try it. Time will tell.
>
> Installed in 1c1936fbb1f0c42e5c7e1d3c903626aa5993a357.
Thanks,
--
Bastien
On Tuesday 25 Mar 2014 09:48:59 James Harkins wrote:
>
> So, just be patient -- it'll happen, but not until project documentation is
> ready.
>
Sure. Looking forward to the new worg page.
Thanks,
chandan
Hi
I am working on a longish document which will be converted to pdf, and I
am doing debugging of scripts at the moment.
Therefore I export the document to pdf, and look for errors there. Now I
have to find the corresponding section in the org file - possible, but
tedious.
Would it be possibler
Eric Schulte writes:
> Rainer M Krug writes:
>
>> Eric Schulte writes:
>>
>>> Rainer M Krug writes:
>>>
Eric Schulte writes:
> Charles Berry writes:
>
>> John Hendy gmail.com> writes:
>>
>> [deleted]
>>> >
>>> > I think the default behavior should be re
Hello,
Bastien writes:
> That's quite a premature and unstable intuition, but I think it's
> worth trying if your intuition goes in the same direction. Otherwise
> let's just prevent apostrophes.
OK, let's try it. Time will tell.
Installed in 1c1936fbb1f0c42e5c7e1d3c903626aa5993a357.
Regard
Hello,
steckerhalter writes:
> This change:
>
> @@ -1169,5 +1168,10 @@ the file including them will be republished as well."
> - (while (re-search-forward
> - "^#\\+INCLUDE:[ \t]+\"\\([^\t\n\r\"]*\\)\"[ \t]*.*$" nil t)
> - (let* ((included-file (expand-file-name (match-string 1
> -(add-
Dear Yasushi,
Yasushi SHOJI writes:
> Meanwhile, Bastien, would you mind to revert the commit for me?
Done. There is no hurry on this, thanks in advance for your time,
--
Bastien
Rustom Mody writes:
> Bastien: Ive written to Takumi Kinjo
Thanks!
--
Bastien
Hi Kelvin,
Kelvin Hu writes:
> Org is awesome and now I use it as my blogging tool, everything is
> perfect except the source code highlighting. Org uses htmlize.el to
> highlight source code, it's fine, but when I use another theme or on a
> different machine, the generated html(contains source
This change:
@@ -1169,5 +1168,10 @@ the file including them will be republished as well."
- (while (re-search-forward
- "^#\\+INCLUDE:[ \t]+\"\\([^\t\n\r\"]*\\)\"[ \t]*.*$" nil t)
- (let* ((included-file (expand-file-name (match-string 1
-(add-to-list 'included-files-ctime
- (org-publish-
52 matches
Mail list logo
