[Date Prev][Date Next][Thread Prev][][Date Index][Thread Index]

Re: Problems with <RET>.

Dear Katsumi,

Greetings, and thank you so much for your quick response. I have
followed your steps from the beginning. I reinstalled emacs-w3m from
cvs using `./configure', `sudo make', and `sudo make install'. In all
of this, I saw no warnings or error messages. (I have saved the output
to a separate file if you should like to see it in the future.) Then I
loaded some libraries as you instructed. After loading w3m-form.el, I
saw this message when tabbing over a form field:

Wrong number of arguments: (lambda (form id name) (let ((plist (aref
form 5)) pair value) (while plist (if (eq id (car plist)) (progn (setq
pair (plist-get (cadr plist) :value)) (if (and pair (string= (car
pair) name)) (progn (setq value (cdr pair) plist nil))))) (setq plist
(cddr plist))) value)), 2

Well, I do not understand that at all, but perhaps you will understand
it? I am hoping that the diagnosis from this code will solve the other
problem of <RET>.

I absolutely love emacs-w3m. I believe it is the BEST text browser,
and I am eternally grateful to everyone who created both w3m and

Hwaen Ch'uqi

On 12/20/15, Katsumi Yamaoka <yamaoka@xxxxxxx> wrote:
> Hi Hwaen,
> In [emacs-w3m : No.12547]
> 	On Sun, 20 Dec 2015 04:44:53 -0500, Hwaen Ch'uqi wrote:
>> I have found that certain buttons in gmail, such as "delete,"
>> no longer respond to <RET>. Instead, I get a message like
>> Invalid function: w3m-anchor
> Hm, for me both RET and the middle mouse click on [Delete] work.
> I doubt your emacs-w3m hasn't been built correctly.  Did you do
> `configure' and `make' normally?  Did you see a warning or an
> error message then?
> [...]
>> I have also been seeing quite often this message, especially when
>> tabbing over a form field
>> Wrong number of arguments: #[(form id name)
> [...]
> Could you get the backtrace again so as to be in human readable
> style?  To do that, in advance, do
> `M-x load-library RET w3m.el RET'  (note: not w3m.elc)
> and do it for w3m-form.el, w3m-proc.el, etc. until the backtrace
> doesn't get a byte-code like this:
>> "^H\306H\307\211^Y^Z\211^[\2038^@^L^K@=\203-^@\310^K\211A@\262^A\311\"\211^R\203-^@
> Regards,