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

hydra editing workflow? #32

Open
odanoburu opened this issue Oct 31, 2018 · 1 comment
Open

hydra editing workflow? #32

odanoburu opened this issue Oct 31, 2018 · 1 comment

Comments

@odanoburu
Copy link
Owner

odanoburu commented Oct 31, 2018

No description provided.

@odanoburu
Copy link
Owner Author

odanoburu commented Nov 3, 2018

a276206 adds the editing commands.

further ideas would be

  • navigation commands (done in add navigation commands to editing hydra #33)
  • clearing command
  • flycheck integration:
    • disable minibuffer errors when editing (checking if flycheck is active by variable flycheck-mode, then setting flycheck-display-errors-function to nil temporarily)
      done using this technique, but showing the errors in the hydra (or else one has to quit it to see the error, then call it again to fix it).
    • adding next/previous flycheck error navigation (using a dynamic hydra dynamically created hydras? abo-abo/hydra#164 that checks if flycheck is on)
      there is no real need for a dynamic hydra. although it would be nice, it's probably not worth the effort.

odanoburu added a commit that referenced this issue Nov 25, 2018
- when editing field interactively, only delete old value after new
  one has been provided (closes #35)
  - this prevents flycheck-checker from running unnecessarily
- don't change =flycheck-display-errors-function=, as the end result
  is basically the same and it probably is what's slowing emacs down
  (related to #32)
  - change delay for showing errors instead, and put message in hydra
- refactor some names
- move to next flycheck error preserving alignment
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

1 participant