unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Nicholas Savage" <nick@nicksavage.ca>
To: "Lars Ingebrigtsen" <larsi@gnus.org>
Cc: 39912@debbugs.gnu.org
Subject: bug#39912: "Probably introduced at or before Emacs version ..." link should open NEWS read-only
Date: Tue, 08 Sep 2020 07:26:11 -0400	[thread overview]
Message-ID: <7843e1b5-d84e-4955-a671-90d32121ac81@www.fastmail.com> (raw)
In-Reply-To: <87v9go4kzq.fsf@gnus.org>

Uhh, no! I did not intend to leave out debbugs. Thanks for letting me know (I had got debbugs set up in emacs and didn't realize exactly how it worked).

But back to the matter at hand, now I can reproduce it. I'm going to attempt a fix for this, it seems like a simple enough fix for me to tackle for my first patch here.

On Tue, Sep 8, 2020, at 06:32, Lars Ingebrigtsen wrote:
> (I'm not sure whether you dropped the debbugs address from the Cc here
> on purpose or not, so I'm not adding it back. :-))
> 
> Nick Savage <nick@nicksavage.ca> writes:
> 
> > So that's interesting. I originally did not use 'emacs -Q', but now that
> > I am using that, it still is read-only. I'm also on the current trunk. I
> > don't have a good explanation for that. I also tried it out on one of my
> > other computers that's on 27.1.50 and it was also read only.
> >
> > So in the describe function for describe-function there are two links
> > - one for the defun and one
> > for the NEWS file. Both of those open for me as read-only.
> 
> Yeah, it sounded like Andreas found the reason why -- the installed
> files are normally not writeable by a user.
> 
>





  parent reply	other threads:[~2020-09-08 11:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04 18:22 bug#39912: 27.0.90; Probably introduced at or before Emacs version Felician Nemeth
2020-09-07 19:54 ` bug#39912: "Probably introduced at or before Emacs version ..." link should open NEWS read-only Nicholas Savage
2020-09-07 21:00   ` Lars Ingebrigtsen
2020-09-08  6:59     ` Andreas Schwab
2020-09-08  7:25       ` Stefan Kangas
2020-09-08  7:26         ` Andreas Schwab
2020-09-08 10:26       ` Lars Ingebrigtsen
     [not found]     ` <871rjdi0wb.fsf@nicksavage.ca>
     [not found]       ` <87v9go4kzq.fsf@gnus.org>
2020-09-08 11:26         ` Nicholas Savage [this message]
2020-09-08 13:54           ` Stefan Kangas
2020-09-08 20:27 ` bug#39912: [PATCH] Open describe-function links in view-mode (Bug#39912) Nicholas Savage
2020-09-08 21:01   ` Stefan Kangas
2020-09-08 21:04     ` Lars Ingebrigtsen
2020-09-09  0:14     ` Nicholas Savage
2020-09-09  9:39       ` Lars Ingebrigtsen
2020-09-10  0:43         ` Nicholas Savage
2020-09-10 13:19           ` Lars Ingebrigtsen

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=7843e1b5-d84e-4955-a671-90d32121ac81@www.fastmail.com \
    --to=nick@nicksavage.ca \
    --cc=39912@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 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).