Fw: Problem with eshell

Fw: Problem with eshell

[Adolfo De Unanue]

Lennart,

I did not download to a new directory, but I always do cvs up, and
everything, and this is the first time I have problems :(

I followed the build instructions, even I tried mak distclean, make
maintainer-clean, etc, etc i.e.

Before the tries, I ran all this tries with a brand new -and empty, of 
course- .emacs

first try:

cvs up
./configure
make
sudo make install

(problems with eshell: Invalid assertion.... Squares instead some words
in all the files)

second try:
cvs up
make distclean
./configure
make
sudo make install

(same)

third try:
cvs up
make maintainer-clean
./configure
make bootstrap
sudo make install

(now eshell throes a segmentation fault)


running out of options...

:(

Adolfo


El Mon, 06 Oct 2008 17:51:11 +0200
"Lennart Borgman (gmail)" <lennart.borgman@gmail.com> escribió:

> Did you download to a new directory? Did you follow the build
> instructions?
> 
> Adolfo De Unanue wrote:
> > Hi Pete,
> > 
> > I downloaded -again- the version from cvs.
> > Same error :(
> > 
> > Adolfo
> > 
> > 
> > 
> > 
> > El Mon, 6 Oct 2008 11:48:39 +0200
> > Peter Dyballa <Peter_Dyballa@Web.DE> escribió:
> > 
> >> Am 06.10.2008 um 04:12 schrieb Adolfo De Unanue:
> >>
> >>> Any hints?
> >>
> >> Update from CVS. The code from last weekend works fine.
> >>
> >> --
> >> Greetings
> >>
> >>    Pete
> >>
> >> They that can give up essential liberty to obtain a little
> >> temporary safety deserve neither liberty nor safety.
> >> 		-Benjamin Franklin, Historical Review of
> >> Pennsylvania.
> >>
> >>
> >>
> > 
> > 
> > 

Re: Fw: Problem with eshell

[Lennart Borgman (gmail)]

Adolfo De Unanue wrote:
> Lennart,
> 
> I did not download to a new directory, but I always do cvs up, and
> everything, and this is the first time I have problems :(
> 
> I followed the build instructions, even I tried mak distclean, make
> maintainer-clean, etc, etc i.e.
> 
> Before the tries, I ran all this tries with a brand new -and empty, of 
> course- .emacs
> 
> first try:
> 
> cvs up
> ./configure
> make
> sudo make install
> 
> (problems with eshell: Invalid assertion.... Squares instead some words
> in all the files)
> 
> second try:
> cvs up
> make distclean
> ./configure
> make
> sudo make install
> 
> (same)
> 
> third try:
> cvs up
> make maintainer-clean
> ./configure
> make bootstrap
> sudo make install
> 
> (now eshell throes a segmentation fault)
> 
> 
> running out of options...
> 
> :(

Download to a new directory.

> Adolfo
> 
> 
> El Mon, 06 Oct 2008 17:51:11 +0200
> "Lennart Borgman (gmail)" <lennart.borgman@gmail.com> escribió:
> 
>> Did you download to a new directory? Did you follow the build
>> instructions?
>>
>> Adolfo De Unanue wrote:
>>> Hi Pete,
>>>
>>> I downloaded -again- the version from cvs.
>>> Same error :(
>>>
>>> Adolfo
>>>
>>>
>>>
>>>
>>> El Mon, 6 Oct 2008 11:48:39 +0200
>>> Peter Dyballa <Peter_Dyballa@Web.DE> escribió:
>>>
>>>> Am 06.10.2008 um 04:12 schrieb Adolfo De Unanue:
>>>>
>>>>> Any hints?
>>>> Update from CVS. The code from last weekend works fine.
>>>>
>>>> --
>>>> Greetings
>>>>
>>>>    Pete
>>>>
>>>> They that can give up essential liberty to obtain a little
>>>> temporary safety deserve neither liberty nor safety.
>>>> 		-Benjamin Franklin, Historical Review of
>>>> Pennsylvania.
>>>>
>>>>
>>>>
>>>
>>>
> 
> 
> 

Re: Problem with eshell

[Adolfo De Unanue]

Lennart,

I followed your advice (i.e. I downloaded emacs to a new directory) and
now eshell works fine, but the font missing-problems is there:


If i do a copy-paste I see this:

Welcome to the Emacs shell

~/software/emacs $ ls
1            admin          etc         lwlib           nt
BUGS         autogen.sh     gc          m4              oldXMenu
COPYING      config.bat     info        mac             site-lisp
CVS          config.guess   install-sh  make-dist       src
ChangeLog    config.log     leim        man             test
INSTALL      config.status  lib-src     mkinstalldirs   update-subdirs
INSTALL.CVS  config.sub     lisp        move-if-change  vms
Makefile     configure      lispintro   msdos           vpath.sed
Makefile.in  configure.in   lispref     nextstep        
README       doc            lock        notes           
~/software/emacs $ 



But in the emacs window I just see some letters and the rest is in
squares. :(

Any *new* suggestions?


PS. In emacs, but in text mode (i.e. executing it inside a linuz
terminal) this doesn't happen, of course



Adolfo



El Tue, 07 Oct 2008 11:42:11 +0200
"Lennart Borgman (gmail)" <lennart.borgman@gmail.com> escribió:

> Adolfo De Unanue wrote:
> > Lennart,
> > 
> > I did not download to a new directory, but I always do cvs up, and
> > everything, and this is the first time I have problems :(
> > 
> > I followed the build instructions, even I tried mak distclean, make
> > maintainer-clean, etc, etc i.e.
> > 
> > Before the tries, I ran all this tries with a brand new -and empty,
> > of course- .emacs
> > 
> > first try:
> > 
> > cvs up
> > ./configure
> > make
> > sudo make install
> > 
> > (problems with eshell: Invalid assertion.... Squares instead some
> > words in all the files)
> > 
> > second try:
> > cvs up
> > make distclean
> > ./configure
> > make
> > sudo make install
> > 
> > (same)
> > 
> > third try:
> > cvs up
> > make maintainer-clean
> > ./configure
> > make bootstrap
> > sudo make install
> > 
> > (now eshell throes a segmentation fault)
> > 
> > 
> > running out of options...
> > 
> > :(
> 
> Download to a new directory.
> 
> > Adolfo
> > 
> > 
> > El Mon, 06 Oct 2008 17:51:11 +0200
> > "Lennart Borgman (gmail)" <lennart.borgman@gmail.com> escribió:
> > 
> >> Did you download to a new directory? Did you follow the build
> >> instructions?
> >>
> >> Adolfo De Unanue wrote:
> >>> Hi Pete,
> >>>
> >>> I downloaded -again- the version from cvs.
> >>> Same error :(
> >>>
> >>> Adolfo
> >>>
> >>>
> >>>
> >>>
> >>> El Mon, 6 Oct 2008 11:48:39 +0200
> >>> Peter Dyballa <Peter_Dyballa@Web.DE> escribió:
> >>>
> >>>> Am 06.10.2008 um 04:12 schrieb Adolfo De Unanue:
> >>>>
> >>>>> Any hints?
> >>>> Update from CVS. The code from last weekend works fine.
> >>>>
> >>>> --
> >>>> Greetings
> >>>>
> >>>>    Pete
> >>>>
> >>>> They that can give up essential liberty to obtain a little
> >>>> temporary safety deserve neither liberty nor safety.
> >>>> 		-Benjamin Franklin, Historical Review of
> >>>> Pennsylvania.
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> > 
> > 
> > 

Re: Problem with eshell

[Lennart Borgman (gmail)]

Adolfo De Unanue wrote:
> Lennart,
> 
> I followed your advice (i.e. I downloaded emacs to a new directory) and
> now eshell works fine,

Congratulations.

> but the font missing-problems is there:
> 
> 
> If i do a copy-paste I see this:
> 
> Welcome to the Emacs shell
> 
> ~/software/emacs $ ls
> 1            admin          etc         lwlib           nt
> BUGS         autogen.sh     gc          m4              oldXMenu
> COPYING      config.bat     info        mac             site-lisp
> CVS          config.guess   install-sh  make-dist       src
> ChangeLog    config.log     leim        man             test
> INSTALL      config.status  lib-src     mkinstalldirs   update-subdirs
> INSTALL.CVS  config.sub     lisp        move-if-change  vms
> Makefile     configure      lispintro   msdos           vpath.sed
> Makefile.in  configure.in   lispref     nextstep        
> README       doc            lock        notes           
> ~/software/emacs $ 
> 
> 
> 
> But in the emacs window I just see some letters and the rest is in
> squares. :(
> 
> Any *new* suggestions?

Yes, please explain this a bit better. Exactly what are you doing and
what fails?

> PS. In emacs, but in text mode (i.e. executing it inside a linuz
> terminal) this doesn't happen, of course
> 
> 
> 
> Adolfo

emacsclient --alternate-editor='emacs -nw' ?

[Teemu Likonen]

I've trying to get "emacs -nw" working as an alternate editor for
emacsclient. No success so far, for example:

    $ export EDITOR="emacsclient --alternate-editor='emacs -nw'" crontab -e
    emacsclient: connect: Connection refused
    emacsclient: error executing alternate editor "emacs -nw"
    crontab: "emacsclient --alternate-editor='emacs -nw'" exited with status 1

The same with this:

    $ export EDITOR=emacsclient
    $ export ALTERNATE_EDITOR="emacs -nw"

It seems that there can't be spaces in the name of the alternate editor,
just a single command name. Does anybody know a work-around?

Re: Problem with eshell

[Adolfo De Unanue]

Hi,

Sorry for my previous post, I just noted the lack of clarity on it.
Well, now eshell is working right (i.e. it not crashes emacs). But the
problem was in the display of the fonts. I don't know why, but emacs
(As I told before, I am using GNU/Emacs 23 cvs version of today in a
Debian Box) is not diplaying the fonts correctly (but before the cvs
up some days ago it did). So this is the problem, and I dont know why
it happen.
I partially solved this problem changing the font to Courier-10, with
all the other letters (BitStream, DejaVu, Monospace) simply doesn't
work. (i.e. I got squares instaead of letters, but strangely enuff,
only in some letters).
I hope that this is a little clearlier than the past post :)


Thanks in advance


Adolfo

On 10/7/08, Lennart Borgman (gmail) <lennart.borgman@gmail.com> wrote:
> Adolfo De Unanue wrote:
>> Lennart,
>>
>> I followed your advice (i.e. I downloaded emacs to a new directory) and
>> now eshell works fine,
>
> Congratulations.
>
>> but the font missing-problems is there:
>>
>>
>> If i do a copy-paste I see this:
>>
>> Welcome to the Emacs shell
>>
>> ~/software/emacs $ ls
>> 1            admin          etc         lwlib           nt
>> BUGS         autogen.sh     gc          m4              oldXMenu
>> COPYING      config.bat     info        mac             site-lisp
>> CVS          config.guess   install-sh  make-dist       src
>> ChangeLog    config.log     leim        man             test
>> INSTALL      config.status  lib-src     mkinstalldirs   update-subdirs
>> INSTALL.CVS  config.sub     lisp        move-if-change  vms
>> Makefile     configure      lispintro   msdos           vpath.sed
>> Makefile.in  configure.in   lispref     nextstep
>> README       doc            lock        notes
>> ~/software/emacs $
>>
>>
>>
>> But in the emacs window I just see some letters and the rest is in
>> squares. :(
>>
>> Any *new* suggestions?
>
> Yes, please explain this a bit better. Exactly what are you doing and
> what fails?
>
>> PS. In emacs, but in text mode (i.e. executing it inside a linuz
>> terminal) this doesn't happen, of course
>>
>>
>>
>> Adolfo
>
>

Re: Problem with eshell

[Lennart Borgman (gmail)]

Hi Adolfo

Coming so far it looks like you have found a bug. Please report this using

  M-x report-emacs-bug

Follow the instructions there and try to tell how to show this bug
starting with

  emacs -Q

Note: It is important that you who found the bug report it because those
who want to fix the bug may need to contact you (now or later if some
more problems connected to this surfaces).



Adolfo De Unanue wrote:
> Hi,
> 
> Sorry for my previous post, I just noted the lack of clarity on it.
> Well, now eshell is working right (i.e. it not crashes emacs). But the
> problem was in the display of the fonts. I don't know why, but emacs
> (As I told before, I am using GNU/Emacs 23 cvs version of today in a
> Debian Box) is not diplaying the fonts correctly (but before the cvs
> up some days ago it did). So this is the problem, and I dont know why
> it happen.
> I partially solved this problem changing the font to Courier-10, with
> all the other letters (BitStream, DejaVu, Monospace) simply doesn't
> work. (i.e. I got squares instaead of letters, but strangely enuff,
> only in some letters).
> I hope that this is a little clearlier than the past post :)
> 
> 
> Thanks in advance
> 
> 
> Adolfo
> 
> On 10/7/08, Lennart Borgman (gmail) <lennart.borgman@gmail.com> wrote:
>> Adolfo De Unanue wrote:
>>> Lennart,
>>>
>>> I followed your advice (i.e. I downloaded emacs to a new directory) and
>>> now eshell works fine,
>> Congratulations.
>>
>>> but the font missing-problems is there:
>>>
>>>
>>> If i do a copy-paste I see this:
>>>
>>> Welcome to the Emacs shell
>>>
>>> ~/software/emacs $ ls
>>> 1            admin          etc         lwlib           nt
>>> BUGS         autogen.sh     gc          m4              oldXMenu
>>> COPYING      config.bat     info        mac             site-lisp
>>> CVS          config.guess   install-sh  make-dist       src
>>> ChangeLog    config.log     leim        man             test
>>> INSTALL      config.status  lib-src     mkinstalldirs   update-subdirs
>>> INSTALL.CVS  config.sub     lisp        move-if-change  vms
>>> Makefile     configure      lispintro   msdos           vpath.sed
>>> Makefile.in  configure.in   lispref     nextstep
>>> README       doc            lock        notes
>>> ~/software/emacs $
>>>
>>>
>>>
>>> But in the emacs window I just see some letters and the rest is in
>>> squares. :(
>>>
>>> Any *new* suggestions?
>> Yes, please explain this a bit better. Exactly what are you doing and
>> what fails?
>>
>>> PS. In emacs, but in text mode (i.e. executing it inside a linuz
>>> terminal) this doesn't happen, of course
>>>
>>>
>>>
>>> Adolfo
>>
> 

Re: Problem with eshell

[Adolfo De Unanue]

Thanks Lennart,
I will do that :)


Adolfo

On 10/7/08, Lennart Borgman (gmail) <lennart.borgman@gmail.com> wrote:
> Hi Adolfo
>
> Coming so far it looks like you have found a bug. Please report this using
>
>   M-x report-emacs-bug
>
> Follow the instructions there and try to tell how to show this bug
> starting with
>
>   emacs -Q
>
> Note: It is important that you who found the bug report it because those
> who want to fix the bug may need to contact you (now or later if some
> more problems connected to this surfaces).
>
>
>
> Adolfo De Unanue wrote:
>> Hi,
>>
>> Sorry for my previous post, I just noted the lack of clarity on it.
>> Well, now eshell is working right (i.e. it not crashes emacs). But the
>> problem was in the display of the fonts. I don't know why, but emacs
>> (As I told before, I am using GNU/Emacs 23 cvs version of today in a
>> Debian Box) is not diplaying the fonts correctly (but before the cvs
>> up some days ago it did). So this is the problem, and I dont know why
>> it happen.
>> I partially solved this problem changing the font to Courier-10, with
>> all the other letters (BitStream, DejaVu, Monospace) simply doesn't
>> work. (i.e. I got squares instaead of letters, but strangely enuff,
>> only in some letters).
>> I hope that this is a little clearlier than the past post :)
>>
>>
>> Thanks in advance
>>
>>
>> Adolfo
>>
>> On 10/7/08, Lennart Borgman (gmail) <lennart.borgman@gmail.com> wrote:
>>> Adolfo De Unanue wrote:
>>>> Lennart,
>>>>
>>>> I followed your advice (i.e. I downloaded emacs to a new directory) and
>>>> now eshell works fine,
>>> Congratulations.
>>>
>>>> but the font missing-problems is there:
>>>>
>>>>
>>>> If i do a copy-paste I see this:
>>>>
>>>> Welcome to the Emacs shell
>>>>
>>>> ~/software/emacs $ ls
>>>> 1            admin          etc         lwlib           nt
>>>> BUGS         autogen.sh     gc          m4              oldXMenu
>>>> COPYING      config.bat     info        mac             site-lisp
>>>> CVS          config.guess   install-sh  make-dist       src
>>>> ChangeLog    config.log     leim        man             test
>>>> INSTALL      config.status  lib-src     mkinstalldirs   update-subdirs
>>>> INSTALL.CVS  config.sub     lisp        move-if-change  vms
>>>> Makefile     configure      lispintro   msdos           vpath.sed
>>>> Makefile.in  configure.in   lispref     nextstep
>>>> README       doc            lock        notes
>>>> ~/software/emacs $
>>>>
>>>>
>>>>
>>>> But in the emacs window I just see some letters and the rest is in
>>>> squares. :(
>>>>
>>>> Any *new* suggestions?
>>> Yes, please explain this a bit better. Exactly what are you doing and
>>> what fails?
>>>
>>>> PS. In emacs, but in text mode (i.e. executing it inside a linuz
>>>> terminal) this doesn't happen, of course
>>>>
>>>>
>>>>
>>>> Adolfo
>>>
>>
>

Problem with eshell

[Adolfo De Unanue]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi

It is me again, I am using the CVS version of GNU/Emacs but since one
month ago, when I run "eshell" and I try to use any command (ls by
example) I got the following error:


Welcome to the Emacs shell

~ $ ls
Invalid function: assert


Someone knows what is happening?

Another -unrelated- question: anything.el would be integrated to Emacs
any time soon?

One more question: Which python mode I should use? The one integrated
with emacs or another? 


Thank you


Adolfo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkjnwr8ACgkQeE41SvEupA6gFgCeJrMpTKvbEDDGjK4uIi+yydwU
U5sAn0sVcEADoQ00ySMEf0FBdERir2V4
=BRv9
-----END PGP SIGNATURE-----

Re: Problem with eshell

[David Hansen]

On Sat, 4 Oct 2008 14:23:43 -0500 Adolfo De Unanue wrote:

> It is me again, I am using the CVS version of GNU/Emacs but since one
> month ago, when I run "eshell" and I try to use any command (ls by
> example) I got the following error:
>
>
> Welcome to the Emacs shell
>
> ~ $ ls
> Invalid function: assert
>
> Someone knows what is happening?

`assert' is a macro defined in the `cl' package.  In some eshell source
file a (eval-when-compile (require 'cl)) is missing.

To find the offending function and file do M-x toggle-debug-on-error and
attach the output in M-x report-emacs-bug (or the diff to fix it).

David

Problem with eshell

[Adolfo De Unanue]

Hi

It is me again, I am using the CVS version of GNU/Emacs but since one
month ago, when I run "eshell" and I try to use any command (ls by
example) I got the following error:


Welcome to the Emacs shell

~ $ ls
Invalid function: assert


Someone knows what is happening?

Another -unrelated- question: anything.el would be integrated to Emacs
any time soon?

One more question: Which python mode I should use? The one integrated
with emacs or another? 


Thank you


Adolfo

Re: Problem with eshell

[Lennart Borgman (gmail)]

Adolfo De Unanue wrote:
> Hi
> 
> It is me again, I am using the CVS version of GNU/Emacs but since one
> month ago, when I run "eshell" and I try to use any command (ls by
> example) I got the following error:
> 
> 
> Welcome to the Emacs shell
> 
> ~ $ ls
> Invalid function: assert

I do not see this problem. Does it happen if you start from

  emacs -Q

Re: Problem with eshell

[Adolfo De Unanue]

Hi

I did what you suggest (I ran emacs -Q), I got the following:




Welcome to the Emacs shell

~ $ ls
Symbol's function definition is void: assert


Any hints?

Thanks for your help

Adolfo 



El Sun, 05 Oct 2008 00:08:25 +0200
"Lennart Borgman (gmail)" <lennart.borgman@gmail.com> escribió:

> Adolfo De Unanue wrote:
> > Hi
> > 
> > It is me again, I am using the CVS version of GNU/Emacs but since
> > one month ago, when I run "eshell" and I try to use any command (ls
> > by example) I got the following error:
> > 
> > 
> > Welcome to the Emacs shell
> > 
> > ~ $ ls
> > Invalid function: assert
> 
> I do not see this problem. Does it happen if you start from
> 
>   emacs -Q
> 

Re: Problem with eshell

[Peter Dyballa]

Am 06.10.2008 um 04:12 schrieb Adolfo De Unanue:

> Any hints?


Update from CVS. The code from last weekend works fine.

--
Greetings

   Pete

They that can give up essential liberty to obtain a little temporary  
safety deserve neither liberty nor safety.
		-Benjamin Franklin, Historical Review of Pennsylvania.

Re: Problem with eshell

[Adolfo De Unanue]

Hi Pete,

I downloaded -again- the version from cvs.
Same error :(

Adolfo




El Mon, 6 Oct 2008 11:48:39 +0200
Peter Dyballa <Peter_Dyballa@Web.DE> escribió:

> 
> Am 06.10.2008 um 04:12 schrieb Adolfo De Unanue:
> 
> > Any hints?
> 
> 
> Update from CVS. The code from last weekend works fine.
> 
> --
> Greetings
> 
>    Pete
> 
> They that can give up essential liberty to obtain a little temporary  
> safety deserve neither liberty nor safety.
> 		-Benjamin Franklin, Historical Review of Pennsylvania.
> 
> 
> 

Re: Problem with eshell

[Lennart Borgman (gmail)]

Did you download to a new directory? Did you follow the build instructions?

Adolfo De Unanue wrote:
> Hi Pete,
> 
> I downloaded -again- the version from cvs.
> Same error :(
> 
> Adolfo
> 
> 
> 
> 
> El Mon, 6 Oct 2008 11:48:39 +0200
> Peter Dyballa <Peter_Dyballa@Web.DE> escribió:
> 
>> Am 06.10.2008 um 04:12 schrieb Adolfo De Unanue:
>>
>>> Any hints?
>>
>> Update from CVS. The code from last weekend works fine.
>>
>> --
>> Greetings
>>
>>    Pete
>>
>> They that can give up essential liberty to obtain a little temporary  
>> safety deserve neither liberty nor safety.
>> 		-Benjamin Franklin, Historical Review of Pennsylvania.
>>
>>
>>
> 
> 
> 

Re: Problem with eshell

[Peter Dyballa]

Am 06.10.2008 um 17:25 schrieb Adolfo De Unanue:

> I downloaded -again- the version from cvs.

Why? Can't you use the cvs programme to update the source code (M-x  
cvs-up RET)? And which Linux variant is the package?

Launching GNU Emacs with -Q and then typing M-x eshell RET to invoke  
the ls command finally produces no failure in Mac OS X 10.4.11 with  
Athena/Xaw3d or in Aqua/GNUStep clothes.

Is your disk OK or has it some self-modifying active sectors? Can you  
you launch GNU Emacs from a shell with minimal environment and LANG/ 
LC_* set to a minimal C? IMO your GNU Linux system is defective – or  
do you have some "customisation" file/RC file for eshell? Eshell,  
term, or shell always load their RC files since they're loading an  
external shell interpreter. I prefer to use *shell* and in it tcsh,  
so when I launch GNU Emacs with -Q and then start the *shell* buffer/ 
process it at once loads ~/.emacs_tcsh. And tcsh *obviously* load its  
RC files since I have aliases!

--
Greetings

   Pete

The day Microsoft makes something that doesn't suck is the day they  
start selling vacuum cleaners.
				– Ernest Jan Plugge