[multi-tty] Wrong type argument: framep, 0

[multi-tty] Wrong type argument: framep, 0

[csant]

Hi,

just an ordinary emacs *user* here, jumping on the multi-tty branch now 
that it is available in CVS. On one machine everything went fine and 
smooth, but on the other one I end up with:

	$ ./src/emacs -Q
	Wrong type argument: framep, 0

and emacs will not start. When starting with

	$ ./src/emacs -Q -nw

emacs starts and seems to be usable, but I get

	Wrong type argument: framep, 1

in minibuffer at startup. Emacsclient is however totally unsuable (even 
with -t flag): it will start and exit immediately.

Configuration options are:

	Configured for `i686-pc-linux-gnu'.
	
	  Where should the build process find the source code?    
	/home/csant/src/public/apps/tools/emacs
	  What operating system and machine description files should Emacs use?
	        `s/gnu-linux.h' and `m/intel386.h'
	  What compiler should emacs be built with?               gcc -g -O2 
	-Wno-pointer-sign 
	  Should Emacs use the GNU version of malloc?             yes
	      (Using Doug Lea's new malloc from the GNU C Library.)
	  Should Emacs use a relocating allocator for buffers?    yes
	  Should Emacs use mmap(2) for buffer allocation?         no
	  What window system should Emacs use?                    x11
	  What toolkit should Emacs use?                          LUCID
	  Where do we find X Windows header files?                
	/usr/X11R6/include
	  Where do we find X Windows libraries?                   /usr/X11R6/lib
	  Does Emacs use -lXaw3d?                                 yes
	  Does Emacs use -lXpm?                                   yes
	  Does Emacs use -ljpeg?                                  yes
	  Does Emacs use -ltiff?                                  yes
	  Does Emacs use -lungif?                                 no
	  Does Emacs use -lpng?                                   yes
	  Does Emacs use X toolkit scroll bars?                   yes

Compiler is

	$ gcc --version
	gcc (GCC) 4.0.2 20050901 (prerelease) (SUSE Linux)

If there is there any more info you'd need to make any sense out of this 
report, then please keep me CC'ed on the messages: I am not subscribing to 
the list, but am reading it in batches. Also, I hope the message is sent 
to the appropriate list - if not, please accept my apologies and tell me 
where I should address this message to.

Kind regarards,
/c

Re: [multi-tty] Wrong type argument: framep, 0

[Dan Nicolaescu]

csant <csant@csant.info> writes:

  > Hi,
  > 
  > just an ordinary emacs *user* here, jumping on the multi-tty branch now 
  > that it is available in CVS. On one machine everything went fine and 
  > smooth, but on the other one I end up with:
  > 
  > 	$ ./src/emacs -Q
  > 	Wrong type argument: framep, 0
  > 
  > and emacs will not start. When starting with
  > 
  > 	$ ./src/emacs -Q -nw
  > 
  > emacs starts and seems to be usable, but I get
  > 
  > 	Wrong type argument: framep, 1
  > 
  > in minibuffer at startup. Emacsclient is however totally unsuable (even 
  > with -t flag): it will start and exit immediately.

There was an incorrect change installed on the multi-tty branch that
makes it fail that way, you can try this patch.

--- env.el      2007-05-13 15:12:35.000000000 -0700
+++ env.el.~1.38.4.1~   2007-05-13 15:13:52.000000000 -0700
@@ -212,8 +212,7 @@ in the environment list of the selected 
   (let ((value (getenv-internal (if (multibyte-string-p variable)
                                    (encode-coding-string
                                     variable locale-coding-system)
-                                 variable)
-                               frame)))
+                                 variable))))
     (if (and enable-multibyte-characters value)
        (setq value (decode-coding-string value
        locale-coding-system)))
     (when (interactive-p)

You need to make sure that env.el is recompiled, and then run make
again in the src directory to recreate emacs. 
Hopefully the change will be reverted soon in CVS....

Re: [multi-tty] Wrong type argument: framep, 0

[csant]

On Mon, 14 May 2007, Dan Nicolaescu wrote:

> There was an incorrect change installed on the multi-tty branch

Thanks for the reply. Reverting that fix (as was done in CVS) indeed gets 
me back with a "running" emacs. However, I am saddened that my report was 
interpreted as somebody complaining not to have a multi-tty emacs to play 
with. The real reason was to help pinpointing issues - David Kastrup 
correctly identified a deeper issue (yes, that *is* broken in the current, 
running multi-tty) by fixing a first problem. But maybe it is too early to get 
feedback from non-developing users?

Now to get back to something more constructive: where would be the correct 
forum to report multi-tty issues? I thought bug-gnu-emacs to be rather for 
released versions - multi-tty is something quite specific that I don't 
think many non-developping users adopt this early.

/c

Re: [multi-tty] Wrong type argument: framep, 0

[Dan Nicolaescu]

csant <csant@csant.info> writes:

  > On Mon, 14 May 2007, Dan Nicolaescu wrote:
  > 
  > > There was an incorrect change installed on the multi-tty branch
  > 
  > Thanks for the reply. Reverting that fix (as was done in CVS) indeed gets 
  > me back with a "running" emacs. However, I am saddened that my report was 
  > interpreted as somebody complaining not to have a multi-tty emacs to play 
  > with. 

Not at all, it was not interpreted like that. 

  > The real reason was to help pinpointing issues - David Kastrup 
  > correctly identified a deeper issue (yes, that *is* broken in the current, 
  > running multi-tty) by fixing a first problem. But maybe it is too early to get 
  > feedback from non-developing users?

I don't think it is too early, you're welcome to use it.  And if you
can find problems developers will try to fix them, just remember to
send detailed description of the problems you encounter.


  > Now to get back to something more constructive: where would be the correct 
  > forum to report multi-tty issues? I thought bug-gnu-emacs to be rather for 
  > released versions - multi-tty is something quite specific that I don't 
  > think many non-developping users adopt this early.

I am not sure... This list is probably not bad at this point.

Thanks
        --dan