Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: Unable to login because can't read password from terminal.
Date: Mon, 23 Jun 2003 14:58:14 +0200	[thread overview]
Message-ID: <84r85lkl21.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <m3smq1ktlg.fsf@c213-89-193-148.cm-upc.chello.se>

Mats Löfdahl <xyzzy@chello.se> writes:

> I did the edebug-defun thing and then went back and looked at the
> sample message again. But the debug thing was never triggered. The
> error string is not present in w3m.el. Maybe if it's generated by w3m
> the program, rather than w3m the emacs interface, there never is an
> emacs-lisp error?  Should I try the edebug-defun trick on
> call-process-region, too?

You should try to edebug-defun all functions from w3m that might call
processes.  Yes, besides start-process and call-process, this also
includes call-process-region.  But I thought that Emacs starts w3m
just once and then sends it commands?  Well, it's also possible that
Emacs uses call-process-region to start w3m and send it some commands.

-- 
This line is not blank.


      parent reply	other threads:[~2003-06-23 12:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-21 12:41 Mats Löfdahl
     [not found] ` <84d6h77dka.fsf@lucy.is.informatik.uni-duisburg.de>
     [not found]   ` <m3el1n7bz1.fsf@c213-89-193-148.cm-upc.chello.se>
     [not found]     ` <848yrv44i0.fsf@lucy.is.informatik.uni-duisburg.de>
     [not found]       ` <m3d6h7kyux.fsf@c213-89-193-148.cm-upc.chello.se>
     [not found]         ` <848yrvw6tz.fsf@lucy.is.informatik.uni-duisburg.de>
     [not found]           ` <m34r2jkxe3.fsf@c213-89-193-148.cm-upc.chello.se>
     [not found]             ` <843ci2qflf.fsf@lucy.is.informatik.uni-duisburg.de>
     [not found]               ` <m3smq1ktlg.fsf@c213-89-193-148.cm-upc.chello.se>
2003-06-23 12:58                 ` Kai Großjohann [this message]

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=84r85lkl21.fsf@lucy.is.informatik.uni-duisburg.de \
    --to=kai.grossjohann@gmx.net \
    /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 NNTP newsgroup(s).