Moritz Mœller

Please reopen this. I think you really need to test with all (or a lot more) `clap_derive` attributes before this is fixed. :) It seems the `config` macro wraps members...

I'm sorry I'm just getting to testing this now. Thanks heaps for the fix! I will provide feedback asap.

Here is another example that doesn't work as expected: ```rust use clap::{CommandFactory, Parser, Subcommand}; use serde::{Deserialize, Serialize}; use std::{ fs::File, path::PathBuf, ffi::OsStr, }; use twelf::{config, Layer}; pub const HELP_TEMPLATE: &str...

I'm not the author of t`twelf`. I tried it and it wasn't working. So I opened the issue. I haven't revisited it since @bnjjj just reopened it after that `Option`...

Yes, of course. The idea is that you can grab the repo w/o this. I also found Git LFS to be more stable downloading such large files over spotty connections.

That sucks. I never converted a repo. I only set up new repos with LFS. I presume you also found [_this_](https://support.atlassian.com/bitbucket-cloud/docs/use-bfg-to-migrate-a-repo-to-git-lfs/) via google and it doesn't help?

That's why they tell you to backup the repo. :] I have a pristine copy from today, in case anything goes wrong.

Maybe the binary files are now staged for commit? `git lfs ls-files` won't list files which are not committed yet. Did you try `git lfs status`? Edit: [this thread](https://github.com/git-lfs/git-lfs/issues/700) helped...

Ah, it's amazing enough you tried immediately. I just created this issue so I don't forget. Didn't expect anyone to jump on it right away. Cheers for the effort.

> Can you give an example how exactly you would split it up? I would copy the guide's `Reading an Image`->`Layer` section under a `Layer` struct docs `Reading` section and...