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

Reject default token if not last #18

Open
nerab opened this issue Mar 18, 2014 · 2 comments
Open

Reject default token if not last #18

nerab opened this issue Mar 18, 2014 · 2 comments

Comments

@nerab
Copy link
Contributor

nerab commented Mar 18, 2014

There can be only one default token, and it must be after all machine tokens. The code should enforce that.

@geemus
Copy link
Contributor

geemus commented Mar 18, 2014

@nerab yeah, I don't know that it makes a huge difference. ie I'm not sure we should worry too much when parsing if it isn't last. That said, we should ensure when we write netrc files that if they include default it gets written last. ie perhaps it would be best to be lenient toward input but strict on output, at least as a first pass.

@Vyazovoy
Copy link
Contributor

Vyazovoy commented May 7, 2024

@nerab, should this ticket be closed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants