GNU bug report logs -
#35882
`emacsclient -t' breaks a terminal when try to open not a readable file
Previous Next
Reported by: vi <at> teknik.io
Date: Fri, 24 May 2019 14:04:02 UTC
Severity: normal
Merged with 24566
Found in version 25.2.50
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 35882 in the body.
You can then email your comments to 35882 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#35882
; Package
emacs
.
(Fri, 24 May 2019 14:04:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
vi <at> teknik.io
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Fri, 24 May 2019 14:04:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
After typing `emacsclient -t <filename>' where <filename> doesn't have a read permission for user,
I stop seeing the text I am typing in a terminal, also broken formatting of output text.
`stty sane' fixes that.
[Message part 2 (text/html, inline)]
Merged 24566 35882.
Request was from
npostavs <at> gmail.com
to
control <at> debbugs.gnu.org
.
(Mon, 27 May 2019 14:20:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#35882
; Package
emacs
.
(Sat, 08 Jun 2019 07:39:02 GMT)
Full text and
rfc822 format available.
Message #10 received at 35882 <at> debbugs.gnu.org (full text, mbox):
> Date: Fri, 24 May 2019 12:43:40 +0000
> From: vi <at> teknik.io
>
> After typing `emacsclient -t <filename>' where <filename> doesn't have a read permission for user,
> I stop seeing the text I am typing in a terminal, also broken formatting of output text.
> `stty sane' fixes that.
I believe this problem is already indirectly solved on the master
branch, since we now visit the file before creating the frame. What I
see here with the master branch code is an error message saying
"*ERROR*: File is not readable: FILE", and the client exits without
leaving the terminal in a messed-up state.
Would it be possible for you to try the master branch and see if it
indeed solves the problem?
Thanks.
Reply sent
to
Eli Zaretskii <eliz <at> gnu.org>
:
You have taken responsibility.
(Wed, 19 Jun 2019 02:40:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
vi <at> teknik.io
:
bug acknowledged by developer.
(Wed, 19 Jun 2019 02:40:03 GMT)
Full text and
rfc822 format available.
Message #15 received at 35882-done <at> debbugs.gnu.org (full text, mbox):
> Date: Tue, 18 Jun 2019 19:53:59 +0000
> From: vi <at> teknik.io
>
> > I believe this problem is already indirectly solved on the master
> > branch, since we now visit the file before creating the frame. What I
> > see here with the master branch code is an error message saying
> > "*ERROR*: File is not readable: FILE", and the client exits without
> > leaving the terminal in a messed-up state.
> >
> > Would it be possible for you to try the master branch and see if it
> > indeed solves the problem?
> >
> > Thanks.
>
>
> I tried master branch. Problem solved.
Thanks, closing.
Reply sent
to
Eli Zaretskii <eliz <at> gnu.org>
:
You have taken responsibility.
(Wed, 19 Jun 2019 02:40:03 GMT)
Full text and
rfc822 format available.
Notification sent
to
Han Boetes <han <at> boetes.org>
:
bug acknowledged by developer.
(Wed, 19 Jun 2019 02:40:03 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Wed, 17 Jul 2019 11:24:06 GMT)
Full text and
rfc822 format available.
This bug report was last modified 5 years and 333 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.