Will-
I'm glad you got things going with command
line editing support for perldl. There is
also an updated PDL shell called pdl2 which
provides some improved support for completions
of various types if you have the needed module
dependencies installed.
If you try to run pdl2 and the dependencie
Hi Will
You could try the SciPDL download which lives within it’s own kitchen sink and
likely won’t break on new MacOS. (Also includes GNU::Readline)
/usr/bin/python includes an editable command line, why can’t this be built in
to perl? I find the whole Term::Readline::XX thing confusing. What
Welcome! Glad to have you aboard.
> On Apr 13, 2018, at 4:58 PM, William Schmidt
> wrote:
>
> That did it. Man, having an editable history list is primo. I think this is
> another example of how badly macOS High Sierra sucks. Apple now wants us to
> install 10.13.4 which will again break eve
That did it. Man, having an editable history list is primo. I think this is
another example of how badly macOS High Sierra sucks. Apple now wants us to
install 10.13.4 which will again break everything that was compiled with
the 10.13.3 Xcode libs, as the download includes new libraries and command
Hey, cool! Ya learn something new every day.
> On Apr 13, 2018, at 4:21 PM, Chris Marshall wrote:
>
> I suggest installing Term::ReadLine::Perl which
> is a pure perl implementation of the readline
> capability. I use it on the windows PDL since
> there is no GNU readline for microsoft com w
I suggest installing Term::ReadLine::Perl which
is a pure perl implementation of the readline
capability. I use it on the windows PDL since
there is no GNU readline for microsoft com windows.
--Chris
On 4/13/2018 18:15, William Schmidt wrote:
Progress, but no cigar, yet...
brew link --force r
Try setting TERM to just “xterm”?
> On Apr 13, 2018, at 4:15 PM, William Schmidt
> wrote:
>
> Progress, but no cigar, yet...
>
> brew link --force readline
>
> I downloaded the latest library and then attempted to reinstall
> Term::ReadLine::Gnu, with the following error in the build log:
>
Progress, but no cigar, yet...
brew link --force readline
I downloaded the latest library and then attempted to reinstall
Term::ReadLine::Gnu, with the following error in the build log:
This part seems correct:
Found `/usr/lib/libtermcap.dylib'.
cc -I/usr/local/opt/readline/include -fno-common
You may have to manually install the Gnu Readline library. It’s becoming
enough of a pain in the butt to get installed, that an Alien::ReadLine might be
called for...
> On Apr 13, 2018, at 3:23 PM, William Schmidt
> wrote:
>
> Hmm,
>
> Tried that.
>
> $ cpanm Term::ReadLine::Gnu
> Term::Re
Hmm,
Tried that.
$ cpanm Term::ReadLine::Gnu
Term::ReadLine::Gnu is up to date. (1.35)
Does it require config or enabling?
Will
On Fri, Apr 13, 2018 at 4:20 PM, Craig DeForest
wrote:
> The problem is that Term::ReadLine is suffering from bit rot. Try
> installing Term::ReadLine::Gnu.
>
>
The problem is that Term::ReadLine is suffering from bit rot. Try installing
Term::ReadLine::Gnu.
> On Apr 13, 2018, at 3:14 PM, William Schmidt
> wrote:
>
> Hello piddlers,
>
> perldl is one great prototyping tool, and I am making great progress
> understanding and mastering PDL running it
11 matches
Mail list logo