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

Avoid keymap <F1> ? #1

Closed
wedgwood opened this issue Aug 15, 2012 · 4 comments
Closed

Avoid keymap <F1> ? #1

wedgwood opened this issue Aug 15, 2012 · 4 comments

Comments

@wedgwood
Copy link

Hi joonty, thanks for your great plugin.
I have some trouble in keymap conflicting.
I think the default keymap <F1> should be changed. Because On many platform, is about ask help from os.

@joonty
Copy link
Collaborator

joonty commented Aug 15, 2012

Hi wedgwood,

Glad you like it!

You can change all the default keymaps, see the help section with

:help VdebugKeys

In your .vimrc file set:

let g:vdebug_keymap['run_to_cursor'] = 'enter key here'

I'll leave this issue open for a bit just in case you have any problems doing this.

@blueyed
Copy link
Contributor

blueyed commented Aug 15, 2012

While it is nice being able to change this via configuration, I think the defaults can be improved:

  • Only add the majority of the mappings when the debugger is started, i.e. after pressing <F5>. Only after that all the other mappings get setup, and will be unmapped after pressing <F6> ("close").
  • Allow for configuration of a Vdebug leader key, which gets prepended to all maps. This could be configured as <Leader>d, which would result in maps like ",d". This would allow to easily use a separate namespace for all of Vdebug's mappings.

@joonty
Copy link
Collaborator

joonty commented Aug 15, 2012

Like it - I've tagged this issue as an enhancement and I'll get that feature in when I can.

Thanks

@zhaocai
Copy link
Contributor

zhaocai commented Aug 23, 2012

I think it is better to map most of the keys to the debug related . only a few keys have general meanings to run globally.

joonty added a commit that referenced this issue Aug 23, 2012
Run and set breakpoint keys are available when Vim starts, but all other
key maps are set when the debugger is started, and unmapped when the GUI
is closed. Also, a leader key can be set with g:vdebug_leader_key
@joonty joonty closed this as completed in 3e44bc5 Aug 28, 2012
joonty added a commit that referenced this issue Apr 4, 2013
Run and set breakpoint keys are available when Vim starts, but all other
key maps are set when the debugger is started, and unmapped when the GUI
is closed. Also, a leader key can be set with g:vdebug_leader_key
joonty added a commit that referenced this issue Apr 6, 2013
Run and set breakpoint keys are available when Vim starts, but all other
key maps are set when the debugger is started, and unmapped when the GUI
is closed. Also, a leader key can be set with g:vdebug_leader_key
paprykarz pushed a commit to paprykarz/vdebug that referenced this issue Dec 25, 2016
Now the setting continuous_mode, if set, is working again: debugger
starts listening on finished debugging session.
reafle added a commit to reafle/vdebug that referenced this issue Oct 8, 2017
Vim and Neovim seem to manage windows differently.
This patch removes redundant window search for source window
and assumes that the source window is always vim-vdebug#1.
BlackIkeEagle pushed a commit that referenced this issue Feb 21, 2018
Vim and Neovim seem to manage windows differently.
This patch removes redundant window search for source window
and assumes that the source window is always #1.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants