I was using Intellij on my Dell Latitude E 7470. It's the smaller laptop without a special numeric keyboard. When you want to use asci code, you must press fn + alt + the number combination representing the asci on keys jkluiop... It was working just fine but I reinstalled Win some time ago and now when I press for example fn +alt + 123 to write curly braces, it automatically jumps to the bottom of the class declaration and creates the curly braces there and not at the spot where I'm writing them... Thanks for any kind of help.
This is how the keyboard looks
keyboard layout
Update - solution
I figured it out. The fn + fn key 1 was end, fn 2 was down and fn 3 was bound as page down. When combined with alt it was using predefined IntelliJ shortcuts I had to remove. This functionality is probably caused by the newest Bios version of Dell Latitude laptops in version 20 + ... I personally have latitude E7470 but I have read on different forums other users complaining about incorrect workings of fn key and inability to change them because the system or Bios settings for FN keys were all removed.
Related
How would one achieve to keep IntelliJ from removing spaces in Python (or any language for that matter) in areas where spaces serve a specific purpose of readability, such as repetitive assignments of many values.
is how I like it and I think many vim users agree that this is the way to go.
However, this is what IntelliJ makes out of it
The issue is specifically interesting with language such as python where spaces can (but do not have to) impact the programs flow.
I am also aware that it is rather difficult to define when spaces should be compacted (i.e. when only one of the 4 lines above are present) and when they should be kept.
I guess some heuristic approaches would work, this however wouldn't really be a 100% on-spot lintable situation.
I like your idea, but don't see how to achieve that within the Editor Settings.
An ugly alternative that does work, but "pollutes" your source, is to Enable formatter markers in comments on this screen: File -> Settings -> Editor -> Code Style:
After choosing that option you can selectively create blocks of code that will be ignored by IDEA when it formats the code:
// #formatter:off
String s1 = "Arkansas" + ".";
String s2 = "Maine" + ".";
String s3 = "Massachusetts" + ".";
String s4 = "Ohio" + ".";
// #formatter:on
You could also raise a bug report with JetBrains: "Provide an option to allow multiple embedded spaces in source code". That should be fairly straightforward for them to implement: just don't replace multiple embedded spaces by a single space when reformatting.
If | is my cursor position
List<String> words = Arrays.asList(|"all cats are grey".split(" "));
Then I would like a shortcut to jump to the closing bracket
List<String> words = Arrays.asList("all cats are grey".split(" ")|);
Note, as per this question the shortcuts Ctrl+{ and Ctrl+} work for jumping between braces { } but not for brackets ( )
Note 2: with standard IntelliJ keymap
It looks like there isn't a specific action to move cursor to the matching bracket.
This does it in 2 keystrokes and is the best I've found: Ctrl+W which selects the block up to the matching bracket, then ▶
That's almost as quick, and better than switching to the mouse.
I don't think there exsists a shortcut for round parenthesis.
I am working with ItelliJ for years, never found one.
Ctrl +Key depends on your Keymap.
You can change it in Settings -> Keymap -> [Keymaps:].
I haven't found round parenthesis, but i could have overlooked it.
Edit:
A possible solution would be, to install the Plugin IdeaVim and use Shift + %
http://vim.rtorr.com/
I Eclipse there is a shortcut to apply format which is:
Cmd + Shift + F
Is there a similar shortcut in Xcode which fixes the formats like tabs, etc.?
You probably want Editor -> Structure -> Re-Indent (Ctrl+i). I does not change the position of braces and things like that. For that, you'd need to use an external code formatting tool like Uncrustify.
I'm using Komodo edit 8.5 on windows 8 and I'm finding it impossible to use. let me illustrate why using the 'pipe' symbol (|) for the cursor.
If I am typing on version an earlier version it would type like any app would ie: ms word or txt pad will let me type between characters as:
if(|) ... and I begin to type an x if(x|)
where as on version 8:
if(x|
the cursor destroys characters in front of it.
I normally write encapsulating brackets then press left to enter into them to begin to give my condistion, this is not helpfull. how do I get this to behave?
also the cursor is an underscore in version 8 wtf's with that!?
It isn't a problem with Komodo Edit. You have switched your cursor to "insert" mode. Look on your keyboard for a key labeled "Ins" or "Insert" (for me it is on the number pad, right next to the right arrow). Hitting this key toggles the mode of the cursor.
I've some records which are really messed up.
My team lead told me to find out the position of characters with ascii value 14 and 15.
I've a query
SELECT CHARINDEX(CHAR(14),X_CUSTOMER_COMMENTS)
FROM vp_service_requests;
SELECT CHARINDEX(CHAR(15),X_CUSTOMER_COMMENTS)
FROM vp_service_requests;
which returns 0 because i wasn't able to find char with 14 and 15 ascii value after google
search i found 14 and 15 ascii value are for shift in and shift out
how this represents on keyboard so i can try for it with CHAR(14) function.
As a holdover from the old DOS days, Windows still allows you to enter certain old ASCII keys from the keyboard by pressing and holding the ALT key, followed by the three-digit code you wish to enter (from the 10-key pad, not the numeric row atop the keyboard), eg for 14, type ALT-014.
However, some of the lower-level codes are inherited from old terminal functions, eg ASCII 7 is a bell, 8 is a backspace, eg, and rather that typing a character, they cause the cursor to behave a certain way or induce an application to respond in a defined manner. You can embed a CHAR(XX) value for testing simply by concatenating the value into a string and INSERTing it into your test table.
It should be Ctrl-N and Ctrl-O although I doubt this will help.
Try loading the records into a good editor and look at them in HEX. Weird characters should stick out like a sore thumb