Kevin Lu

What about https://github.com/alexanderwallin/node-gettext?

I can contribute something for the YDKe URLs on YGOProDeck. I'd need to know at what part of the codebase to inject it though.

I'm referring to a base64 url format like so ``` ydke:///7pZBN5skgDebJIA3mySAIUG5QGFBuUBhQblAadZ+gGNsEEEktETAgdIdR7imfcA4pn3AG9N/wGRkeEBkZHhAfJAdR5P0O0BT9DtAawJdAR0RysBkQerAvstxAL7LcQCSnBJA2++MQRvvjEEkw08BJMNPAQ5QFgE+Sm+BO8nUQBwwzgEEtmgAvuaMQN8QQEFfEEBBXxBAQX4QHUeO0nJBQ==!oPs6BV+NLAX2ZNEA5+34Auft+AI0cV8F5a3yA+Wt8gNTzMUEU8zFBFPMxQSKhTYESzzJA0s8yQNLPMkD!! ```

Why does the README even claim fuzzy search when it's not a thing?

Is this a fresh environment? If the files already exist in `~/.mc` then I don't expect the message to appear.

I should clarify that I'm running this against MinIO specifically and not the local file system. When I run your commands, which deal with the local file system, the output...

If this is intended behaviour then maybe this is a better topic for documentation? I learned of the flag from the [admin client docs](https://docs.min.io/docs/minio-admin-complete-guide.html), section 6, and I really did...

Alright. If the Go parser position issue cannot be worked around, I suggest sending diagnostic messages to stderr if possible to avoid clobbering regular output. I will keep in mind...

:eyes:

~I just encountered this bug as well. I wonder what the root cause is?~ Nevermind, just found the fixing #248... almost two months