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

Add new bindings to ESS layer #4176

Closed

Conversation

andrew-christianson
Copy link

Reopening #4166 with on a separate branch in my fork + resolve the merge conflict with #4150.

Commit Message:

Add new evil-leader bindings for lots of the functions behind
ess-dev-map and ess-doc-map. Major additions are SPC m d for IDE-like
commands (roxygen, style), SPC m b for debugger interaction, and a few
extras in SPC m s and SPC m h.

Also add a few new layer variables controlling the indenting style, and
update README for all.

Useful, IDE like functions.
| Key Binding | Description |
|-------------+--------------------------------------------------------------------------------------------|
| ~SPC m d l~ | ~(ess-developer-load-package)~ load a specified directory with ~devtools::load_all~ |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please, avoid function names here. People usually far more interested in what it does 😸

@d12frosted
Copy link
Collaborator

Wow, this is an old one PR. Is it still relevant? 😸

P. S. Sorry for taking so long 😢

@andrew-christianson
Copy link
Author

Spacemacs + ESS is still my daily driver @ work so it's still relevant to me :). I've been using the stock layer for a while now for convenience sake, though I'd love to come back to this and incorporate the above + resolve the conflicts if you guys would consider it.

- [[#Developer][Developer]]
- [[#debugging][Debugging]]
- [[#help][Help]]
- [[Install][Install]]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aren’t these links supposed to start with #? And if you change them to use # (and without initial capital letters) instead, you will get a smaller diff (reduced to your additions only).

I just ran ./core/tools/spacefmt/spacefmt all while on your branch, which indeed changed these lines to #. So you should probably use #.

To use this configuration layer, add it to your =~/.spacemacs=. You will need to
add =ess= to the existing =dotspacemacs-configuration-layers= list in this
file.
To use this configuration layer, add it to your =~/.spacemacs=. You will need to
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spurious change. Only changes whitespace (indentation). Same for many of the hunks below this one.

@LemmingAvalanche
Copy link
Contributor

Btw: the email addresses of your “author” and “committer” are different on one of the commits, which makes one of the commits show up as “andrew committed with andrew” on GitHub. ☺

@nikolaiam
Copy link
Contributor

R support was one of the chief reasons for me to start using Spacemacs, so very relevant to me as well! Would love to see this merged 😊

andrew-christianson and others added 4 commits June 5, 2017 14:42
Add new evil-leader bindings for lots of the functions behind
ess-dev-map and ess-doc-map. Major additions are SPC m d for IDE-like
commands (roxygen, style), SPC m b for debugger interaction, and a few
extras in SPC m s and SPC m h.

Also add a few new layer variables controlling the indenting style, and
update README for all.
@robbyoconnor
Copy link
Contributor

Copy link
Contributor

@robbyoconnor robbyoconnor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@TheBB
Copy link
Collaborator

TheBB commented Jun 7, 2017

I'd be happy to merge at least the first commit if you make the changes that have been proposed, and bring the company integration up to scratch with current Spacemacs.

@bmag bmag mentioned this pull request Oct 23, 2017
@github-actions
Copy link

This PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this PR is still need merging!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Sep 30, 2020
@github-actions github-actions bot closed this Dec 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement ☺ stale marked as a stale issue/pr (usually by a bot)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants