>
> I am reviewing this complex bug report now.
> Looks like everything should be fixed.
> Fixed.
> Let me know if you still see problems.
>
I will do, thanks. I've not seen the problem for months.
On Sat, 15 Feb 2025 at 14:58, Ihor Radchenko wrote:
> Paul Stansell writes:
>
> > Using "C-c + C-y" in the last cell of the table below to sum the column
> > gives the wrong answer because the "2025" part of the date in the hea
|
Previous versions of org mode did not behave this way.
Thanks,
Paul
Emacs : GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.33, cairo version 1.16.0)
of 2024-09-17, modified by Debian
Package: Org mode version 9.8-pre (release_9.7.21-252-g9a3b22 @
~/.emacs.d/org-mode-git/l
>
> This commit should include the updates I mentioned.
> However, "release_9.7.18-205-g0ce4f3.dirty" says that your loaded Org
> mode is "0ce4f3" back from last year. Maybe you just forgot to do make
> autoloads. Maybe you are loading Org from a different folder, not where
> you pulled the latest
>
> > The ".dirty" is because of the patch you asked me to apply.
>
> Ok. I see.
> I thought that you are testing the latest main after my last message
> where I mentioned 3 commits I installed.
>
I thought I was testing the correct version. I thought I pulled the latest
version after you made th
> I think that the easiest way to test things would be simply trying the
> latest main branch.
>
Okay, I'll do that.
> Note that you no longer need the manually installed patch - it has been
> installed upstream already.
>
Okay, thanks
>
> I am afraid that not stripping the newlines will lead to other bugs
> popping up.
>
Okay, thanks for that info.
>
> One weird thing in the above warning is //. Is // really what you see?
>
If you mean the "//" in the following line:
Warning (emacs): Emacs reader failed to read data in
"~/.cache/org-persist//gc-lock.eld". The error was: "End of file during
parsing"
then I would say that it is what I'm real
>
> Looks like the cache was not right.
> Maybe some kind of race condition.
> ... but
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=7999433067
> supposed to fix such case. So, I am confused.
>
> May you please check which Org commit you are on?
>
I'm using the following versio
en
though "#+STARTUP: hideblocks" is specified.
bug3.org :: On opening this file, the content of Section is displayed but
the contents of neither code block are hidden, even though "#+STARTUP:
hideblocks" is specified.
Also, is there any way to hide the output in the "#+R
Hi Ihor,
On opening an org file in emacs I received the warnings in the attached
file.
Paul
Warning (org-element): org-element--cache: Warning(scratch.org): (nil) Cached
element is incorrect in scratch.org. (Cache tic up to date: "yes") Resetting.
If this warning appears regular
Hello,
The attached org file gives an example of output from an octave code block
that is unexpected and inconsistent. The problem is that disp("\n") does
not print a new line. The problem only occurs when the ":session" header
is used.
Paul
Emacs : GNU Emacs 27.1
Hi Ihor,
On Sun, 12 Jan 2025 at 17:22, Paul Stansell wrote:
> Please try and let me know if you still see anything suspicious.
>>
>
It's quite rare, but I'm still receiving these warnings:
Warning (emacs): Emacs reader failed to read data in
"~/.cache/org-persist//
>
> Please try and let me know if you still see anything suspicious.
>
I will do, thanks.
st//gc-lock.eld". The error was: "End of file during
parsing"
I'm not getting all the helpful debugging information.
Paul
>
> Ok. Then, may you try another version of the patch?
>
sure, I've done it.
I just got the attached warnings (with the patch applied) when I opened a
file called scratch.org.
Warning (org-element): org-element--cache: Warning(scratch.org): (nil) Cached
element is incorrect in scratch.org. (Cache tic up to date: "yes") Resetting.
If this warning appears regularly, please r
>
> This looks more reasonable.
> Is this with my patch applied?
>
Yes, the patch is applied.
>
> It's everything that was printed in the Warnings buffer.
>
Actually, maybe it wasn't everything as I didn't scroll up in the buffer!
It just happened again:
Warning (org-element): org-element--cache: Warning(scratch.org): Org
parser error in scratch.org::8756. Resetting.
The error was: (err
>
> It is not the full log, right?
>
It's everything that was printed in the Warnings buffer.
Hi Ihor,
Here are some diagnostic messages I just received when opening a file
called scratch.org:
org-element-cache diagnostics(scratch.org): Recovering persistent cached
element: "(keyword (:standard-properties [1 1 nil nil 22 0 nil top-comment
element t nil nil nil nil # nil nil (section
(:s
>
> May it be that you often have multiple Emacs processes running
> simultaneously and killed by signal?
>
I do typically have multiple Emacs processes running simultaneously, but
I'm not aware that I kill Emacs processes, I either quit Emacs with C-x
C-c, or I click on the "X" in the top right o
c-lock.eld". The error was: "End of file during
parsing"
Paul
arser error in
scratch.org::8756. Resetting.
The error was: (error "Invalid search bound (wrong side of point)")
Backtrace:
nil
Please report this to Org mode mailing list (M-x org-submit-bug-report).
Then I closed the buggy emacs window and tried again and it
Hi Ihor,
Thanks for your advice, it helps a lot. Sorry for submitting
something that wasn't a bug.
Paul
On Thu, 7 Mar 2024 at 13:16, Ihor Radchenko wrote:
> Paul Stansell writes:
>
> > It seems that using ":var d=data" breaks ":colnames yes"
he table (although it read the header as data), and the third code
uses both ":colnames yes" and ":var d=data" but gives the error "Wrong type
argument: sequencep, hline".
Thanks,
Paul
# = Start example =
#+name: data
|--
from a
non-existent file name that consists of all uppercase letters.
Thanks,
Paul
# = Start example =
#+name: data
|+|
| x | y |
|+|
| 111.89 | 88.37 |
| 392.12 | 297.33 |
|+|
This code block works.
Hello Ihor,
Thanks very much for your clarification and advice. I didn't know about
C- or `org-fold-catch-invisible-edits'. Setting
(setq org-fold-catch-invisible-edits 'error)
is very useful.
Paul
ction
below this one (using return or Alt-return) the previous section is
always opened. For sections that aren't the last one can put the cursor at
the start of the next section and press Alt-return to insert a new section
above it without unfolding any sections.
Kind rega
> >> org-hide-drawer-all
> >>
> >
> > I don't seem to have that command. I'm using Org mode
> > release_9.6.10-835-gf3de4c.
>
> It was made into a command in
>
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=13353f1fa34f6f085ffbf142b380af7308f02981
I see, I found the command, i
>
> > In the meantime, is there a command that will close all drawers, even
> those
> > that are open in sections (headings) that are closed? I searched but
> > didn't find anything.
>
> org-hide-drawer-all
>
I don't seem to have that command. I'm using Org mode
release_9.6.10-835-gf3de4c.
I gr
Hello Ihor,
In the meantime, is there a command that will close all drawers, even those
that are open in sections (headings) that are closed? I searched but
didn't find anything.
Thanks,
Paul
ot; in "Subsection 1". Then press
Ctrl-a to go to the beginning of the line. At this point all the drawers
in "Subsection 1" are opened and left open. They are not closed by
Shift-tab visibility cycling.
This doesn't happen with Org mode version 9.5.5 (release_9.5.5).
Tha
Hello Bruno,
> Could allowing column names on the LHS in my first example be put on a
> todo list?
>
It seems to be on a todo list already as the following exists:
- https://list.orgmode.org/877cqwbpa2@runbox.com
Paul
h the column name on the RHS, works
|---+++|
| | 3 | 4 ||
| ^ | c1 | c2 | c3 |
|---+++|
#+TBLFM: $c3 = $c1 + $c2
Could allowing column names on the LHS in my first example be put on a todo
list?
By the way, there is a small error in your example as your $3 should be $4.
Thanks,
Paul
++|
#+TBLFM: $4 = $c1 + $c2
|---+++|
| ! | c1 | c2 | c3 |
| # | 1 | 2 ||
| # | 3 | 4 ||
|---+++|
#+TBLFM: $c3 = $c1 + $c2
Is this a bug?
Thanks,
Paul
===
Emacs : GNU Emacs 28.2 (build 1, x86_64-pc-linux-gnu,
> May you please add
>
> (setq org-element--cache-self-verify 'backtrace)
> (setq org-element--cache-self-verify-frequency 1.0)
>
> to your config?
>
Yes, I'll do that, thanks.
r error
in file.org::1687. Resetting.
The error was: (error "Invalid search bound (wrong side of point)")
Backtrace:
nil
Please report this to Org mode mailing list (M-x
org-submit-bug-report). Disable showing Disable logging
Paul
Backtrace:
nil
Please report this to Org mode mailing list (M-x org-submit-bug-report).
Disable showing Disable logging
When I opened the same file a second time there was no error message.
Paul
Emacs : GNU Emacs 28.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.37, cairo version 1.16.0)
>
> Thanks for reporting!
> Fixed, on main.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=13e4ee737
Great work, thanks!
Hello,
The attached org file gives examples of outputs from octave code blocks
that are unexpected and inconsistent.
The attached bug.org file should be opened with
emacs -Q -l init.el bug.org
The problems only occur when the ":session" header is used.
Paul
Emacs : GNU Emacs 2
>
> Meanwhile, you can set :main no as default header argument for fortran.
>
Thanks for taking another look. I was not aware of ":main no", but it's a
perfectly good fix for my problem.
3.14159 * r**2
return
end function area
END MODULE Circle
end program main
which is broken because org/babel has added the first and last lines.
Thanks,
Paul
Hello,
The attached file is an example of how tangle wraps the Fortran module in
program main
end program main
which prevents the code from compiling.
There are more instructions on how to reproduce the bug in the attached
bug.org file.
Paul
Emacs : GNU Emacs 28.2 (build 1, x86_64-pc
On Sat, 29 Jul 2023 at 09:30, Ihor Radchenko wrote
>
> Thanks for reporting!
> Fixed, on main.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=d38ca5923
It's working fine now. Thanks very much for your quick response!
In org version 9.3, the gnuplot code block below successfully plots the data
in Table1 (which includes a local hyperlink in the last column).
#+name: Table1
| x | y | notes |
|---++|
| 0 | 0 | [[note_1]] |
| 1 | 1 ||
| 2 | 4 ||
<>: a note
#+begin_
ents".
Thanks!
Paul
. orgmode has ignored them in the past (BEFORE 9.6) and I am happy
with that as long as the files do not become corrupted. Can one set the
encoding in orgmode as not having to configure file in real time would be
helpful.
tx Paul
Paul H. Schlesinger MD, PhD
Washington University School of Medicine
roblem has stopped. Can anyone report a similar issue, a cause
and a solution.
Thank you
Paul H. Schlesinger MD, PhD
Washington University School of Medicine
Don't let your models of reality become confused with reality itself.
show and "org" package to install although there are many "org-xxx"
packages. Suggestions appreciated!
Paul H. Schlesinger MD, PhD
Washington University School of Medicine
Don't let your models of reality become confused with reality itself.
On 7/25/22 01:50, Ihor Radchenko wrote:
The conventions sound reasonable, though I do not think that they are
documented in D.6 Tips for Documentation Strings section of the Elisp
manual.
Thanks, I added the following to the Elisp manual to try to fix that:
https://git.savannah.gnu.org/cgit/e
The Emacs doc string convention is to document values as-is when that
is clear, and surrounded by `single quotes' otherwise. For example, a
doc string "(a b c)" stands for a list of symbols, and the doc string
"`a'" stands for a single symbol. The doc string "\\=`a" is typically
not correct for tha
Thanks for the review. Pushed with the changes you suggested.
* lisp/ox-publish.el (org-publish-cache-mtime-of-src):
Rename from org-publish-cache-ctime-of-src, since it
has always cached mtime not ctime. All uses changed.
---
lisp/ox-publish.el | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/lisp/ox-publish.el b/l
d+" are
highlighted automatically. This changes as soon as one modifies
any character.
This seems to be some interference between bug-reference-mode and
Org mode, or maybe even a bug in Emacs itself.
Best,
Paul
On 5/13/22 05:28, Max Nikulin wrote:
Feel free to commit your variant though, I will not object, but I am not
going to update my patch in this way as well.
I'll leave it up to you; it's not a big deal either way.
On 5/12/22 09:55, Max Nikulin wrote:
+(unless (file-exists-p file)
+ (error "File to tangle does not exist: %s" file))
+(when (file-newer-than-file-p file tangled-file)
(org-babel-tangle-file file ...
file-newer-than-file-p succeeds only if FILE exists, so in that case
it'
The comments don't seem to match the code here.
+ (let* ((tangled-file (concat (file-name-sans-extension file) ".el"))
+ (file-mtime (file-attribute-modification-time
+ (file-attributes (file-truename file
+ (tangled-mtime (file-attribute-modification-ti
7 00:00:00 2001
From: Paul Eggert
Date: Sat, 30 Apr 2022 19:27:15 -0700
Subject: [PATCH] org-encode-time compatibility function
* lisp/org/org-compat.el (org-encode-time): New function.
---
lisp/org/org-compat.el | 10 ++
1 file changed, 10 insertions(+)
diff --git a/lisp/org/org-comp
write `org-compile-time' to
treat the case when there were no file prior to the call as that the
file has been updated without comparison of timestamps
Yes, that sounds simpler and better. How about the attached patch?From fbd6561952acf359236afcf7957a197376a18c66 Mon Sep 17 00:00:00 2001
On 4/27/22 09:55, Stefan Monnier wrote:
Instead of rounding the times to whole seconds, wouldn't it make more
sense to check that the difference is larger than 1s?
org-file-newer-than-p is intended to work on filesystems like HFS+ that
store just the seconds part of the last-modified time. Sin
b Mon Sep 17 00:00:00 2001
From: Paul Eggert
Date: Wed, 27 Apr 2022 00:29:26 -0700
Subject: [PATCH] Use org-time-convert-to-integer instead of by hand
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
* lisp/org/org-macs.el (org-file-newer-than-p):
Don’t a
On 4/25/22 08:37, Paul Eggert wrote:
Yes, I plan to omit the patches that were objected to, and install the
rest. Once that's done you should be good to go for Org. (Alas my
workstation died over the weekend, but I should have things up and
running again soon...)
Got my workstati
Yes, I plan to omit the patches that were objected to, and install the
rest. Once that's done you should be good to go for Org. (Alas my
workstation died over the weekend, but I should have things up and
running again soon...)
On 4/23/22 01:25, Ihor Radchenko wrote:
+ (should (string-equal
+ "2022-03-24 23:30:01"
+ (format-time-string
+"%F %T"
+(org-encode-time '(01 30 23 24 03 2022 nil -1 nil)
...
These tests will be executed using system value of TZ. I am not sure if
What appears to be happening here is that the MS-Windows native
timestamp resolution is 1/64th of a second, and your system's clock is
offset by 0.0075 s from an integer boundary. I.e., the timestamps in
increasing order are:
...
1650522862 + 62/64 + 0.0075 = 1650522862.976250
1650522862
On 4/20/22 12:30, Eli Zaretskii wrote:
I see the time samples change in jumps of 15 msec.
Could you give the first part of the output? I would like to see what
the the samples are jumping from and to, and how often they jump.
Something like the following is what I'd hope to see from the fir
On 4/20/22 12:14, Eli Zaretskii wrote:
Sorry, my bad. The result is the same, but I do get printouts. What
do you want to know or see from there?
I want to see what the current_timespec's resolution is, which we should
be able to tell from the debugging output. For example, on my Solaris 10
do internally, and it's also similar to what Emacs's
cal-dst already does (maybe you can look there for ideas), so you'd be
in good company.From f98c3f4426fecf794f47f27aebe1f3b854fb1bfd Mon Sep 17 00:00:00 2001
From: Paul Eggert
Date: Wed, 20 Apr 2022 12:03:19 -0700
Subject: [PATCH]
On 4/20/22 08:07, Max Nikulin wrote:
I have not checked if mktime is a part of
POSIX and C standard.
mktime is part of both the C standard and POSIX. POSIX extends the C
standard by saying that time_t is an integer type (the C standard allows
time_t to be a floating-point type) and that time_t
21-01-31
23:30:00 +0300" if TZ is 10800. And perhaps this is the right way to go
in the long run anyway.From 3d02a8e1192a782a16ffdee4940612f69a12629f Mon Sep 17 00:00:00 2001
From: Paul Eggert
Date: Mon, 18 Apr 2022 13:08:26 -0700
Subject: [PATCH 1/6] Support (encode-time (list s m h D M
this
thread.
It is a messy area but I hope the documentation is clearer now.From f1ba92448d1e573640547c68d9bed89fe5c43da0 Mon Sep 17 00:00:00 2001
From: Paul Eggert
Date: Sat, 16 Apr 2022 18:48:51 -0700
Subject: [PATCH] Document encode-time caveats
MIME-Version: 1.0
Content-Type: text/plain
On 4/15/22 10:23, Max Nikulin wrote:
if you are storing future events bound to wall time then namely
time zone identifier should have precedence.
Although that would make sense for some applications it's not a good
idea in general. For example, if you're scheduling a Zoom meeting you
should
On 4/14/22 06:19, Max Nikulin wrote:
date-time +
"America/Los_Angeles" input should not be reduced to timezone offset in
the output.
It depends on the application. For some applications (e.g., generating
"Date:" lines in email), it is entirely correct to output a timestamp
like "14 Apr 202
On 4/13/22 07:40, Max Nikulin wrote:
I do not see a way to get 23:30 EAT +0300.
Are you asking for a function F where you say, "I want to give F a
possibly-ambiguous decoded local time D, and for F to return all
timestamps that map to D"? If so, encode-time doesn't do that, because
the unde
On 4/11/22 08:22, Max Nikulin wrote:
+ (defmacro org-encode-time (&rest time)
+(pcase (length time)
+ (1 `(encode-time ,(car time)))
+ (6 `(encode-time (list ,@time nil -1 nil)))
+ (9 `(encode-time (list ,@time)))
After seeing this code and thinking about it a bit more I no
Hello Eric,
Thank you very much: that did it :-). Should have known there is always already
a way!
Kind regards,
Paul
Sent from my iPhone
> On 11 Apr 2022, at 13:06, Eric S Fraga wrote:
>
> Hi Paul,
>
>> On Monday, 11 Apr 2022 at 12:08, Paul van Gelder wrote:
>> F
n edit some relevant Elisp code (and propose
that as feature solution), but that may take a long time since I've never done
that in the past.
Anyhow, thanks for this amazing mode and wish you all a good day.
Kind regards,
Paul
functions rather than encode-time+decode-time, which are
best used for time calculations not calendar calculations. (I realize
that fixing this in Org would be nontrivial; perhaps I should file this
"PS" as an Org bug report for whoever has time to fix it)From 094345e10ad45e06f7b3
does keep two of the Org-related parts of dd0727e1ec1; these
parts should work OK with Emacs 25 and so can be merged into Org before
it starts assuming Emacs 27.From 9e07ec56c7e58ee1eb5598dfdd1b772a690daa24 Mon Sep 17 00:00:00 2001
From: Paul Eggert
Date: Tue, 5 Apr 2022 17:48:05 -0700
Subject
When working remotely, a python SRC block with a session and :results set to
output will return a FileNotFoundError.
To reproduce this bug:
1. Open a .org file remotely
2. Insert the following
#+BEGIN_SRC python :results output :session check
print("a")
#+END_SRC
3. org-ctrl-c-ctrl-c in the code b
Oh right, many thanks for both the answers !
On Sat, 20 Jun 2020 at 07:44, Kyle Meyer wrote:
> Paul Bonaud writes:
>
> > In the “Capturing column view” paragraph of the Org-mode manual there is
> no
> > mention of the `:match` parameter which was added in
> >
> ht
://orgmode.org/manual/Capturing-column-view.html
If I can contribute via a patch or git please let me know how I can do
this. I didn't find the source code of the orgmode.org/manual in the wild.
Many thanks for your help and have a nice day,
Paul B.
Hello all!
I have been working to increase my frame use with emacs, and have taken the
following from the manual:
(custom-set-variables
'(display-buffer-base-action
'(
(display-buffer-reuse-window display-buffer-pop-up-frame)
(reusable-
Paul H. Schlesinger MD, PhD
Washington University School of Medicine
Don't let your models of reality become confused with reality itself.
-- Forwarded message -
From: Paul Schlesinger
Date: Sat, Feb 23, 2019 at 12:15 PM
Subject: Preview of latex fragments
To: Orgmode
toggle the image.
Paul Schlesinger
Paul H. Schlesinger MD, PhD
Washington University School of Medicine
Don't let your models of reality become confused with reality itself.
The old approach required Lisp code to use (current-time)
explicitly when calling other primitives, e.g., (float-time
(current-time)). The new approach fakes all the primitives,
so that Lisp code can now use expressions like plain (float-time).
* testing/org-test.el (org-test-at-time): New macro.
t("here")
even.append(("this should be in the list as well",))
even
#+END_SRC
Emacs : GNU Emacs 25.2.2 (x86_64-pc-linux-gnu, GTK+ Version 3.22.21)
of 2017-09-22, modified by Debian
Package: Org mode version 9.1.14 (9.1.14-1-g4931fc-elpa @
/home/paul/org-mode/
On 03/28/2018 12:33 PM, Paul Eggert wrote:
Unfortunately the new org code contains the expression (encode-time 0
0 0 0 0 -5), which won't work on Emacs platforms where time_t is
32 bits or is unsigned, since such platforms cannot represent a time_t
value corresponding to the year -
I see that the exact same "bug" was reported at the start of 2016 by
David Bremner. Personally, I feel that fewer people would be confused
by this if the default value was set to "untilnow".
I also realised that the full list of values that I can use for
org-clock-display-default-range is describ
not
simply over the full range of clocked times in a heading.
Kind regards,
Paul
On 7 January 2018 at 00:32, Nicolas Goaziou wrote:
> Hello,
>
> Paul Stansell writes:
>
> > The sum of the clock time seems to be summing just times in the current
> > year. In the examp
Hello,
The sum of the clock time seems to be summing just times in the current
year. In the example below typing C-c C-x C-d in the "Example" section
displays "1:00" instead of "2:00" on the heading line. The clocktable
computes the sum correctly as "2:00".
Thanks
# Start Example -
Turns out that the issue was caused by trying to disable a flycheck checker
using the org edit src hook
On Mon, Dec 18, 2017, 6:30 AM Nicolas Goaziou
wrote:
> Hello,
>
> Paul Davis writes:
>
> > Using ~C-c '~ to edit a src block works as expected, but if I make
&
Hi I was trying to use the new :show-process header argument for clojure in
Org mode version 9.1.4 (9.1.4-13-g84cb63-elpaplus @
(org-plus-contrib-20171218/)
I get the following error:
org-babel-insert-result: Wrong type argument: markerp, nil
lpaplus @
/home/paul/.emacs.d/elpa/org-plus-contrib-20171211/)
current state:
==
(setq
org-tab-first-hook '(org-babel-hide-result-toggle-maybe
org-babel-header-arg-expand)
outline-minor-mode-hook '((lambda nil (make-local-variable (quote
smart-outline-cut)) (setq smart-outl
>>> >>> Traceback (most recent call last):
File "", line 1, in
NameError: name '_' is not defined
>>> >>> >>> 'org_babel_python_eoe'
>>>
However, the following code block does not give an error:
| 2 | This=> |
| 3 | three |
|---+|
and
|---+--|
| | <6> |
| 1 | one |
| 2 | This is a long chunk of text |
| 3 | three|
|---+--|
Thanks,
Paul
E
Hello,
Latex math mode is not set in a footnote when exporting an org file to
tex or pdf. Below and attached is a simple example.
Thanks
---cut here--
* Example
When exporting to pdf math $\hat{x}$ is okay in the main text but
not in this footnote.[f
On Thu, 15 Jun 2017, at 03:18 AM, Kaushal Modi wrote:
> On Wed, Jun 14, 2017 at 1:02 PM Bastien Guerry wrote:
>
> > The question is: why this patch in the first place? Paul authored it
> > and I committed it, so I should know--but I don't. Maybe Paul know or
> >
There appear to be more than just one of us.
paul
On Mon, Jan 30, 2017 at 11:26 AM, Kenneth Jacker
wrote:
>
> there are people besides just me that use it :)
>
>
> Yes ... like me!
>
> *OrgMode* is one of my most used "systems".
>
> Getting *MobileOrg*
1 - 100 of 582 matches
Mail list logo
