Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Format-Hex should have Count and Offset parameters #3383

Closed
rkeithhill opened this issue Mar 21, 2017 · 3 comments · Fixed by #7877
Closed

Format-Hex should have Count and Offset parameters #3383

rkeithhill opened this issue Mar 21, 2017 · 3 comments · Fixed by #7877
Assignees
Labels
Issue-Enhancement the issue is more of a feature request than a bug Resolution-Won't Fix The issue won't be fixed, possibly due to compatibility reason. WG-Cmdlets-Utility cmdlets in the Microsoft.PowerShell.Utility module

Comments

@rkeithhill
Copy link
Collaborator

Is there any chance we could add Count and Offset parameters? I could probably live without Offset but on the PSCX Format-Hex command, I use -Count almost all the time. That's because I use it to see if a text file has a BOM, in which case I only want to see the first 3 characters.

@SteveL-MSFT SteveL-MSFT added WG-Cmdlets-Utility cmdlets in the Microsoft.PowerShell.Utility module Issue-Enhancement the issue is more of a feature request than a bug Up-for-Grabs Up-for-grabs issues are not high priorities, and may be opportunities for external contributors labels Mar 21, 2017
@adamdriscoll
Copy link
Contributor

I have a working prototype of this and will put in a PR for it but will do so during my PoshSummit session as this is one of my examples\demos for our lab. So please don't fix until then. ;)

image

@lzybkr lzybkr removed the Up-for-Grabs Up-for-grabs issues are not high priorities, and may be opportunities for external contributors label Mar 30, 2017
@lzybkr
Copy link
Member

lzybkr commented Mar 30, 2017

OK - no longer up for grabs.

@iSazonov
Copy link
Collaborator

Resumed this work.

@iSazonov iSazonov added the Resolution-Won't Fix The issue won't be fixed, possibly due to compatibility reason. label Oct 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Enhancement the issue is more of a feature request than a bug Resolution-Won't Fix The issue won't be fixed, possibly due to compatibility reason. WG-Cmdlets-Utility cmdlets in the Microsoft.PowerShell.Utility module
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants