I am using Sublime Text 2 and it is great.
I use it to write html, css and ruby.
I have a problem when I edit my spec files, because it adds and removes blank lines in the whole file and makes the git log unreadable.
this is the git diff
Seems like your editor is configured to remove trailing whitespace and other developers in the team don't use that setting. Or vise versa. they remove whitespace and you don't.
Therefore I suggest to use the same settings in the whole team.
To enable or disable that feature, go to SublimeText 2 > Preferences > User Settings and add
"trim_trailing_white_space_on_save": true
or
"trim_trailing_white_space_on_save": false
to the configuration
Related
About Translate JMeter projects,
I follow the translating steps and open I18NEdit,
I see the translation text options but I notice that I can't localize Menu items as File, Exit,..
It seems that there are texts (messages.properties) that can't be localized.
Is messages.properties localization is done manually by adding messages_[locale].properties?
Am I missing something ? Is it on purpose or should an enhancement be opened?
We don't really use i18nedit for translation. But you can still use it.
Anyway, Internationalization in JMeter is based on properties files:
src/core/org/apache/jmeter/resources/messages_[locale].properties
src/components/..../*.properties (except some like colors.properties)
src/protocol/..../*.properties
No need to translate deprecated components.
The 2 latter are related to components that rely on TestBean approach (no specific GUI)
Note that a PR (github mirror) is preferred over a patch:
https://github.com/apache/jmeter/blob/trunk/CONTRIBUTING.md
I am using Visual Studio Code on my Ubuntu box and when I checked in my code into BitBucket, somehow they are in different alignment, see below.
What would have caused this and how to I rectify this?
Your code almost certainly contains both tabs and spaces for indentation.
When this happens, almost any difference in how tabs are rendered will lead to anomalies such as you've shown above--code that looks right in one rendering looks all wrong in another.
Most code editors include ways to convert the entire file to using either spaces or tabs, but not a combination of the two. Using only spaces probably does the most to guarantee that the code will look the same, regardless of the environment.
On the other hand, using only tabs means that each user will probably see the code as s/he normally views code (at least assuming s/he has his/her environment set up to deal with tabs). For example, if the code is indented with tabs, and you like indentation to be by 8 spaces, but I prefer 4 spaces, each of us can get exactly that from identical source code (i.e., most editors will let us set the tab stops as we see fit).
Select the whole document or the line you have problem with,
Then go to Edit -> Advanced -> Tabify Selected Lines
That should fixed the issue. More info : https://blogs.msdn.microsoft.com/zainnab/2010/03/14/how-to-convert-tabs-to-spaces-and-vice-versa/
How to go about ignoring empty lines in the gerrit Diff View?
I have already turned the "Ignore Whitespace" to "All" in the Diff Preferences but I would like to hide added or removed empty lines in the Side by Side new change screen:
This is not possible in Gerrit.
Everything about Gerrit's diff screen that can be customized is listed here, nothing about empty lines is mentioned. Neither is it anywhere else in the settings.
I thought it might be possible if you were to edit Gerrit's diff script, but from the looks of it that is not a viable way either. If you search for "git diff ignore empty lines" you'll find about zero useful hits.
There is however this unofficial project that makes it possible to ignore empty lines that are not close to important changes, so even if you were to somehow edit the way Gerrit handles diffs, that wouldn't really do what you want.
Every time I type if and press the space bar, Delphi completes it with if True then and a new empty line above.
Is there a way to remove this "autocomplete" feature or at least edit it to not create the new line?
From the Tools | Options | Editor Options | Code Insight menu, deselect the Auto complete check box under Code template completion.
Once you disable template auto complete then you need to manually invoke the template if you want it. Do that with CTRL+J.
That's called a live template, and you can edit the list of live templates in the template window, from the View menu.
Find the template you don't like, select it, and click the "remove template code" button.
Since the default location for the live code templates is C:\Program Files (x86)\Embarcadero\Studio\16.0\ObjRepos\en\Code_Templates (for XE8, similar for other editions), you will need to change the permissions on this directory (and its subdirectories) in order to edit or add live templates. Default permissions do not include write permission to this directory.
I'm trying to do a block selection using jVi in Netbeans. I cannot seem to get it working - there seems to be a lot of good info on this topic, however I'm not seeing the answer to my problem.
This is what I understand: to do a block select, you first enter visual mode and select some text. Then you hit Ctrl-V to enter block select mode? For me, Ctrl-V pastes the clipboard, so I found someone mentioned Ctrl-Q. I try that, but I cannot get text to select in a column using the arrow keys or the h,j,k,l keys. For me, it just does a regular selection grabbing the rest of the line, and the line below (if I move the cursor down) up to the cursor.
What am I missing?
jVi has options to specify which control keys are handled by jVi and which passed on to NetBeans for processing. Your description indicates that Ctrl-V is being handled by NB (not by jVi). In NetBeans look at
Tools > Options > jViConfig > Ctrl-Key Bindings
and enable/check the keys that jVi should process.
Make sure you're not in a special more before you start (just press ESC a few times). It's also possible that some of your jVi startup scripts are remapping those keys.
Ctrl-V is the default, but Ctrl-Q was introduces on gvim on Windows, to avoid confusing users who knew Ctrl-v is for pasting text. You can look at your key mappings by typing
:map
in command-mode. You can even do
:verbose map
to find out where each mapping was defined. I think that only lists user-set mappings, so it'll show you when Ctrl-V and Ctrl-Q were re-defined by a script.
This worked for me - combining both suggestions from above. In jVi settings page, enable Ctrl-Q and use it for classic Ctrl-V functionality. Do not enable Ctrl-V as it has too many side effects wrt handling of mouse selection buffer. Works nicely in this way for me with netbean 8.2.