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

untagged issue? #52

Open
gngrossi opened this issue Mar 13, 2024 · 3 comments
Open

untagged issue? #52

gngrossi opened this issue Mar 13, 2024 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@gngrossi
Copy link

bash-5.2$ /bin/touch OP

bash-5.2$ ls -lT OP

  • untagged T=off -rw-r--r-- 1 @02858 @ISSTC00 0 Mar 13 10:10 OP

bash-5.2$ /bin/echo hello >> OP

bash-5.2$ ls -lT OP

  • untagged T=off -rw-r--r-- 1 @02858 @ISSTC00 6 Mar 13 10:10 OP

bash-5.2$ /bin/cat OP
hello

--

bash-5.2$ vim OP
1 <88><85><93><93><96>^U

@IgorTodorovskiIBM
Copy link
Collaborator

This is related to the zoslib heuristic for untagged files. You can try setting export __UNTAGGED_READ_MODE=ASCII to force conversion of untagged files to ASCII. This setting will affect all untagged files and all tools linking to zoslib (which is probably 80% of the tools). If most/all of your untagged files contain 1047 content then this setting is probably preffered for you.

man zoslib for more details

@gngrossi
Copy link
Author

Looks good.
Do you plan to configure vim to set __UNTAGGED_READ_MODE or is this an option for the user?
thanks

@MikeFultonDev
Copy link
Collaborator

@IgorTodorovskiIBM this is a borderline bug I would say since vim gets confused pretty easily, but presumably this also belongs under zoslib and not vim? You ok if we open an issue in zoslib and then close this one?

@MikeFultonDev MikeFultonDev added the bug Something isn't working label Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants