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

Command-C messes up capitlization #14

Open
raysalemi opened this issue Feb 19, 2014 · 5 comments
Open

Command-C messes up capitlization #14

raysalemi opened this issue Feb 19, 2014 · 5 comments

Comments

@raysalemi
Copy link

While I understand that Emacs uses esc-W for copy, the command-C should either do a copy or nothing. The capitalization behavior messes me up constantly.

Thanks!
Ray

@glyph
Copy link
Owner

glyph commented Feb 19, 2014

To quote Emacs itself,

M-c runs the command capitalize-word
  which is an interactive built-in function in `C source code'.
It is bound to M-c.

Capitalize the following word (or ARG words), moving over.

So this is "accurate" behavior; the real problem for my fingers is that it doesn't move over like Emacs does, and instead leaves the cursor in place :-).

Perhaps you could come up with a PR that allows local configuration for disabling certain keystrokes? Or perhaps you should re-map "meta" to a key other than command?

@raysalemi
Copy link
Author

But ESC-C is different than Command-C in a pretty fundamental way.

ESC-C is two keystrokes while Command-C is one keystroke.

So Command-c is not really an implementation of M-c.

I'd be happy to check out the remapping options. How would I do that?

Thanks!

Ray

On Wed, Feb 19, 2014 at 12:48 PM, Glyph notifications@github.com wrote:

To quote Emacs itself,

M-c runs the command capitalize-word
which is an interactive built-in function in `C source code'.
It is bound to M-c.

Capitalize the following word (or ARG words), moving over.

So this is "accurate" behavior; the real problem for my fingers is that
it doesn't move over like Emacs does, and instead leaves the cursor in
place :-).

Perhaps you could come up with a PR that allows local configuration for
disabling certain keystrokes? Or perhaps you should re-map "meta" to a key
other than command?

Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-35526708
.

Author of "FPGA Simulation: A Complete Step-by-Step Guide"
www.fpgasimulation.com

@glyph
Copy link
Owner

glyph commented Feb 19, 2014

@rdsalemi - In E-Max, on the mac, by default, Meta (M-) is interpreted to be Command. Hence, just like M-w is Command-w, M-c is Command-c.

However, E-Max ought to support command prefixing, so you can literally tap ESC then W to get the same keystroke.

There's no remapping options right now, but if you look at emax_build_keymaps.py you can see that it's building sublime keymaps by interpreting a value for "meta". If you could read a user configuration at that point and refuse to generate certain mappings then you could configure this away. Also that's where the ESC prefix would need to be implemented.

In any case somebody's going to have to write some code here, I'm more than happy to review any pull requests :-).

@raysalemi
Copy link
Author

Thanks! I will take a look.

On Wed, Feb 19, 2014 at 2:49 PM, Glyph notifications@github.com wrote:

@rdsalemi https://github.com/rdsalemi - In E-Max, on the mac, by
default, Meta (M-) is interpreted to be Command. Hence, just like M-w is
Command-w, M-c is Command-c.

However, E-Max ought to support command prefixing, so you can literally
tap ESC then W to get the same keystroke.

There's no remapping options right now, but if you look at
emax_build_keymaps.py you can see that it's building sublime keymaps by
interpreting a value for "meta". If you could read a user configuration at
that point and refuse to generate certain mappings then you could configure
this away. Also that's where the ESC prefix would need to be implemented.

In any case somebody's going to have to write some code here, I'm more
than happy to review any pull requests :-).

Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-35540147
.

Author of "FPGA Simulation: A Complete Step-by-Step Guide"
www.fpgasimulation.com

@glyph
Copy link
Owner

glyph commented Feb 19, 2014

Thanks for your report!

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