Enrique Kessler Martínez

Hey there, Sure, no problem. The use case that I have in mind is defining the cycle and toggle-type functions only for buffers that are considered popups. Thanks for the...

Sure! I was trying to assign the keys for only buffers in that state, not on every buffer but only applied in a popup buffer. Another example that comes to...

This has been cool to read! Thanks both!

Thanks for the feedback, I agree with your points. I think the suggestion for splitting them comes from the symbols being consumed on the `rune-core` crate, even though probably that's...

I'm good with keeping the symbols together, it makes sense. What I'm thinking is that if we were to move all the symbols back to the main crate (rune) we...

Let's remove the separation between the symbols, so we would have everything on the build.rs. Let's think about the references of that build script on the rune-core, and maybe we...

For the `tagged` issue. If we were to move the `IntoObject` outside the rune-core crate, say with something like this to avoid the orphan rule: ```rust struct Bool(bool); impl IntoObject...

For the cloning issues, we could have a shallow repo, when cloning the submodule just to have the latest commit and that should theoretically improve that (need to check on...

Also wondering whether special symbols, like `true` or `nil` (specially `nil`, since we use it everywhere) should be treated differently. I'm thinking whether `Symbol` should be placed on the main...

Have been testing different commands, to see what gives us the best chance of getting contributors up to speed quickly: ``` ❯ time git clone --depth=1 git://git.sv.gnu.org/emacs.git savannah-emacs Cloning into...