too much bureaucracy to add a new command... To get the
async close patch in, I wasn't able to add [kill]. To add
[kill], A TIP will have to be created, discussed, edited,
discussed, rejected, rewritten, discussed more, voted on,
then applied..
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't see any reason why it wouldn't work, except for the
parts of that patch that have already been applied. But
then the patch utility would just skip them with a warning.
It would be nicer, though, to fix the executables that
you're piping to to have them respect EOF on the write side
of the pipe (write side as viewed from the child).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=130120
attach is the patch that was realesed in the past
Logged In: YES
user_id=79902
patch still missing (stupid tracker form's fault probably)
Logged In: YES
user_id=130120
attached again
Logged In: YES
user_id=7549
too much bureaucracy to add a new command... To get the
async close patch in, I wasn't able to add [kill]. To add
[kill], A TIP will have to be created, discussed, edited,
discussed, rejected, rewritten, discussed more, voted on,
then applied..
Logged In: YES
user_id=130120
shame.
will the old patch work on tcl 8.5?
If not can a new patch be created.
Logged In: YES
user_id=7549
I don't see any reason why it wouldn't work, except for the
parts of that patch that have already been applied. But
then the patch utility would just skip them with a warning.
It would be nicer, though, to fix the executables that
you're piping to to have them respect EOF on the write side
of the pipe (write side as viewed from the child).
Logged In: YES
user_id=72656
see TIP #88, which will be revived at some point hopefully.