zsh-workers
 help / color / mirror / code / Atom feed
* A couple of problems with version 4.0.2
@ 2001-07-19 13:28 Raúl Núñez de Arenas Coronado
  2001-07-19 14:33 ` Andrej Borsenkow
  0 siblings, 1 reply; 3+ messages in thread
From: Raúl Núñez de Arenas Coronado @ 2001-07-19 13:28 UTC (permalink / raw)
  To: zsh-workers

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2123 bytes --]

    Hello zsh workers :)

    First of all, thanks for such a good shell. It's invaluable for me.

    I think that zsh is near to perfection, but nobody's perfect ;)))

    Well, I have a couple of suggestions about zsh since I've had
some little problems installing it. First of all, the file
Src/zshpaths.h, which is generated by the makefile, doesn't seem to
be updated when re-running configure with other directory options. It
must be removed by hand in order to have it rebuilt. Maybe it is
updated, but with the same information it contained before. I don't
really know what the problem is, but if I rerun configure with
different directories for modules, etc... the files are properly
installed in their new locations but Src/zshpaths.h is not changed.

    The second problem is that I need to adapt zsh to our filesystem,
and I need to put the dinamic-loadable modules in the directory
$(prefix)/lib/zsh instead of $(prefix)/lib/zsh/$(VERSION)/zsh, and I
cannot change this using configure. I must do it at build time with
something like 'make MODDIR=<mymoddir>'. This is not a problem, but I
think that for being coherent that change should be achieved by using
the configure script.

    The last is just a suggestion: I want to use zsh instead of ash
in a special linux bootdisk we have at work, but the maintainer of
that disk has said to me that the editing keybindings in zsh cannot
be removed and that they occupy a lot. To my knowledge the edition
facilities of zsh (command-line edition, I mean) are loaded as a
module and so it can be removed, aren't they? It those facilities
cannot be removed (some people would sacrifice command line edition
for space sometimes), would it be possible in future versions...?.
Anyway I like zsh just like it is now. It's simply fantastic.

    I want to tell you that IMHO zsh has an invaluable way of dealing
with key bindings: by using bindkeys -d I can easily remove all
keybindings and leave only those I choose, without having fear of
pressing a 'bad' keycombo. Thanks for that and other features that
make zsh the way it is.

    Raúl Núñez de Arenas Coronado


^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: A couple of problems with version 4.0.2
  2001-07-19 13:28 A couple of problems with version 4.0.2 Raúl Núñez de Arenas Coronado
@ 2001-07-19 14:33 ` Andrej Borsenkow
  2001-07-19 16:07   ` Bart Schaefer
  0 siblings, 1 reply; 3+ messages in thread
From: Andrej Borsenkow @ 2001-07-19 14:33 UTC (permalink / raw)
  To: Raъl Nъсez de Arenas Coronado, zsh-workers

>
>     Well, I have a couple of suggestions about zsh since I've had
> some little problems installing it. First of all, the file
> Src/zshpaths.h, which is generated by the makefile, doesn't seem to
> be updated when re-running configure with other directory options.

Currently it depends on Makemod that is actually rebuilt only when some
module gets added/removed (it depends on config.modules).

I guess, it should depend on config.status as well. At least, this provides
obvious workaround.

>     The second problem is that I need to adapt zsh to our filesystem,
> and I need to put the dinamic-loadable modules in the directory
> $(prefix)/lib/zsh instead of $(prefix)/lib/zsh/$(VERSION)/zsh,
                                                            ^^^
the last zsh is part of module name, so installation directory is
$prefix/lib/zsh/$VERSION. I am not sure setting it to $prefix/lib would be a
good choice, because modules names may conflict with another SW (currently
all modules are named as zsh/something but we may get foo/bar sometimes).
So, it is better to keep them under common directory. Versioning allows
several versions to coexist.

Why would oyu need to force particular location?

>     The last is just a suggestion: I want to use zsh instead of ash
> in a special linux bootdisk we have at work, but the maintainer of
> that disk has said to me that the editing keybindings in zsh cannot
> be removed and that they occupy a lot. To my knowledge the edition
> facilities of zsh (command-line edition, I mean) are loaded as a
> module and so it can be removed, aren't they?

Strictly speaking, they are autoloaded if zsh runs interactive. But if
corresponding modules do not exist, zsh will run without. What I do not like
is error message:

bor@itsrm2% zsh -f
zsh: failed to load module: zsh/zle

Maybe, we could make it conditional on zsh name? (name it azsh for simple
zsh :-)

I do not know if it possible to put zsh on a floppy. On my system (not a
ix86 and with debugging):

bor@itsrm2% size =zsh
/tools/bin/zsh: 796300 + 58864 + 2525272 = 3380436

Looks like a bit too much for a floppy. May be, static build without all
modules needs a bit less.

-andrej


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: A couple of problems with version 4.0.2
  2001-07-19 14:33 ` Andrej Borsenkow
@ 2001-07-19 16:07   ` Bart Schaefer
  0 siblings, 0 replies; 3+ messages in thread
From: Bart Schaefer @ 2001-07-19 16:07 UTC (permalink / raw)
  To: zsh-workers, Raúl Núñez de Arenas Coronado

On Jul 19,  6:33pm, Andrej Borsenkow wrote:
} Subject: RE: A couple of problems with version 4.0.2
}
} >     The last is just a suggestion: I want to use zsh instead of ash
} > in a special linux bootdisk we have at work, but the maintainer of
} > that disk has said to me that the editing keybindings in zsh cannot
} > be removed and that they occupy a lot.
} 
} Strictly speaking, they are autoloaded if zsh runs interactive. But if
} corresponding modules do not exist, zsh will run without. What I do not
} like is error message:
} 
} bor@itsrm2% zsh -f
} zsh: failed to load module: zsh/zle

If you compile zsh without the zle module, rather than compiling it with
and then removing the dynamic library, you don't get any complaint.

} I do not know if it possible to put zsh on a floppy. On my system (not a
} ix86 and with debugging):
} 
} bor@itsrm2% size =zsh
} /tools/bin/zsh: 796300 + 58864 + 2525272 = 3380436

A static link, with ONLY the zsh/main module, stripped but compiled with
-g (so non-optimized code):

   text    data     bss     dec     hex filename
 448879   12576   66808  528263   80f87 Src/zsh

That's still about 1/3 of the available space on a floppy.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2001-07-19 16:20 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-07-19 13:28 A couple of problems with version 4.0.2 Raúl Núñez de Arenas Coronado
2001-07-19 14:33 ` Andrej Borsenkow
2001-07-19 16:07   ` Bart Schaefer

Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).