renders almost inoperable the %?string referencing

you can extract particular job with the help of many of the little unix tools but why not to do it with the already existing knob of the native tool just by setting the knob free?

is it for historical reasons, by oblivion, or what were/are the technical rationale? just curious


--- /usr/src/bin/ksh/jobs.c.orig        Wed Jul 24 15:21:01 2013
+++ /usr/src/bin/ksh/jobs.c     Mon Jul 29 10:16:12 2013
@@ -34,7 +34,7 @@ struct proc {
        int     state;
        int     status;         /* wait status */
        pid_t   pid;            /* process id */
-       char    command[48];    /* process command string */
+       char    command[LINE];  /* process command string */
      };

      /* Notify/print flag - j_print() argument */
/end diff


otherwise, if i apply proper mdoc macro:

--- /usr/src/bin/ksh/ksh.1.orig Mon Jul 29 10:52:54 2013
+++ /usr/src/bin/ksh/ksh.1      Mon Jul 29 11:29:17 2013
@@ -4562,6 +4562,7 @@
    .It %? Ns Ar string
    The job with its command containing the string
    .Ar string
+.Ns , if you're lucky
    (an error occurs if multiple jobs are matched).
    .It % Ns Ar string
    The job with its command starting with the string
/end diff


best
/ty

Reply via email to