STDIN of dialog4ports

[rank1seeker at gmail.com]

Thanks Ilya,

Well, better you patch it as you already know the layout of
dialog4ports's code, as you've been main dev and you know where to start
patching. I believe it's a little change which would cost you only hour
or few. ;)
+ you are way more experienced in C then I (I did it only for about 4
  months)

Just throw a patch and I'll gladly test it. (added hackers@)


Domagoj Smolčić



On Thu, 12 Mar 2015 14:54:47 +0300
Ilya A. Arkhipov <rum1cro at yandex.ru> wrote:

> Yes, now dialog4ports can't to get from STDIN any data.
> But if you want you(or maybe I) can prepare patch for that ^_^
> 
> 12.03.2015, 07:45, "rank1seeker at gmail.com" <rank1seeker at gmail.com>:
> > Hi!
> >
> > I'm contacting you because you have developed dialog4ports and I'll
> > try to be very short in my request.
> >
> > GOAL: File "/var/db/ports/$PORT/options" being created via 'make
> > config' as it is when ENTER is pressed as soon as dialog was
> > displayed.
> >
> > Before 9.0 my solution was:
> > When in port's dir (DOESN'T have "/var/db/ports/$PORT/options" file
> > set => doesn't exists yet) --
> > # make config << MyEND
> > o
> > MyEND
> > --
> > Additionally, I avoided dialog being displayed by sending it
> > to /dev/null. Once "/var/db/ports/$PORT/options" is created, task
> > is done => NO build, install, etc ...
> >
> > Now as I understand, change to "raw" mode type of dialog4ports's
> > STDIN, which differs from pipe's buffered mode, makes me unable to
> > pipe ENTER (\n) to dialog
> >
> > Now I'm forced to use lang/expect which is overhead and very slow!
> >
> > Thanks in advance.
> >
> > Domagoj Smolčić
>