tech-userlevel by thread

• Date Index
• Date Index (newest page)
• Old Index

• [PATCH] include/paths.h comments about users, tlaronde
• [PATCH] Allow qualified filename (bar/foo) PATH se, tlaronde
  • Re: [PATCH] Allow qualified filename (bar/foo) PAT, RVP
    • Re: [PATCH] Allow qualified filename (bar/foo) PAT, tlaronde
    • Re: [PATCH] Allow qualified filename (bar/foo) PAT, Robert Elz
  • Re: [PATCH] Allow qualified filename (bar/foo) PAT, Mouse
    • Re: [PATCH] Allow qualified filename (bar/foo) PAT, Rhialto
    • Re: [PATCH] Allow qualified filename (bar/foo) PAT, tlaronde
      • Re: [PATCH] Allow qualified filename (bar/foo) PAT, Mouse
      • Re: [PATCH] Allow qualified filename (bar/foo) PAT, tlaronde
      • Re: [PATCH] Allow qualified filename (bar/foo) PAT, Mouse
      • Re: [PATCH] Allow qualified filename (bar/foo) PAT, tlaronde
      • Re: [PATCH] Allow qualified filename (bar/foo) PAT, Mouse
      • Re: [PATCH] Allow qualified filename (bar/foo) PAT, tlaronde
• posix_spawnp(3) not checking for empty file name, tlaronde
  • Re: posix_spawnp(3) not checking for empty file na, Martin Husemann
• PATH vs current dir and dir sure to be not existin, tlaronde
  • Re: PATH vs current dir and dir sure to be not exi, Robert Elz
    • Re: PATH vs current dir and dir sure to be not exi, tlaronde
• postinstall vs. obsolete libs, Valery Ushakov
• Symbols from new jemalloc not found, Ryo ONODERA
  • Re: Symbols from new jemalloc not found, Rin Okuyama
    • Re: Symbols from new jemalloc not found, Ryo ONODERA
    • Re: Symbols from new jemalloc not found, Christos Zoulas
      • Re: Symbols from new jemalloc not found, Rin Okuyama
      • Re: Symbols from new jemalloc not found, Ryo ONODERA
  • Re: Symbols from new jemalloc not found, Taylor R Campbell
    • Re: Symbols from new jemalloc not found, Ryo ONODERA
• sh(1) and NUL, Thomas Klausner
  • Re: sh(1) and NUL, Robert Elz
    • Re: sh(1) and NUL, Thomas Klausner
    • Re: sh(1) and NUL, Robert Elz
• sh(1) read: add LINE_MAX safeguard and "-n" option, tlaronde
  • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, Robert Elz
    • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, tlaronde
      • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, tlaronde
      • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, Robert Elz
      • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, Robert Elz
      • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, tlaronde
      • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, tlaronde
      • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, Robert Elz
    • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, Greg Troxel
      • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, tlaronde
    • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, tlaronde
    • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, Robert Elz
    • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, Robert Elz
    • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, Robert Elz
      • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, tlaronde
    • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, Robert Elz
      • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, tlaronde
      • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, Robert Elz
      • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, tlaronde
      • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, Robert Elz
      • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, tlaronde
      • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, Robert Elz
      • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, Mouse
      • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, tlaronde
      • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, Paul Goyette
      • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, Jason Thorpe
      • Re: sh(1) read: add LINE_MAX safeguard and "-n" op, Edgar Fuß
• ed(1) as default editor in sh(1), tlaronde
  • Re: ed(1) as default editor in sh(1), Valery Ushakov
  • Re: ed(1) as default editor in sh(1), Greg Troxel
• interactive shell detection in shrc, Valery Ushakov
  • Re: interactive shell detection in shrc, Robert Elz
    • Re: interactive shell detection in shrc, Valery Ushakov
      • Re: interactive shell detection in shrc, Steffen Nurpmeso
      • Re: interactive shell detection in shrc, Greg A. Woods
      • Re: interactive shell detection in shrc, Steffen Nurpmeso
      • Re: interactive shell detection in shrc, RVP
      • Re: interactive shell detection in shrc, Steffen Nurpmeso
      • Re: interactive shell detection in shrc, Robert Elz
      • Re: interactive shell detection in shrc, Greg A. Woods
      • Re: interactive shell detection in shrc, Robert Elz
      • Re: interactive shell detection in shrc, Robert Elz
      • Re: interactive shell detection in shrc, Greg A. Woods
      • Re: interactive shell detection in shrc, Steffen Nurpmeso
      • Re: interactive shell detection in shrc, Robert Elz
      • Re: interactive shell detection in shrc, Steffen Nurpmeso
      • Re: interactive shell detection in shrc, Steffen Nurpmeso
      • Re: interactive shell detection in shrc, Greg A. Woods
      • Re: interactive shell detection in shrc, tlaronde
      • Re: interactive shell detection in shrc, Greg A. Woods
      • Re: interactive shell detection in shrc, tlaronde
      • Re: interactive shell detection in shrc, RVP
      • Re: interactive shell detection in shrc, tlaronde
      • Re: interactive shell detection in shrc, RVP
      • Re: interactive shell detection in shrc, Steffen Nurpmeso
      • Re: interactive shell detection in shrc, Greg A. Woods
      • Re: interactive shell detection in shrc, George Georgalis
      • Re: interactive shell detection in shrc, Robert Elz
      • Re: interactive shell detection in shrc, Greg A. Woods
      • Re: interactive shell detection in shrc, Robert Elz
      • Re: interactive shell detection in shrc, Greg A. Woods
      • Re: interactive shell detection in shrc, George Georgalis
      • Re: interactive shell detection in shrc, George Georgalis
      • Re: interactive shell detection in shrc, tlaronde
      • Re: interactive shell detection in shrc, Robert Elz
      • Re: interactive shell detection in shrc, Steffen Nurpmeso
      • Re: interactive shell detection in shrc, Greg A. Woods
      • Re: interactive shell detection in shrc, Greg A. Woods
      • Re: interactive shell detection in shrc, Robert Elz
    • Re: interactive shell detection in shrc, Robert Elz
      • Re: interactive shell detection in shrc, Valery Ushakov
      • Re: interactive shell detection in shrc, Robert Elz
      • Re: interactive shell detection in shrc, Steffen Nurpmeso
  • <Possible follow-ups>
  • Fwd: Re: interactive shell detection in shrc, Steffen Nurpmeso
    • Re: Fwd: Re: interactive shell detection in shrc, RVP
      • Re: Fwd: Re: interactive shell detection in shrc, RVP
      • Re: Fwd: Re: interactive shell detection in shrc, Steffen Nurpmeso
    • Re: Fwd: Re: interactive shell detection in shrc, Robert Elz
      • Re: Fwd: Re: interactive shell detection in shrc, Steffen Nurpmeso
      • Re: Fwd: Re: interactive shell detection in shrc, RVP
      • Re: Fwd: Re: interactive shell detection in shrc, Robert Elz
      • Re: Fwd: Re: interactive shell detection in shrc, Mouse
      • Re: Fwd: Re: interactive shell detection in shrc, RVP
      • Re: Fwd: Re: interactive shell detection in shrc, Rhialto
      • Re: Fwd: Re: interactive shell detection in shrc, RVP
      • Re: Fwd: Re: interactive shell detection in shrc, RVP
    • Re: Fwd: Re: interactive shell detection in shrc, Robert Elz
• sh(1): POSIX "Command Search and Execution", tlaronde
  • Re: sh(1): POSIX "Command Search and Execution", Robert Elz
    • Re: sh(1): POSIX "Command Search and Execution", tlaronde
    • Re: sh(1): POSIX "Command Search and Execution", Robert Elz
      • Re: sh(1): POSIX "Command Search and Execution", tlaronde
      • Re: sh(1): POSIX "Command Search and Execution", David Holland
      • Re: sh(1): POSIX "Command Search and Execution", tlaronde
      • Re: sh(1): POSIX "Command Search and Execution", Robert Elz
      • Re: sh(1): POSIX "Command Search and Execution", tlaronde
      • Re: sh(1): POSIX "Command Search and Execution", RVP
      • Re: sh(1): POSIX "Command Search and Execution", Robert Elz
      • Re: sh(1): POSIX "Command Search and Execution", tlaronde
      • Re: sh(1): POSIX "Command Search and Execution", Robert Elz
      • Re: sh(1): POSIX "Command Search and Execution", tlaronde
  • PATH_OPT: allowing to search for qualified utiliti, tlaronde
• etiquette for new failing test cases, followed by , Greg Troxel
  • Re: etiquette for new failing test cases, followed, Martin Husemann
  • Re: etiquette for new failing test cases, followed, Roland Illig
    • Re: etiquette for new failing test cases, followed, Greg Troxel
      • Re: etiquette for new failing test cases, followed, Roland Illig
  • Re: etiquette for new failing test cases, followed, Taylor R Campbell
    • Re: etiquette for new failing test cases, followed, Greg Troxel
• mysterious remquo bug, Greg Troxel
  • Re: mysterious remquo bug, Greg Troxel
  • Re: mysterious remquo bug, RVP
  • Re: mysterious remquo bug, Robert Elz
    • Re: mysterious remquo bug, Greg Troxel
  • Re: mysterious remquo bug, Martin Husemann