zsh-workers
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: Oliver Kiddle <okiddle@yahoo.co.uk>,
	Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Adding (compiling) a module to already build Zsh
Date: Thu, 15 Sep 2016 14:22:25 +0200	[thread overview]
Message-ID: <CAKc7PVAAi-5azEjcsaFe_k1tXR7UNiAr8JheHJ-jUCMrf9Aviw@mail.gmail.com> (raw)
In-Reply-To: <CAHYJk3TiGCvpnpGNCaAhgG6O-RxVqgg__Sx9SQ8pKUyDXOp92g@mail.gmail.com>

On 14 September 2016 at 21:03, Mikael Magnusson <mikachu@gmail.com> wrote:
> http://cgit.mika.l3ib.org/cgit/zsh-cvs/commit/?h=a095c720fff0893b9f1ca3f96bb28de125aa155f
>
> I did this at least 5 years ago so I didn't know as much then as I do
> know about autoconf, but I think AC_CHECK_LIB is a convenience macro
> for something that first checks if a lib is linkable, and then adds it
> to the list of things to link to globally. We could just expand those
> to the full thing that only does the check without adding, and since
> the lib is always the same, the part of the patch that has the
> unconditional lib names in the .mdd files should be fine?
>
> https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Libraries.html
> ah, actually we can just provide the action-if-found action and it
> won't add the name to LIBS for us, even better.

I once proposed update of configure when I at Ubuntu 14.04 observed,
that when the terminal handling library is detected to be terminfo,
Zcurses is not being build. I was warned that the "link modules'
libraries to Zsh binary" is dictated by traits of some platforms, so
if Zsh binary doesn't have ncurses, then any module also can't have
it, and thus Zcurses is not build. I recall analyzing configure.ac and
seeing there a precedence list of terminal handling libraries, when I
wondered why configure ends with "-ldl -ltinfo -lrt -lm -lc", without
-lncurses (ran the configure on Ubuntu 14.04 laptop right now). Being
afraid about Zcurses future, I want to say that possibly altered
configure.ac should strive for always building Zcurses, because it is
an important module, maybe currently I'm the single person that's
going to prove that, but I will with my new plugin which will change
the way shell is used and put in shadow fish and bash. Zcurses is an
asset, together with loadable modules, rich flags (e.g. [[
${(M)${(f)"$(<$f)"}:#$query} ]] as replacement for forking for grep),
patterns, etc. One can code like in Ruby, what I proved with
zsh-navigation-tools that supports 120k-150k elements in the
selectable list function n-list. Of course Zsh coding style has its
long learning curve, I code for about 14 months and constantly
improve, and I must say that many other plugin authors devote say 1
month for a plugin, when I constantly updated ZNT for 10 months. In
short, Zsh can have developer community (already has, but they code
close to ABSGuide and don't devote enough time) writing software
thanks to well established platform, and "Zcurses everywhere" is
important part of that platform, and not requiring that Zsh binary is
linked to what modules are linked will allow to do "Gdbm everywhere"
etc.

Best regards,
Sebastian Gniazdowski


  reply	other threads:[~2016-09-15 12:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-12  6:12 Sebastian Gniazdowski
2016-09-12 17:38 ` Bart Schaefer
2016-09-14  7:16   ` Sebastian Gniazdowski
2016-09-14  8:54     ` Oliver Kiddle
2016-09-14 16:19       ` Bart Schaefer
2016-09-14 19:03       ` Mikael Magnusson
2016-09-15 12:22         ` Sebastian Gniazdowski [this message]
2016-09-14 15:09     ` Lawrence Velázquez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKc7PVAAi-5azEjcsaFe_k1tXR7UNiAr8JheHJ-jUCMrf9Aviw@mail.gmail.com \
    --to=sgniazdowski@gmail.com \
    --cc=mikachu@gmail.com \
    --cc=okiddle@yahoo.co.uk \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).