public inbox for gnats-prs@sourceware.org
help / color / mirror / Atom feed
From: andrewg@platypuspartners.com
To: gnats-gnats@sourceware.cygnus.com
Subject: gnats/250: edit-pr in Emacs generates errors and does not display edit buffer
Date: Tue, 28 Aug 2001 19:54:00 -0000 [thread overview]
Message-ID: <20010829025105.23866.qmail@sourceware.cygnus.com> (raw)
>Number: 250
>Category: gnats
>Synopsis: edit-pr in Emacs generates errors and does not display edit buffer
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Aug 28 19:54:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Andrew Gray
>Release: gnats-3.113.1
>Organization:
>Environment:
Red Hat Linux release 7.1, kernel 2.4.2-2, i586,
Emacs 20.7.1
>Description:
After entering M-x edit-pr, then the number of a valid PR,
The message "error in process sentinel: Opening input file:
no such file or directory, /usr/" appears in the command
buffer and the PR does not appear. Looking in the *Messages*
buffer reveals the following:
Fetching PR 200 in background.
Parsing the categories file...
error in process sentinel: Opening input file: no such file or directory, /usr/local/share/gnats/gnats-db/gnats-adm/cat [2 times]
A buffer named "*edit-pr 200*" exists and has the PR,
but it is in Fundamental mode, so it not useful for editting
the PR.
>How-To-Repeat:
Start Emacs.
M-x edit-pr
200<Return>
>Fix:
I have attached a patch to the gnats-el.in file that fixes
this problem in my environment. The patch simply restores
some code that was commented out. Looking at the ChangeLog
this change appears to have been made by Jason Merrill
<jason@redhat.com> on 2000-07-12. Unfortunately I don't
understand how the gnats Lisp code works, so it is not
obvious to me that the commented out code is incomplete
as the comment asserts. Also, I do not know how my patch
will affect other environments or scenarios.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="patchfile.out"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="patchfile.out"
SW5kZXg6IGduYXRzLWVsLmluCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KUkNTIGZpbGU6IC9jdnMvZ25hdHMvZ25hdHMv
Z25hdHMvQXR0aWMvZ25hdHMtZWwuaW4sdgpyZXRyaWV2aW5nIHJldmlzaW9uIDEuMS4xLjIuNi4y
CmRpZmYgLXUgLXAgLXIxLjEuMS4yLjYuMiBnbmF0cy1lbC5pbgotLS0gZ25hdHMtZWwuaW4JMjAw
MC8wNy8xNyAyMzoxNzo0NwkxLjEuMS4yLjYuMgorKysgZ25hdHMtZWwuaW4JMjAwMS8wOC8yOSAw
MjoxOTo0OQpAQCAtMTQ0OSwxNCArMTQ0OSwxMCBAQCBpZiBuZWVkZWQuIgogICAgICAgICAgIChz
ZXQtYnVmZmVyIGJ1ZikKICAgICAgICAgICAoc2V0cSBidWZmZXItcmVhZC1vbmx5IG5pbCkKICAg
ICAgICAgICAoZXJhc2UtYnVmZmVyKQotOzsgVGhpcyBpcyBvYnZpb3VzbHkgaW5jb21wbGV0ZS4g
IFRoZSBjdXJyZW50IHN0YXRlIGlzIHJhdGhlciBzdWJvcHRpbWFsLAotOzsgYnV0IHVzYWJsZTsg
Y29weSB0aGUgYXBwcm9wcmlhdGUgZmlsZSBmcm9tIHRoZSByZW1vdGUgaG9zdC4gIFRoZSBjb21t
ZW50ZWQKLTs7IGNvZGUgaXMganVzdCBicm9rZW4uCi07ICAgICAgICAgIChpbnNlcnQtZmlsZS1j
b250ZW50cwotOyAgICAgICAgICAgKGlmIGduYXRzOm5ldHdvcmstc2VydmVyCi07ICAgICAgICAg
ICAgICAgKGNvbmNhdCBibiAiLiIgZmlsZW5hbWUpCi07ICAgICAgICAgICAgIGZpbGUpKQotICAg
ICAgIChpbnNlcnQtZmlsZS1jb250ZW50cyBmaWxlKQorICAgICAgICAgIChpbnNlcnQtZmlsZS1j
b250ZW50cworICAgICAgICAgICAoaWYgZ25hdHM6bmV0d29yay1zZXJ2ZXIKKyAgICAgICAgICAg
ICAgIChjb25jYXQgYm4gIi4iIGZpbGVuYW1lKQorICAgICAgICAgICAgIGZpbGUpKQogICAgICAg
ICAgIChzZXRxIHJlc3VsdCAoZ25hdHM6OmdldC1hbGlzdCBidWYpKQogICAgICAgICAgIChraWxs
LWJ1ZmZlciBidWYpKSkKICAgICAgIChtZXNzYWdlICJQYXJzaW5nIHRoZSAlcyBmaWxlLi4uZG9u
ZS4iIGRlc2MpKQo=
reply other threads:[~2001-08-28 19:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010829025105.23866.qmail@sourceware.cygnus.com \
--to=andrewg@platypuspartners.com \
--cc=gnats-gnats@sourceware.cygnus.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.
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).