Copy belonging target label shortcut #105
Comments
|
The quickest way to do this currently:
Even easier would be to map these actions to hotkeys. |
|
Thanks!
Is it difficult to expose an aggregate action?
…On Wed, 21 Jun 2017 at 22:15 brendandouglas ***@***.***> wrote:
The quickest way to do this currently:
- right-click > Open Corresponding BUILD file (navigates to the
relevant target in the BUILD file)
- right-click again > Copy BUILD target string
Even easier would be to map these actions to hotkeys.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#105 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABUIF6uWqO6xYnGVG8U-8jQ6USEdQ2T6ks5sGWu7gaJpZM4OBSnp>
.
|
|
Not difficult, it's just that there are many similar actions we could expose, and I don't want to clutter the menus. I could create the action, but not add it to the menu (allowing users to bind it to a hotkey themselves), but then it's not going to be discoverable. |
|
please do...
There's always a tradeoff between discoverability and clutter.
This is the first small thing our internal users asked for... (they asked
for some big things as well :) )
…On Tue, Jul 11, 2017 at 4:48 PM brendandouglas ***@***.***> wrote:
Not difficult, it's just that there are many similar actions we could
expose, and I don't want to clutter the menus.
I could create the action, but not add it to the menu (allowing users to
bind it to a hotkey themselves), but then it's not going to be discoverable.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#105 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABUIF8GJxMs-Tsr8xHtzGq2NOQd97QWSks5sM303gaJpZM4OBSnp>
.
|
@brendandouglas can I have a go at that? It's a feature we use a lot at the moment, and having it be a single action would be of great help! |
|
Sure, please do! |
|
Added a command that adds this functionality (and used it twice myself, already!) I also think this doesn't clutter the context menu too much. Would love if it could stay as is! |
blorente
pushed a commit
to blorente/intellij
that referenced
this issue
Oct 3, 2023
feat: Add commented-out gazelle target to default project view (bazelbuild#104) feat(release): Publish IntelliJ CE version of the plugin. (bazelbuild#103) feat(tools): Add script to check versions (bazelbuild#105) Radar: rdar://110389652 (Opening section of Bazel plugin setup confusing.) Co-authored-by: Daniel Wagner-Hall <[email protected]> build: Add release pipeline for version checker (bazelbuild#109) Co-authored-by: Gibson Fahnestock <[email protected]>
blorente
pushed a commit
to blorente/intellij
that referenced
this issue
Oct 24, 2023
feat: Add commented-out gazelle target to default project view (bazelbuild#104) feat(release): Publish IntelliJ CE version of the plugin. (bazelbuild#103) feat(tools): Add script to check versions (bazelbuild#105) Radar: rdar://110389652 (Opening section of Bazel plugin setup confusing.) Co-authored-by: Daniel Wagner-Hall <[email protected]> build: Add release pipeline for version checker (bazelbuild#109) Co-authored-by: Gibson Fahnestock <[email protected]> feat: capture sdk and bazel plugin info for radar (bazelbuild#117) * feat: capture sdk and bazel plugin info for radar * Fix issues for clion plugin version Co-authored-by: Joshua Harris <[email protected]> build(prb): Make prb test every version of released products build(ci): Increase timeout in Rio build(ci): Key version counters by product build(ci): Make apple version checker publish optional fix: Default to workspace to infer project name (bazelbuild#122) Instead of defaulting to "the parent directory of the project view file", which is rarely what we want. feat: Add support for cc_gtest_testsuite in BUILD files (bazelbuild#121)
blorente
pushed a commit
to blorente/intellij
that referenced
this issue
Nov 1, 2023
feat: Add commented-out gazelle target to default project view (bazelbuild#104) feat(release): Publish IntelliJ CE version of the plugin. (bazelbuild#103) feat(tools): Add script to check versions (bazelbuild#105) Radar: rdar://110389652 (Opening section of Bazel plugin setup confusing.) Co-authored-by: Daniel Wagner-Hall <[email protected]> build: Add release pipeline for version checker (bazelbuild#109) Co-authored-by: Gibson Fahnestock <[email protected]> feat: capture sdk and bazel plugin info for radar (bazelbuild#117) * feat: capture sdk and bazel plugin info for radar * Fix issues for clion plugin version Co-authored-by: Joshua Harris <[email protected]> build(prb): Make prb test every version of released products build(ci): Increase timeout in Rio build(ci): Key version counters by product build(ci): Make apple version checker publish optional fix: Default to workspace to infer project name (bazelbuild#122) Instead of defaulting to "the parent directory of the project view file", which is rarely what we want. feat: Add support for cc_gtest_testsuite in BUILD files (bazelbuild#121) cleanup: Enable --test_output=errors by default
blorente
pushed a commit
to blorente/intellij
that referenced
this issue
Jan 30, 2024
docs(readme): Reformat readme, change rebase process feat: Add commented-out gazelle target to default project view (bazelbuild#104) feat(release): Publish IntelliJ CE version of the plugin. (bazelbuild#103) feat(tools): Add script to check versions (bazelbuild#105) Radar: rdar://110389652 (Opening section of Bazel plugin setup confusing.) Co-authored-by: Daniel Wagner-Hall <[email protected]> build: Add release pipeline for version checker (bazelbuild#109) Co-authored-by: Gibson Fahnestock <[email protected]> feat: capture sdk and bazel plugin info for radar (bazelbuild#117) * feat: capture sdk and bazel plugin info for radar * Fix issues for clion plugin version Co-authored-by: Joshua Harris <[email protected]> build(prb): Make prb test every version of released products build(ci): Increase timeout in Rio build(ci): Key version counters by product build(ci): Make apple version checker publish optional fix: Default to workspace to infer project name (bazelbuild#122) Instead of defaulting to "the parent directory of the project view file", which is rarely what we want. feat: Add support for cc_gtest_testsuite in BUILD files (bazelbuild#121) cleanup: Enable --test_output=errors by default feat(file-a-radar): add IntelliJ log to File a Radar draft Turns out to be surprisingly easy to attach IntelliJ logs to the created radar draft. rdar://117680933 ([IDE] Capture IntelliJ log when Filing a Radar) docs: Rewrite release instructions (bazelbuild#155)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
Is there a way to copy the target label a file belongs to? The idea is that many times when I want to add a dependency on a class I can use
CMD+Nto find the file and thenCMD+SHIFT+Cto copy the file path. From there it's a bit of fiddling to get the target name.Is there a simpler way in the plugin?
It seems that you already know which target the file belongs to.
The text was updated successfully, but these errors were encountered: