From: Bastien <bzg@altern.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] `org-load-noerror-mustsuffix´ is not defined, introduced by 5484a33b
Date: Sat, 12 Jan 2013 17:06:08 +0100 [thread overview]
Message-ID: <87bocucrnz.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87a9seh050.fsf@Rainer.invalid> (Achim Gratz's message of "Sat, 12 Jan 2013 16:49:31 +0100")
> No, not at all. That's what reverting db7ece9fa2 does. And if you
> really want to flip off folks with strange Org installations instead of
> helping them survive, then leave out that third "t", i.e. just change
> that line to:
Please lower your tone.
I'm not "flipping off" anybody.
> In other words something like this:
>
> (require 'org-compat)
> (require 'org-macs)
> (add-to-list 'load-path "/home/org-mode/lisp")
> (require 'org)
Anybody can see this is wrong, and instead of letting users shoot
themselves in the foot with a wrong setup, we should educate them to
use a correct one like
(add-to-list 'load-path "/home/org-mode/lisp")
(require 'org)
which shouldn't be that hard.
> will result in a correctly loaded Org with the patch, but yield either a
> not-correctly working Org (silently wrong and producing strange results
> that nobody can reproduce) or a failure to load Org at all (you get an
> error at least) without it.
I'm fine with not fixing this right now.
> It is also an experiment to determine if Emacs should do something like
> this (by default or as an option) and how to best implement it. Even if
> it eventually moved into Emacs however, Org would still have to
> implement it as a workaround for older Emacsen that don't have it.
Again, I'm fine with any experiment that can be done on Emacs side so
that Emacs autoloads are always correct. But I won't allow a patch
that advise `require' in Org for now.
Thanks,
--
Bastien
next prev parent reply other threads:[~2013-01-12 16:06 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 16:08 [BUG] `org-load-noerror-mustsuffix´ is not defined, introduced by 5484a33b Eric Schulte
2013-01-10 16:29 ` Bastien
2013-01-10 16:38 ` Eric Schulte
2013-01-10 17:09 ` Bastien
2013-01-10 17:29 ` Eric Schulte
2013-01-10 17:44 ` Nick Dokos
2013-01-10 18:13 ` Eric Schulte
2013-01-10 18:44 ` Bastien
2013-01-10 19:28 ` Eric Schulte
2013-01-10 20:05 ` Bastien
2013-01-10 21:12 ` Eric Schulte
2013-01-10 22:24 ` Eric Schulte
2013-01-10 22:45 ` Nick Dokos
2013-01-10 23:05 ` Bastien
2013-01-10 23:44 ` Eric Schulte
2013-01-11 7:04 ` Bastien
2013-01-11 12:28 ` Bastien
2013-01-11 15:41 ` Eric Schulte
2013-01-11 16:31 ` Bastien
2013-01-11 16:50 ` Achim Gratz
2013-01-11 16:40 ` Achim Gratz
2013-01-11 16:58 ` Bastien
2013-01-11 17:04 ` Achim Gratz
2013-01-11 17:23 ` Bastien
2013-01-11 19:30 ` Achim Gratz
2013-01-11 20:19 ` Eric Schulte
2013-01-11 20:48 ` Achim Gratz
2013-01-12 6:57 ` Bastien
2013-01-12 6:56 ` Bastien
2013-01-12 7:44 ` Achim Gratz
2013-01-12 8:40 ` Bastien
2013-01-12 10:27 ` Achim Gratz
2013-01-12 11:03 ` Achim Gratz
2013-01-12 13:35 ` Bastien
2013-01-12 15:49 ` Achim Gratz
2013-01-12 16:06 ` Bastien [this message]
2013-01-12 16:17 ` Achim Gratz
2013-01-12 16:12 ` Bastien
2013-01-12 16:24 ` Achim Gratz
2013-01-11 9:12 ` Achim Gratz
2013-01-10 23:27 ` Stelian Iancu
2013-01-10 23:27 ` Stelian Iancu
2013-01-10 20:09 ` Achim Gratz
2013-01-10 22:30 ` Eric Schulte
2013-01-10 22:55 ` Nick Dokos
2013-01-11 8:58 ` Achim Gratz
2013-01-10 19:37 ` Nick Dokos
2013-01-10 19:47 ` Achim Gratz
2013-01-13 22:08 ` Thorsten Jolitz
2013-01-13 23:06 ` Stelian Iancu
2013-01-13 23:22 ` Thorsten Jolitz
2013-01-14 21:44 ` Eric Schulte
2013-01-15 1:29 ` Thorsten Jolitz
2013-01-15 6:07 ` Eric Schulte
2013-01-15 11:31 ` Thorsten Jolitz
2013-01-15 12:22 ` Nick Dokos
2013-01-15 13:36 ` Thorsten Jolitz
2013-01-15 13:49 ` Nick Dokos
2013-01-15 18:58 ` Achim Gratz
2013-01-15 20:17 ` Thorsten Jolitz
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bocucrnz.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=Stromeko@nexgo.de \
--cc=emacs-orgmode@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/org-mode.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).