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

Support for more layouts in mac2linux #98

Open
naphta opened this issue Apr 22, 2021 · 2 comments
Open

Support for more layouts in mac2linux #98

naphta opened this issue Apr 22, 2021 · 2 comments

Comments

@naphta
Copy link

naphta commented Apr 22, 2021

I did have a search and didn't see anyone else having done this, I'm opening up the issue just in-case there are other followers here who are interested in how they'd like to see it approached.

My rough thinking was to put some basic flags in which can select on the most common layouts, perhaps qwerty and dvorak in addition to colemak?

Happy to have a pass at this myself (with my close to non existent C experience, although it looks straightforward enough).

I was tempted to pull it out into a separate project since it'd be unfair to bloat your dotfiles with features you wouldn't use, and it seems like a useful enough setup to be worth sharing more generally.

@wincent
Copy link
Owner

wincent commented Apr 22, 2021

I was tempted to pull it out into a separate project since it'd be unfair to bloat your dotfiles with features you wouldn't use, and it seems like a useful enough setup to be worth sharing more generally.

Generally I think the best approach is to fork the dotfiles and make them your own. Or "steal" from them by taking the bits that you consider useful. Having said that, I don't mind adding features — even ones I don't use — as long as they don't bring too much complexity. Obviously, exactly what constitutes "too much" is a matter of subjective judgment.

As for the specific thing you're talking about here (more layouts), I suspect that mac2linux is "pre-alpha" at this stage, which means it could change a lot in the future. So, not exactly solid ground on which to build... 😂

All of which is to say, it's up to you whether you want to have a try.

@naphta
Copy link
Author

naphta commented Apr 22, 2021

@wincent It's exactly that pre-alphaness I'm keen to jump on the bandwagon of. It'd be nice to provide extra layout without making it a pain to rebase in the future.

I'll have a pass at it, the way it's been written so far looks fairly permissive on the layout front anyway.

Anything worth looking at "while I'm in there" from your point of view?

The important part really is the rules moreso than the rest of it.

wincent added a commit that referenced this issue Jul 11, 2022
Seeing as the other base16 submodule just broke, I thought I'd check
this related one for breakage too, but this one hasn't had its default
branch deleted, and just some minor updates:

* vendor/base16-templates-source 420ca45...3af55c8 (8):
  > Update README.md
  > Merge pull request #105 from krgn/master
  > Merge pull request #102 from bradcush/feat/base16-nvim
  > Merge pull request #101 from wincent/patch-1
  > Merge pull request #98 from fmunch/mate-terminal
  > Merge pull request #97 from ArenM/master
  > Merge pull request #95 from MArpogaus/master
  > Merge pull request #92 from Misterio77/patch-2
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

2 participants