Hi,
with Emacs 26.1 and org-mode version 9.2
(release_9.2-148-g7d638d @ ~/src/org-mode/lisp/),
org-table-iterate does not update tables for me. In the following
table:
| 1 | 1 |
| 2 | 2 |
|---+---|
| 3 | 4 |
#+TBLFM: $2=$1+1::@3$1=vsum(@1..@2)
M-x org-table-iterate does not update the table,
Hi,
when I have this file
=== cut ===
* A
** B
** C
=== cut ===
and set org-archive-location to "::* Archived Tasks", as
recommended in the documentation of this variable. Then, after
doing C-c C-x C-a
---
doc/org.texi | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/doc/org.texi b/doc/org.texi
index 142fa9627..11c6a0f39 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -5263,7 +5263,8 @@ keeping track of your music CDs, where properties could
be things such as
Hi,
consider the following file
* a
** b
:PROPERTIES:
:XXX: 2
:END:
#+COLUMNS: %6XXX{+;%5.1f} %10ITEM
when I move the cursor to item ** b and do C-u C-c C-x C-c
(org-columns with universal argument), then column view is
started for the whole buffer, but
Nicolas Goaziou writes:
> The intent of the check is to warn the user that a columns contains
> invalid values. Applying `string-to-number' unconditionally could give
> strange results for example, with {mean,%.2f}.
I do see your point here. I don't use mean, but it is
it is an invisible change,
probably rewriting the value for XX on a.
Thanks,
Hendrik Tews
Emacs : GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.12)
of 2017-04-29 on trouble, modified by Debian
Package: Org mode version 9.0.7 (release_9.0.7-439-g2906e5 @
/home/tews/src/org-mode/lisp/)
current state
Hi,
Thanks a lot for the quick fix!
I am not sure I understand the check
(when (or (not (string-match-p "[0-9]" value))
(and (string-match-p "[1-9]" value)
(= 0 (string-to-number value
before the error message. Wouldn't it be good enough
for
* a
** b
:PROPERTIES:
:XX: 5.0
:END:
#+COLUMNS: %6XX{+;%6.1f} %10ITEM
Thanks,
Hendrik Tews
Emacs : GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.12)
of 2017-04-29 on trouble, modified by Debian
Package: Org mode version 9.0.7 (release_9.0.7-439-g2906e5 @
/home/tews/src/org-mode
Hi,
is there a specific reason why I can only have one buffer with
column view active?
Would it be sufficient to make org-columns-begin-marker
buffer-local to permit several column views being active at the
same time in different buffers?
Thanks in advance,
Hendrik Tews