problem with zsh

problem with zsh

[Fahim Azad]

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


Hi!

I wanted to switch from bash to z-shell in my Manjaro Linux pc terminal but by mistake I wrote "/ usr / bin / git-shell" instead of "/ bin / zsh". After restart the terminal will not work at all. When I click to open the terminal, it starts up but quickly disappears. I have tried with other terminals but unfortunately it did not help to fix the problem. Please help me!
With best regardsFahim Azad

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

Re: problem with zsh

[Bart Schaefer]

You're going to need to log in with a different user name, or boot in
single user mode.  Alternatively, if you have access to the filesystem
from elsewhere via a shared drive, you may be able to edit the
/etc/passwd file to fix the shell assignment.

On Tue, Sep 15, 2020 at 4:08 AM Fahim Azad <f_azaad@yahoo.co.uk> wrote:
>
> Hi!
>
> I wanted to switch from bash to z-shell in my Manjaro Linux pc terminal but by mistake I wrote "/ usr / bin / git-shell" instead of "/ bin / zsh". After restart the terminal will not work at all. When I click to open the terminal, it starts up but quickly disappears. I have tried with other terminals but unfortunately it did not help to fix the problem. Please help me!
>
> With best regards
> Fahim Azad
>

Re: problem with zsh

[Peter Stephenson]

> On 15 September 2020 at 17:39 Bart Schaefer <schaefer@brasslantern.com> wrote:
> You're going to need to log in with a different user name, or boot in
> single user mode.  Alternatively, if you have access to the filesystem
> from elsewhere via a shared drive, you may be able to edit the
> /etc/passwd file to fix the shell assignment.

There may be other ways using GUI clients, since the implication is
it's still possible to start utilities, and it looks like you're changing
settings from the command line.  For example, start emacs and use

M-x set-variable RET explicit-shell-file-name RET "/bin/zsh" RET

(double quotes needed), then

M-x shell RET

to get a shell command line. M-x is usually entered as ESC x and there
is TAB completion for the Emacs names.

It just depends what you have access to.

pws

> On Tue, Sep 15, 2020 at 4:08 AM Fahim Azad <f_azaad@yahoo.co.uk> wrote:
> >
> > Hi!
> >
> > I wanted to switch from bash to z-shell in my Manjaro Linux pc terminal but by mistake I wrote "/ usr / bin / git-shell" instead of "/ bin / zsh". After restart the terminal will not work at all. When I click to open the terminal, it starts up but quickly disappears. I have tried with other terminals but unfortunately it did not help to fix the problem. Please help me!
> >
> > With best regards
> > Fahim Azad
> >
>

Re: problem with zsh

[Peter Stephenson]

On Tue, 2020-09-15 at 17:50 +0100, Peter Stephenson wrote:
> > On 15 September 2020 at 17:39 Bart Schaefer <schaefer@brasslantern.com> wrote:
> > You're going to need to log in with a different user name, or boot in
> > single user mode.  Alternatively, if you have access to the filesystem
> > from elsewhere via a shared drive, you may be able to edit the
> > /etc/passwd file to fix the shell assignment.
> 
> There may be other ways using GUI clients, since the implication is
> it's still possible to start utilities, and it looks like you're changing
> settings from the command line.

Another way: whatever desktop you're using probably has a way of running
commands directly.

For example, if it's the KDE Plasma desktop, typing Alt-Space should get
you a command line window.  Then type:

konsole -e /bin/zsh

There will no doubt be equivalents for other desktops.

pws

problem with zsh

[BERK GEVECI]

greetings,

i have downloaded and compiled the latest version of
zsh (2.5.03) on several machines. it is running fine
on four sgis ( with irix versions from 4 to 5 ).
unfortunately, i had serious problems running it on
a titan running 'TitanOS UNIX Release 4.2 P2 on 3000 Series'.
it compiled fine with bunch of warnings ( as i was warned of ).
the problem is that filename generation is acting very strangely.
problems:
1) when i first run zsh ( starting from a csh ), it changes
to the root directory.
2) when i try 'ls -d a*' in a directory which contains
the following files:
 ammar  run.1  run.2  temp
i get these messages:
amma: No such file or directory
amtables: No such file or directory
authority: No such file or directory

[ amtables -> .gamtables
  amma     -> .gamma
  authorithy -> .Xauthority, hidden files ]

can you please help me solve this problem ?

maybe a copy of the output from 'buildzsh auto' can be
useful:

#
# buildzsh -- zsh configuration tool
#
# try "buildzsh help" for more information
#

Building zsh 2.5.03

	determining host type...
	...looks like a titan 

Building config.h...

	starting features probing...

	not using pure SYSV...
	not using termios...
	not using termio...
	using sgttyb...
	using <dirent.h>...
	using <unistd.h>...
	using <string.h>...
	using <memory.h>...
	not using <locale.h>...
	using <utmp.h>...
	using host field in utmp...
	using <sys/time.h>...
	using <sys/wait.h>...
	not using waitpid()...
	using select()...
	not using <sys/select.h>...
	using fifos...
	not using strftime()...
	not using tcsetpgrp()...
	not using tcgetattr() and friends...
	using setpgrp()...
	using sigblock()...
	not using RFS...
	using getrusage() and wait3()...
	not using NIS...
	not using username caching...
	using signal handlers returning int...
	using automatically reset signal handlers...
	not using sigset() to install said signal handlers...

	finished probing features...

	defining installation specifics...

	DEFTMPPREFIX is ""/tmp/zsh""...
	GLOBALZSHENV is ""/etc/zshenv""...
	GLOBALZSHRC is ""/etc/zshrc""...
	GLOBALZLOGIN is ""/etc/zlogin""...
	GLOBALZPROFILE is ""/etc/zprofile""...
	using "suspended" instead of "stopped"...
	DEFAULT_HISTSIZE is "30"...

	defined installation specifics...

Building signals.h...done

Building Makefile...

	CC is "cc -43"...
	checking whether make understands VPATH...
"???", line 1: ERROR: preprocessor error: no output file produced
*** Error code 2

	(make does not understand VPATH...)

	probing for Makefile...

	CFLAGS is "-O"...
	LD is "cc -43"...
	LDFLAGS is "-O"...
	LIBS is "-ltermcap"...
	Working out modules (*.{[hco],pro})...
	.c....
	.h....
	.pro....
	.o....

	probed for Makefile...

	...possible notes
	...special rules
	...general rules

You may want to look at the file(s) I just created:

	config.h
	signals.h
	Makefile

to make sure they are correct.	Or you may just want
to go ahead and try running make to see what happens.

Shall I execute "make" now? 
In that case you will have to call the following yourself:

	make



n.b.: i am not subscrided.

sincerely,
Berk Geveci

Re: problem with zsh

[Richard Coleman]

> i have downloaded and compiled the latest version of
> zsh (2.5.03) on several machines. it is running fine
> on four sgis ( with irix versions from 4 to 5 ).
> unfortunately, i had serious problems running it on
> a titan running 'TitanOS UNIX Release 4.2 P2 on 3000 Series'.
> it compiled fine with bunch of warnings ( as i was warned of ).
> the problem is that filename generation is acting very strangely.
> problems:
> 1) when i first run zsh ( starting from a csh ), it changes
> to the root directory.
> 2) when i try 'ls -d a*' in a directory which contains
> the following files:
>  ammar  run.1  run.2  temp
> i get these messages:
> amma: No such file or directory
> amtables: No such file or directory
> authority: No such file or directory

A couple of things.

1) The zsh mailing list is now broken into 3 mailing lists.
   zsh-announce@math.gatech.edu
   zsh-users@math.gatech.edu
   zsh-workers@math.gatec.edu

   You sent your message to the old zsh-list mailing list,
   which gets forwarded to zsh-workers.  You should probably
   use zsh-workers in the future.  Information about the various
   mailing lists is contained in the META-FAQ available on any of
   the zsh ftp sites.

2) I would appreciate if you would try to compile the latest beta
   release (beta10 with beta11 due in the next week or so) on this
   machine.  If necessary, I can make you a snapshot of the latest
   baseline source.  Although 2.5.03 is the latest production release,
   no more versions or upgrades for this particular version will be
   released.  The next production release will be 3.00, so we should
   make sure the latest beta compiles on this machine.

3) You shouldn't worry too much about it being a beta release.  Although
   it has plenty of bugs, I think it is as least as stable as 2.5.03.
   It is also considerably more portable.

Richard Coleman
coleman@math.gatech.edu