comment on

Thanks a ton for helping me out with this. I see what you mean about unsafe signals, so I'll probably just use Term::ReadLine::Perl instead. I suppose that solves my issues.

It is somewhat comforting to know that this is just how T:R:Gnu works instead of me doing horribly wrong. ;)

Since I'm sure I can get things moving along with T:R:Perl, what would be the best way to make sure users are using the T:R:Perl package instead of Gnu? Would it be considered good form to just set the environment variable along with a "use Term::ReadLine::Perl"?

Thanks again for taking the time to look into this. It was really a stumbling block for me so I appreciate the help. In hindsight I probably should have just moved to T:R:Perl and called it a day, but I got obsessed a bit. ;)

In reply to Re^2: Perl Term::ReadLine::Gnu Signal Handling Difficulties by sgt_b2002
in thread Perl Term::ReadLine::Gnu Signal Handling Difficulties by sgt_b2002

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


P is for Practical
	PerlMonks