From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#28785: 27.0.50; Wishlist: There should be a mode for .netrc and .authinfo Date: Sat, 21 Sep 2019 11:10:22 +0200 Message-ID: <87woe2ypz5.fsf@gnus.org> References: <871rwa10wk.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="114587"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: 28785@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Sep 21 11:11:13 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iBbQ7-000Tfn-CC for geb-bug-gnu-emacs@m.gmane.org; Sat, 21 Sep 2019 11:11:11 +0200 Original-Received: from localhost ([::1]:40390 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iBbQ6-0001Dl-9D for geb-bug-gnu-emacs@m.gmane.org; Sat, 21 Sep 2019 05:11:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39718) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iBbPz-0001DV-Sl for bug-gnu-emacs@gnu.org; Sat, 21 Sep 2019 05:11:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iBbPy-0007ui-J4 for bug-gnu-emacs@gnu.org; Sat, 21 Sep 2019 05:11:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:50290) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iBbPy-0007uc-FX for bug-gnu-emacs@gnu.org; Sat, 21 Sep 2019 05:11:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iBbPy-0002St-9L for bug-gnu-emacs@gnu.org; Sat, 21 Sep 2019 05:11:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 21 Sep 2019 09:11:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 28785 X-GNU-PR-Package: emacs Original-Received: via spool by 28785-submit@debbugs.gnu.org id=B28785.15690570309424 (code B ref 28785); Sat, 21 Sep 2019 09:11:02 +0000 Original-Received: (at 28785) by debbugs.gnu.org; 21 Sep 2019 09:10:30 +0000 Original-Received: from localhost ([127.0.0.1]:59108 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iBbPR-0002Rw-Sz for submit@debbugs.gnu.org; Sat, 21 Sep 2019 05:10:30 -0400 Original-Received: from quimby.gnus.org ([80.91.231.51]:49794) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iBbPQ-0002Rn-1i for 28785@debbugs.gnu.org; Sat, 21 Sep 2019 05:10:28 -0400 Original-Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=marnie) by quimby.gnus.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iBbPK-0000CZ-NF for 28785@debbugs.gnu.org; Sat, 21 Sep 2019 11:10:26 +0200 In-Reply-To: <871rwa10wk.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 21 Sep 2019 10:58:19 +0200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:166856 Archived-At: Lars Ingebrigtsen writes: > Does anybody remember whether this really was the conclusion, or whether > there's another framework for hiding stuff that should be used? Found it. Ted asked and Stefan M answered. So the solution is to extend reveal-mode with a `display' thing and then use that. > > Right. I tried to find a standard way to do the hiding part, especially > > one that would work with `reveal-mode`, and failed. Would doing it with > > `jit-lock-register` work with `reveal-mode` automatically? > reveal-mode doesn't care which mechanism you use to add the `invisible` > property, so doing it with jit-lock-register will neither help nor > hinder the use of reveal-mode. > The current constraint of reveal-mode is that it only works for text > hidden using the `invisible' property, and only if that property is > applied via an overlay. > It might very well be too restrictive for your use case (e.g. you might > prefer to hide the passwords by replacing them with ******* or something > like that, which requires the use of a `display` rather than > `invisible` property, and you might also prefer to use a text-property > rather than an overlay), but my suggestion was to extend reveal-mode to > be able to handle such cases. > You can see in reveal-open-new-overlays what tests are applied before > "opening" an overlay: > (and inv > ;; There's an `invisible' property. Make sure it's > ;; actually invisible, and ellipsized. > (and (consp buffer-invisibility-spec) > (cdr (assq inv buffer-invisibility-spec))) > (or (setq open > (or (overlay-get ol 'reveal-toggle-invisible) > (and (symbolp inv) > (get inv 'reveal-toggle-invisible)) > (overlay-get ol 'isearch-open-invisible-temporary))) > (overlay-get ol 'isearch-open-invisible) > (and (consp buffer-invisibility-spec) > (cdr (assq inv buffer-invisibility-spec)))) > (overlay-put ol 'reveal-invisible inv)) > It could test for the presence of the `display` property (and maybe > check for the presence of a reveal-specific property like > reveal-toggle-invisible above, so that it doesn't reveal any and all > `display` properties but only those that were designed to be revealed). > Stefan -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no