Repository navigation
_output_ should strip trailing forward slashes #56
Description
Activity
- Good thinking there! Didn't realise that. Definitely worth doing.…On Thu, 15 Aug. 2019, 10:56 pm Michael Skelton, ***@***.***> wrote: When building command files I notice that the trend is to build them as: nmap -sC -sV -oA _output_/scans/nmap _target_ Noting that a slash after _output_ is the trend. The problem with this is that it's not uncommon to then launch this command file as something like: interlace -cL example.il -t 127.0.0.1 -o ./ This results in a path that has // within it. To better support such use cases, as a default the output flag should strip any trailing forward slashes. This should also be noted within README.md as expected behavior. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#56?email_source=notifications&email_token=AEBVTU62HL4UHTVGCH5GYXLQEVG6DA5CNFSM4IL56WY2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HFNSXDA>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEBVTU44KGOWX5H3XJ7IDELQEVG6DANCNFSM4IL56WYQ> .Reacted by Michael Skelton
When building command files I notice that the trend is to build them as:
Noting that a slash after
_output_is the trend.The problem with this is that it's not uncommon to then launch this command file as something like:
This results in a path that has
//within it. To better support such use cases, as a default the output flag should strip any trailing forward slashes. This should also be noted within README.md as expected behavior.