An 8 yearsPhpStorm User configuration sharing
I have been using PhpStorm for a long time, almost 8 years . Since 2012 to be more precise. It was the third edition at that time. A lot happened during that time and a lot of changes took place. certainly. You learn a lot every day. This article is a summary of my 8 years of experience with PhpStorm. These are my best settings to make you a faster developer and let you focus on more important things.
If you don't care about the exact settings and their purpose, you can download my snapshot (containing my personal GitHub and Material themes) and import it into PhpStorm via File > Import Settings. Just scroll to the end of this article to find what you need.
My Best Settings
I will only show you the settings you need to change, they are different from the default settings. [ ] to deselect or [x] to select.
General
Hide all unnecessary things
View > Appearance
● [ ] Toolbar
● [ ] Tool Window Bars
● [ ] Status Bar
● [ ] Navigation bar
Settings
Appearance & Behavior > Appearance
● [ ] Animate windows
No improvement, but will reduce performance
● [x] Show memory indicator
If you use the status bar to better understand memory usage
● [ ] Show tool window bars
Remove more useless status bars
● [ ] Show tool window numbers
Delete more useless status bars
Appearance & Behavior > System Settings
● [ ] Reopen last project on startup
I develop multiple projects at the same time, so I want to choose which project should be opened at the beginning
● [ ] Confirm application exit
If I want Exit the application, which should close immediately without any confirmation
● [x] Open project in new window
PhpStorm allows you to open a project in the same window as the current project. This is 99% not what you want.
Appearance & Behavior > File Colors
● [ ] Enable File Colors
● [ ] Use in Editor Tabs
● [ ] Use in Project View
Maybe you like it, maybe you don’t. I have no idea. These options remove the file color and background color from labels and directory numbers for some special folders such as node_modules or tests .
Shortcut keys
Basically I use the default shortcut keys, but I still modified the following shortcut keys to improve my efficiency.
Translator's Note: Cmd in macbook is equivalent to Alt in Windows.
● Ctrl V Split Vertically
Split vertically.
● Ctrl H Split Horizontally
Split horizontally.
● Cmd T Run...
If you are in a test file, you only need to press this shortcut key in the method to test the method.
● Shift Cmd T Run
This shortcut key can be used anywhere in the program. It just runs the last test again.
● Ctrl W Hide Active Tool Window
When running a test, the test window will open. This may also be useful if you use the terminal in PhpStorm. You can turn it off at any time using this shortcut key.
● Cmd 2 Select in Project View
You probably know this by now. Use Cmd 1 to toggle the sidebar. I still frequently need to jump into the sidebar project tree. I often use Shift Shift to search everything, or Cmd O to search for classes. So I never use sidebars. However, this shortcut works great if you want to access the menu using the currently open file.
Editor > General
● [ ] Enable Drag'n'Drop functionaliy in editor
This option is actually very useless. If you don't disable it, it can move the code around with the mouse, which happens often even if you don't want it to.
● [ ] Show notification after reformat code action
● [ ] Show notification after optimize imports action
● [x] Soft-wrap-files
This is a very cool feature. When you edit a Markdown file, lines never wrap. Using this option you can change it. They have him encapsulated now.
Strip trailing spaces on Save: All
This command removes all trailing spaces on each individual save command (PhpStorm will save automatically if tabs are not used).
● [ ] Always keep trailing spaces on caret line
● [x] Ensure line feed at file end on save
Use this option to ensure that there is a line feed at the end of the file Blank line.
Editor > General > Appearance
● [ ] Show hard wrap and visual guides
● [ ] Show code lens on scrollbar hover
This will remove the "preview" of the code when you hover over a specific location on the scrollbar.
Editor > General > Breadcrumbs
● [ ] Show Breadcrumbs
We don’t need breadcrumbs. So we disable it. We like the clean user interface.
Editor > General > Code Completion
● [x] Show full method signatures
We want to view when the code completion of the method is started All content.
Editor > General > Code Folding
Personally, I don't like any code folding because I want to see the code I write.
● [ ] Show coding folding outline
● [ ] File header
● [ ] Imports
● [ ] HTML 'style' attribute
● [ ] XML entities
● [ ] Data URIs
● [ ] Imports
Editor > General > Editor Tabs
● Appearance: None
If you don’t use tabs, I recommend you use this setting. You can use Cmd E to get recent files or Shift Shift for quick search. Therefore, there is no need to display these tabs.
Editor > General > Smart Keys > PHP
● [ ] Enable smart function parameters completion
● [ ] Select variable name without '$' sign on double click
If I double-click the variable, I don't want it to select the $ sign, so I don't enable that setting.
Editor > General > Font
This configuration is more personalized, you can choose according to your own preferences. The following is the configuration that suits me
● Font: Menlo
● Size: 15
● Line spacing: 1.9
Editor > General > Color Scheme > General
If you are like me and don't like these method delimiters, you can disable them. There is currently no way for you to disable the separator for use statements, but there is a workaround, just unset the foreground color for the following entries
● [ ] Method separator color, Foreground
Editor > General > Code Style
● Line Seperator: Unix and macOS
Editor > General > Inspections
you You may wonder why I didn't explain it. List making is very complex. I've made some adjustments here for Laravel so that you can have a clean environment instead of annoying underlines. My spell checker is also available in the download. If you have any questions please let me know.
Editor > General > Inlay Hints
● [ ] Show hints for:
I don’t need to show hints.
Languages & Frameworks > PHP > Debug
● [ ] Force break at first line when no path mapping specified
● [ ] Force break at first line when a script is outside the project
When using Laravel Valet, you should break both. Otherwise, xdebug will start debugging in Valet.
Tools > Web Browsers
[ ] Show browsers popup in the editor
Do you remember all the previews with the little browser icons? ? You can disable it.
Conclusion
This IDE is as clean and intuitive as Sublime, but with more integrated IDEs than Sublime.
Am I missing anything? If you have any other practical tips you can help me make PhpStorm better. let me know.
The above is the detailed content of Configuration sharing from an 8-year PhpStorm user. For more information, please follow other related articles on the PHP Chinese website!