unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ken Manheimer <ken.manheimer@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 22452@debbugs.gnu.org
Subject: bug#22452: 24.4; Tramp remote shell fails on remote+sudo+homedir destination
Date: Sun, 24 Jan 2016 14:11:38 -0500	[thread overview]
Message-ID: <CAAT_zTHs5_bWs5MhpoVjTTej+iekHCAvLz8FQ5EdDF313MvjpA@mail.gmail.com> (raw)
In-Reply-To: <87wpqyak4k.fsf@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 1673 bytes --]

On Sun, Jan 24, 2016 at 1:48 PM, Michael Albinus <michael.albinus@gmx.de>
wrote:

> Ken Manheimer <ken.manheimer@gmail.com> writes:
>
> [...]

But the "Selecting deleted buffer" error is hidden very well, likely by
> an `ignore-errors' wrapper. And debugging changes the behaviour.
>

Ignore-errors wrappers are often not sufficiently thought through. An idea
I've often had is that code which legitimately is not interrupted by errors
is therefore, inherently, acting as a kind of "executive", responsible for
running code for something else. (Some common examples are read-eval-print
loops, more sophisticated ones are RPC services, interpreters, dev tools
like debuggers and profilers, etc.) While the executive needs to continue,
the part that's often insufficiently tended is a responsibility to convey
the error to the parties for which it's running the code, so they can react
accordingly.

That's a pretty darn abstract assessment, though, very vague about what
"convey the error" means.  In this case, it may just mean indicating more
about the code context where the error occurred, so that someone debugging
the problem has more leads to track it down. A language that I like for
this kind of thing, Python, provides library calls which expose the
traceback context, so that info can be explicitly included. Not sure if
emacs lisp has similar facilities.

Ken

> Interesting that changing tramp-verbose avoids the problem. Sounds
> > like that, in itself, might be a lead on the problem?
>
> My guess is it is related to Tramp's debug buffer (it won't be touched
> when tramp-verbose is less than 3). I'll continue to dig.
>
> > Ken
>
> Best regards, Michael.
>

[-- Attachment #2: Type: text/html, Size: 2869 bytes --]

  reply	other threads:[~2016-01-24 19:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-24  2:00 bug#22452: 24.4; Tramp remote shell fails on remote+sudo+homedir destination Ken Manheimer
2016-01-24  2:20 ` Ken Manheimer
2016-01-24 17:48 ` Michael Albinus
2016-01-24 18:38   ` Ken Manheimer
2016-01-24 18:48     ` Michael Albinus
2016-01-24 19:11       ` Ken Manheimer [this message]
2016-01-28 12:45     ` Michael Albinus
2016-01-31 17:09       ` Ken Manheimer

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=CAAT_zTHs5_bWs5MhpoVjTTej+iekHCAvLz8FQ5EdDF313MvjpA@mail.gmail.com \
    --to=ken.manheimer@gmail.com \
    --cc=22452@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    /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).