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 "copy to clipboard" command to History tab #3219

Open
jmcphers opened this issue Jul 25, 2018 · 8 comments
Open

Add "copy to clipboard" command to History tab #3219

jmcphers opened this issue Jul 25, 2018 · 8 comments

Comments

@jmcphers
Copy link
Member

@jmcphers jmcphers commented Jul 25, 2018

Request from an RStudio Server user (paraphrased):

I often want to copy R commands from one R session to another. I use the History tab, click To Console or To Source, then copy and paste the emitted command. It'd be a lot easier if I could just copy the command directly via Ctrl+C or a toolbar button.

@aronatkins
Copy link
Contributor

@aronatkins aronatkins commented Sep 12, 2018

Similar workflow: Browse history and copy a command to paste elsewhere (Github comment, email, some other editor).

@DDorch
Copy link

@DDorch DDorch commented Nov 3, 2020

I also search for this functionality for the same reason. It's annoying to double-click on an item of the history tab to get it in the console and then select it for copying it.

The weird thing is that if you right-click on a row of the history tab a menu with "Cut, Copy, paste and Select All" items appears. But the "copy" item is disable and I don't understand what can do the "Paste" command in this context.

@stale
Copy link

@stale stale bot commented Feb 4, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs, per https://github.com/rstudio/rstudio/wiki/Issue-Grooming. Thank you for your contributions.

@stale stale bot added the wontfix label Feb 4, 2021
@mikebessuille mikebessuille added stale Issues which have been closed automatically due to inactivitiy. and removed wontfix labels Feb 4, 2021
@stale stale bot removed the stale Issues which have been closed automatically due to inactivitiy. label Feb 4, 2021
@aronatkins
Copy link
Contributor

@aronatkins aronatkins commented Feb 5, 2021

Please keep this alive.

@HenrikBengtsson
Copy link
Contributor

@HenrikBengtsson HenrikBengtsson commented Jun 22, 2021

Adding my upvote for this one:

I just observed a beginner testing out a few commands in the console, which they then wanted to copy-and-paste into their Rmarkdown document. The obvious attempt to copy from the 'History' panel ended with confusion by trying to figure out why 'Copy' was disabled while 'Paste' wasn't (see screenshot). What does 'Paste' mean here?
flameshot_2021-06-22T140818.

The advantage of being able to copy from the 'History' panel is that you'll only copy the command called, and none of it's output, which you otherwise have to deal with if you copy from the console. Also, re-running commands in the 'History' panel just to be able to copy from there is also inferior; you might trigger a long running task or produce lots of output that you have to scroll back over, plus you might now want to run that command again, e.g. file.remove(), install.package(), etc.

@github-actions
Copy link

@github-actions github-actions bot commented Feb 17, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs, per https://github.com/rstudio/rstudio/wiki/Issue-Grooming. Thank you for your contributions.

@github-actions github-actions bot added the stale Issues which have been closed automatically due to inactivitiy. label Feb 17, 2022
@colearendt
Copy link
Member

@colearendt colearendt commented Feb 18, 2022

Stale bot, stale bot,
Why must you
Threaten to close
All issues

@stale stale bot removed the stale Issues which have been closed automatically due to inactivitiy. label Feb 18, 2022
@pymrkc
Copy link

@pymrkc pymrkc commented Apr 19, 2022

👍

@mikebessuille mikebessuille added this to the 2024 milestone Jun 21, 2022
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

7 participants