From: Jean Louis <bugs@gnu.support>
To: tomas@tuxteam.de
Cc: emacs-devel@gnu.org
Subject: Re: How to disable completely org-persist
Date: Sun, 4 Dec 2022 14:57:38 +0300 [thread overview]
Message-ID: <Y4yLMiOrVToPAiIN@protected.localdomain> (raw)
In-Reply-To: <Y4xzGsKVNaDNbhZW@tuxteam.de>
* tomas@tuxteam.de <tomas@tuxteam.de> [2022-12-04 13:16]:
> On Sun, Dec 04, 2022 at 10:27:53AM +0100, Angelo Graziosi wrote:
> >
> > Ihor Radchenko on emacs-orgmode wrote:
> >
> > > That being said, it should not be a big deal to allow disabling
> > > org-persist when desired. In fact, org-persist is already
> > > auto-disabled when using emacs -Q. I can add a user switch
> > > on top.
> >
> > I wonder what kind of answer is this.. Also not using ORG mode at all fixes the issue..
>
> Angelo: I do share your wish. I still think we all can do
> without the hostility you express that wish. From where
> I stand, it is horribly unjust. Ihor and the other folks
> are doing a lot of work we can just profit from.
I see that above as funny misunderstanding of course, not
hostility. How can that be hostility? Wondering about the answer it
means there is some missing information which was clarified by Ihor,
and there is bit irony, which I welcome. Irony and wondering are not
hostilities.
Just my observation.
It is funny.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2022-12-04 11:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1158097067.265983.1670026787291@mail1.libero.it>
2022-12-04 9:27 ` How to disable completely org-persist Angelo Graziosi
2022-12-04 4:34 ` Ihor Radchenko
2022-12-04 9:32 ` Angelo Graziosi
2022-12-04 10:14 ` tomas
2022-12-04 11:57 ` Jean Louis [this message]
2022-12-04 12:37 ` Eli Zaretskii
2022-12-04 12:46 ` John ff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y4yLMiOrVToPAiIN@protected.localdomain \
--to=bugs@gnu.support \
--cc=emacs-devel@gnu.org \
--cc=tomas@tuxteam.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).