From: "T.V Raman" <raman@google.com>
To: Richard Stallman <rms@gnu.org>
Cc: rpluim@gmail.com, emacs-devel@gnu.org
Subject: Re: auth-sources and EWW
Date: Sat, 19 Sep 2020 07:20:24 -0700 [thread overview]
Message-ID: <p911rixzw47.fsf@google.com> (raw)
In-Reply-To: <E1kJU8Q-0006rW-Cb@fencepost.gnu.org> (Richard Stallman's message of "Sat, 19 Sep 2020 00:06:02 -0400")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 924 bytes --]
Richard Stallman <rms@gnu.org> writes:
That's the problem, witness this cae:
The name of the option is far removed from the place where the symptom
manifests itself, you'd never make the connection unless you were very
close to the code.
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> > This goes back to one of my biggest complaints re custom; once
> > something lands in there, it's well-nigh impossible to figure out what
> > to pull out when something like this bites,
>
> What is the difficulty in doing that?
>
> If you know the name of the option, I'd expect it to be easy to find
> the code for the custom setting, and delete that if you wish to. Why
> isn't this easy?
--
7©4 Id: kg:/m/0285kf1 •0Ü8
next prev parent reply other threads:[~2020-09-19 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 15:19 auth-sources and EWW T.V Raman
2020-09-18 15:31 ` Lars Ingebrigtsen
2020-09-18 15:35 ` Robert Pluim
2020-09-18 15:41 ` T.V Raman
2020-09-18 16:07 ` Robert Pluim
2020-09-18 16:22 ` T.V Raman
2020-09-19 4:06 ` Richard Stallman
2020-09-19 6:26 ` Tim Cross
2020-09-19 14:20 ` T.V Raman [this message]
2020-09-21 8:17 ` Robert Pluim
2020-09-21 14:44 ` T.V Raman
2020-09-21 16:07 ` Robert Pluim
2020-09-22 5:32 ` Tim Cross
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=p911rixzw47.fsf@google.com \
--to=raman@google.com \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=rpluim@gmail.com \
/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).