From: Ted Zlatanov <tzz@lifelogs.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 28785@debbugs.gnu.org
Subject: bug#28785: 27.0.50; Wishlist: There should be a mode for .netrc and .authinfo
Date: Thu, 21 Dec 2017 10:02:37 -0500 [thread overview]
Message-ID: <87fu84gm42.fsf@lifelogs.com> (raw)
In-Reply-To: <m31sm9lxfy.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 11 Oct 2017 13:45:53 +0200")
On Wed, 11 Oct 2017 13:45:53 +0200 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> This mode would just be the normal fundamental mode (or conf mode or
LI> something), but it would add `display' properties on all password tokens
LI> so that these wouldn't be immediately visible to passers-by while you're
LI> editing the file.
LI> And a command to toggle the visibility, I guess.
LI> Hm... perhaps a general minor mode that hides certain bits based on a
LI> syntax of some sort?
One of my big annoyances with netrc format is that it's badly defined
(previously discussed on bug list). So I implemented JSON support in
auth-source. Thus we can now use something like
https://github.com/DamienCassou/json-navigator as the UI, if the default
JSON editing is not good enough (for me it is).
The token display is a great idea and IMO it should be a minor mode,
operating like prettify-symbols mode. Then it could be used in any major
mode that tags its secret data appropriately, not just netrc.
WDYT?
Ted
next prev parent reply other threads:[~2017-12-21 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 11:45 bug#28785: 27.0.50; Wishlist: There should be a mode for .netrc and .authinfo Lars Ingebrigtsen
2017-12-21 15:02 ` Ted Zlatanov [this message]
2017-12-21 15:10 ` Lars Ingebrigtsen
2018-04-13 23:19 ` Lars Ingebrigtsen
2019-09-21 8:58 ` Lars Ingebrigtsen
2019-09-21 9:10 ` Lars Ingebrigtsen
2019-09-21 10:06 ` Lars Ingebrigtsen
2019-09-21 9:19 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fu84gm42.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=28785@debbugs.gnu.org \
--cc=larsi@gnus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.