I've been trying to understand the whole TODO universe, now that I've
finally tackled it. The ability to create all the various states (I haven't
tried SEQ of state groups yet) on an issue entered as a heading in an org
file and then change the status of that heading is marvelous. For example,
I've
Hi Tom,
Tom Gillespie writes:
> As with many things in emacs, I sometimes feel like I'm loosing my
> mind, or loosing track of just exactly what variables are set
You're not losing your mind. After some further testing I find that
you're right, and my understanding of the situation was incorrec
Hi Jack,
As with many things in emacs, I sometimes feel like I'm loosing my
mind, or loosing track of just exactly what variables are set or not
set, but I could swear that for at least the past year when running
#+begin_src bash blocks with C-c C-c and no :results header set the
results are th
Actually, on closer inspection. Shouldn't:
(defalias 'org-highest-priority 'org-priority-highest)
be
(defvaralias ...)?
On Sat, Feb 29, 2020 at 8:09 PM No Wayman
wrote:
> After updating Org, I'm hitting errors for an undefined
> `org-highest-priority'.
> I see that this is an alias for `org-
Hi Tom,
Tom Gillespie writes:
> First a disclosure, I would be very unhappy if option 1 were selected,
> it would require me to make a whole bunch of changes and try to find
> an option to revert to the current default behavior.
Wasn't option 1 already the default behavior, until the changes ma
It seems to me that two separate issues have been mixed up and causing
some confusion here. However, I think it is actually quite simple once
we consider the issues separately.
Issue 1: Defining the meaning of :result value and :result output
Issue 2: Specifying what the default :result setting
Hi all,
Sorry to be late to this thread (and for a wall of text), but as a
heavy user of ob-shell I wanted to chime in. First a disclosure, I
would be very unhappy if option 1 were selected, it would require me
to make a whole bunch of changes and try to find an option to revert
to the current
After updating Org, I'm hitting errors for an undefined
`org-highest-priority'.
I see that this is an alias for `org-priority-highest', but
describe-function (and I'm not sure why it's describe-function vs
describe-variable) dutifully reports:
org-highest-priority is an alias for ‘org-priorit
Hi Bastien,
Thank you again for looking into this. I guess you couldn't find an easy
fix.
This bug is quite the pain, since it gets triggered by the comment-line
function: every time I try to comment something, the cursor goes to the
beginning of the block.
With org-src-tab-acts-natively b
Afaict, the org-block face isn't applied to special blocks. Its
documentation implies it applies to any block.
The relevant function is org-fontify-meta-lines-and-blocks-1.
It may be a simple matter of changing the logic a bit and adding
(add-face-text-property bol-after-beginline beg-of-endli
Hello,
The functionality which I was trying is documented as not supported:
http://www.gnu.org/software/emacs/manual/html_node/org/Column-formulas.html
The left-hand side of a column formula cannot be the name of column, it
must be the numeric column reference or $>.
Regards,
Lester
On Sat, F
Hi Felipe,
It looks like you've made some quite substantial changes to ob-shell.
I think it would be a good idea to split this up into 2 patches, and to
start a new thread for the ob-shell patch.
I'm not as familiar with ob-shell, and it's also had some work
lately. So it'd be good to get some m
Sorry, I was confused about this:
> According to my reading of this thread, most of the commenters were in
> agreement that we should keep the original behavior and return the exit
> code, as we do in 9.3.
Actually, it looks like ":results value" does return the exit code. I
just got confused bec
Hi Bastien,
Bastien writes:
> thanks for your thoughtful inputs. I've now removed the option.
I think it's good you removed the option.
However, it looks like the behavior now is to return the output, instead
of the exit code, when ":results value".
According to my reading of this thread, mo
Hello,
I'm trying to use named fields.
This works:
| ! | col2 | col3 |
| # | abc | abc |
#+TBLFM: $3 = $col2
However, assignment to named field "$col3":
| ! | col2 | col3 |
| # | abc | |
#+TBLFM: $col3 = $col2
... results in error "Unknown field: col3".
I was expecting assignment to the
Hello,
I am encountering an error when using this .org code:
--
| abc | hello |
#+TBLFM: :: $2 = '(org-sbe hello_world)
#+NAME: hello_world
#+BEGIN_SRC shell -n
echo "hello"
#+END_SRC
--
Hi Lester,
Lester Longley writes:
> At https://orgmode.org/manual/Feedback.html:
> I believe that this should be "M-x toggle-debug-on-error ",
> instead of "M-x toggle-debug-or-error ".
Fixed, thanks!
--
Bastien
Hello,
At https://orgmode.org/manual/Feedback.html:
I believe that this should be "M-x toggle-debug-*on*-error ",
instead of "M-x toggle-debug-*or*-error ".
Regards,
Lester
In the meantime I figure out these two options, too. But I decided the effort
seems to high for me. Especially as emacs an minted use different syntactic
categories.
Johannes
Am 01.02.2020 um 14:50 schrieb John Kitchin
mailto:jkitc...@andrew.cmu.edu>>:
My guess is you have two options:
1. Cu
19 matches
Mail list logo
