Re: [O] org-table debugging formula - error

this is presumably an entirely transient issue! On Thu, Oct 11, 2018 at 6:07 PM Nicolas Goaziou wrote: > Hello, > > Joe Corneli writes: > > > Hello, > > > > I got an error when debugging the behaviour of a formula. > > > > You'll need: > > > >

[O] org-table debugging formula - error

Hello, I got an error when debugging the behaviour of a formula. You'll need: (setq org-table-formula-debug t) Then with any luck this should allow you to reproduce the error: C-c C-c to run formula. | Task | Estimated Effort | |---+--| |

[O] bug#32722: bug#32722: bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

On Fri, Sep 21 2018, Richard Stallman wrote: > > There are a handful of references to MELPA inside Emacs. Are these to > > be discouraged? > > The question is rather broad, so I can only say "it depends". Whether > a reference to software outside Emacs is good or bad depends on its >

[O] bug#32722: bug#32722: bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

On Thu, Sep 20, 2018 at 2:57 AM Richard Stallman wrote: > The deep problem with the reference to htmlize is that it > blurs the distinction between Emacs itself > and Lisp code that is not part of Emacs. > We need to highlight that distinction, not blur it. There are a handful of references to

Re: [O] Bug: parsing latex ``$\mathit{math}$'' in export [9.0.5 (release_9.0.5-474-g942b62 @ /home/joe/org-mode/lisp/)]

On Fri, May 12, 2017 at 4:37 PM, Nicolas Goaziou wrote: > I'm not convinced it is worth changing the syntax class of "'" or even > making a special case for "'". You can get rid of this problem using > \(P\) instead. Thanks for suggesting this work around, I didn't know

[O] Bug: parsing latex ``$\mathit{math}$'' in export [9.0.5 (release_9.0.5-474-g942b62 @ /home/joe/org-mode/lisp/)]

With the test file as follows: == #+TITLE: example #+AUTHOR:Joe Corneli #+DATE: May 12, 2017 #+DESCRIPTION: example #+LANGUAGE: en #+OPTIONS: H:3 num:t toc:t \n:nil @:t ::t |:t ^:nil -:t f:t *:t <:t #+OPTIONS: Te

Re: [O] Bug: link beginning with parenthesis doesn't work [9.0.5 (release_9.0.5-474-g942b62 @ /home/joe/org-mode/lisp/)]

uot; just means "run a search process", that search process *could* be smart enough to notice that "no coderef was found, maybe the user meant to link to some plain text in parentheses". Then I wouldn't see an error. On Thu, Apr 20, 2017 at 11:12 PM, Nicolas Goaziou <m

Re: [O] Bug: entering range of times [9.0.5 (release_9.0.5-474-g942b62 @ /home/joe/org-mode/lisp/)]

Yeah the problem has been resolved after restarting Emacs. I think the old version had new files but not everything had been loaded, so it was indeed mixed.

Re: [O] Bug: link beginning with parenthesis doesn't work [9.0.5 (release_9.0.5-474-g942b62 @ /home/joe/org-mode/lisp/)]

On Thu, Apr 20, 2017 at 8:35 PM, Nicolas Goaziou > Joe Corneli <holtzerman...@gmail.com> writes: >> Debugger entered--Lisp error: (error "No match for coderef: like this") > > The error message should give you the answer. Links within parenthesis > denote &q

[O] Bug: entering range of times [9.0.5 (release_9.0.5-474-g942b62 @ /home/joe/org-mode/lisp/)]

As I understand it I should be able to enter a range of times using either of the following formats: ** TODO time range <2017-04-21 Fri 15:45-16:45> ** TODO time+date range <2017-04-21 Fri 15:45>--<2017-04-22 Sat 15:45> Docs: http://orgmode.org/manual/Timestamps.html However, using the formats

[O] Bug: link beginning with parenthesis doesn't work [9.0.5 (release_9.0.5-474-g942b62 @ /home/joe/org-mode/lisp/)]

Hello, I've noticed a problem with the link system. Reproduction steps. 1. Find any text in a file, surrounded by parentheses (like this). 2. org-capture the region in parentheses to come up with, e.g., ** TODO This is a problem (like this) [[file:~/test.tex::(like%20this)]] 3. Now try

Re: [O] Fontification of org code block not printed

On Fri, Aug 1, 2014 at 8:31 AM, Francesco Pizzolante f...@missioncriticalit.com wrote: I have to say that I'm surprised about the way this issue has been fixed. Let me tell you why. 1) The fix 'simply' removes a useful Org functionality, which I use for 3 years now, without providing any

[O] Bug: babel config - org-mode fontification error [8.2.10 (release_8.2.10 @ /home/joe/org-mode/lisp/)]

Hello: I have Cider and Clojure Mode installed from Elpa, with Org mode fresh from Git as of today (May 9, 2015). I've provided files below to replicate a bug in babel fontification behavior, having to do with which order things are loaded in. If you save the files below, and run emacs -Q -l

Re: [O] Custom todo-like thing in agenda?

On Sat, Aug 16, 2014 at 3:15 AM, Marcin Borkowski mb...@wmi.amu.edu.pl wrote: Hi all, I was wondering whether something like this is possible. (Well, I'm pretty sure it is, what I don't know whether I'm competent enough to pull it off...) I'd like to be able to create a special agenda view

Re: [O] [PATCH] problem with size of inline images

On Wed, Aug 6, 2014 at 2:22 PM, Nicolas Goaziou m...@nicolasgoaziou.fr wrote: Thanks for your patch. Would you mind providing a commit message and send it again with git format-patch? Don't forget to add TINYCHANGE at its end if you haven't signed FSF papers. Sure. I did sign them quite

[O] [PATCH] problem with size of inline images

Hello: I've noticed a problem around line 19171 of org.el. The size of images is supposed to be controlled by attributes and by `org-image-actual-width'. But it seems like the use of `when', `save-match-data' and `string-to-number' are in the wrong order in this region, so that `(match-string

[O] processing lines before display to agenda

I would find it quite useful to have a variable similar to `org-agenda-prefix-format' that would apply changes to the *contents*, rather than to the *prefix* of agenda items. The nice thing about `org-agenda-prefix-format' is that it allows different formatting for different agenda buffers.

Re: [O] processing lines before display to agenda

Bastien b...@gnu.org writes: I would simply hack the agenda display through a function in `org-agenda-finalize-hook'. You'd rather hide 10 priority cookies from there instead of letting `org-agenda-format-item' process possibly thousands of entries. Thanks for the tip! I already use that