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

『エンジニア目線で使ってみて便利だったChrome拡張の紹介』を書いた #177

Merged
merged 1 commit into from
Dec 13, 2024

Conversation

kyu08
Copy link
Owner

@kyu08 kyu08 commented Dec 12, 2024

No description provided.

@kyu08 kyu08 force-pushed the chrome-extensions-for-dev-2024 branch 5 times, most recently from cb83312 to cf6019f Compare December 12, 2024 16:05

あらゆる操作をキーボードだけで行いたいと考えている筆者にとってはなくてはならない拡張です。

基本的な操作方法についてはたくさんの情報があると思いますのでここでは筆者のキーマップや最近知った機能について紹介します。

Choose a reason for hiding this comment

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

🚫 [textlint] <eslint.rules.ja-technical-writing/ja-no-weak-phrase> reported by reviewdog 🐶
弱い表現: "思います" が使われています。 (ja-technical-writing/ja-no-weak-phrase)

map e scrollUp
```

また、最近知ったvimiumの機能についても紹介したいと思います。ふと[README](https://github.com/philc/vimium)を眺めていたら

Choose a reason for hiding this comment

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

🚫 [textlint] <eslint.rules.ja-technical-writing/ja-no-weak-phrase> reported by reviewdog 🐶
弱い表現: "思います" が使われています。 (ja-technical-writing/ja-no-weak-phrase)

## find+ | Regex Find-in-Page Tool
[find+ | Regex Find-in-Page Tool](https://chromewebstore.google.com/detail/find+-regex-find-in-page/fddffkdncgkkdjobemgbpojjeffmmofb)

正規表現を使ってページ内検索を行うことができるChrome拡張です。

Choose a reason for hiding this comment

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

🚫 [textlint] <eslint.rules.ja-technical-writing/ja-no-redundant-expression> reported by reviewdog 🐶
【dict5】 "検索を行う"は冗長な表現です。"検索する"など簡潔な表現にすると文章が明瞭になります。
解説: https://github.com/textlint-ja/textlint-rule-ja-no-redundant-expression#dict5 (ja-technical-writing/ja-no-redundant-expression)

便利です。

## おわりに
Chrome拡張開発者のみなさんに圧倒的感謝...!

Choose a reason for hiding this comment

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

🚫 [textlint] <eslint.rules.ja-technical-writing/no-exclamation-question-mark> reported by reviewdog 🐶
Disallow to use "!". (ja-technical-writing/no-exclamation-question-mark)

@kyu08 kyu08 force-pushed the chrome-extensions-for-dev-2024 branch 3 times, most recently from 8e81523 to 1611791 Compare December 12, 2024 16:09

![notion-sidebar-tamer-before.gif](notion-sidebar-tamer-before.gif)

そこでNotion Sidebar Tamerを使うとカーソルをサイドバー付近に移動してもサイドバーが表示されなくなります。やったね!

Choose a reason for hiding this comment

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

🚫 [textlint] <eslint.rules.ja-technical-writing/no-exclamation-question-mark> reported by reviewdog 🐶
Disallow to use "!". (ja-technical-writing/no-exclamation-question-mark)

@kyu08 kyu08 force-pushed the chrome-extensions-for-dev-2024 branch from 1611791 to 2e9517b Compare December 12, 2024 16:11
## おわりに
Chrome拡張開発者のみなさんに圧倒的感謝...!

[^1]: このケースだとカーソルを右側に持っていってコピーすることもできますが普段は左側に持っていかないとコピーが難しいケースが多いためこのように書いています。具体的なケースが思い出せたら記事を修正しようと思います。

Choose a reason for hiding this comment

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

🚫 [textlint] <eslint.rules.ja-technical-writing/ja-no-redundant-expression> reported by reviewdog 🐶
【dict2】 "することもできます"は冗長な表現です。"することも"を省き簡潔な表現にすると文章が明瞭になります。
解説: https://github.com/textlint-ja/textlint-rule-ja-no-redundant-expression#dict2 (ja-technical-writing/ja-no-redundant-expression)

## おわりに
Chrome拡張開発者のみなさんに圧倒的感謝...!

[^1]: このケースだとカーソルを右側に持っていってコピーすることもできますが普段は左側に持っていかないとコピーが難しいケースが多いためこのように書いています。具体的なケースが思い出せたら記事を修正しようと思います。

Choose a reason for hiding this comment

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

🚫 [textlint] <eslint.rules.ja-technical-writing/ja-no-weak-phrase> reported by reviewdog 🐶
弱い表現: "思います" が使われています。 (ja-technical-writing/ja-no-weak-phrase)

@kyu08 kyu08 force-pushed the chrome-extensions-for-dev-2024 branch 4 times, most recently from e196dca to 4dc93d0 Compare December 13, 2024 01:42
@kyu08 kyu08 force-pushed the chrome-extensions-for-dev-2024 branch from 4dc93d0 to d22fc4e Compare December 13, 2024 01:43
@kyu08 kyu08 marked this pull request as ready for review December 13, 2024 01:43
@kyu08 kyu08 merged commit cfdc4e5 into main Dec 13, 2024
1 check passed
@kyu08 kyu08 deleted the chrome-extensions-for-dev-2024 branch December 13, 2024 01:44
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

Successfully merging this pull request may close these issues.

1 participant