unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: emacs-devel@gnu.org
Subject: Re: How to disable completely org-persist
Date: Sun, 4 Dec 2022 11:14:50 +0100	[thread overview]
Message-ID: <Y4xzGsKVNaDNbhZW@tuxteam.de> (raw)
In-Reply-To: <825716062.1084056.1670146073366@mail1.libero.it>

[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]

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.

Especially given how friendly and helpful Org devels are.

I can understand that software doing things one doesn't like
can be infuriating. But this is free software. You get a
chance to do something about it!

At another point in this thread, Ihor has already stated
that it's possible to add a switch (and actually hinted
at where to look). He even considers adding that switch
later. If you are in a hurry about this...  how about
offering a patch?

Cheers
-- 
t 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2022-12-04 10:14 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 [this message]
2022-12-04 11:57     ` Jean Louis
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=Y4xzGsKVNaDNbhZW@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=emacs-devel@gnu.org \
    /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).