Wikipedia:Reference desk/Archives/Computing/2021 March 26
| Computing desk | ||
|---|---|---|
| < March 25 | << Feb | March | Apr >> | March 27 > |
| Welcome to the Wikipedia Computing Reference Desk Archives |
|---|
| The page you are currently viewing is a transcluded archive page. While you can leave answers for any questions shown below, please ask new questions on one of the current reference desk pages. |
March 26
editVisual Studio 2015 only shows JavaScript warnings if build fails
editI am developing a .NET web application with the back-end written in C# and the front-end written in HTML and JavaScript.
I have found out that if building the C# back-end fails, Visual Studio 2015 shows me about 300 warnings about the JavaScript code, such as missing semicolons or superfluous parentheses. But if the C# back-end builds OK, I don't see any warnings about the JavaScript code, even though it's the exact same code.
What is causing this? Why am I only seeing warnings if the build fails? This way if I want to lint the JavaScript code to get it formally correct as well as working, I have to purposefully introduce build errors into the back-end. JIP | Talk 00:03, 26 March 2021 (UTC)
Compose sequences
editUnder Linux the compose sequence "MULTI_KEY T H" yields Þ (thorn) and "MULTI_KEY D H" yields Ð (eth) and their lowercase versions þ and ð are also available. Is there any compose sequence for yogh (Ȝ ȝ)? It's in Unicode at U+021C Ȝ LATIN CAPITAL LETTER YOGH (HTML & # 540;) and U+021D ȝ LATIN SMALL LETTER YOGH (HTML & # 541;) respectively, but I cannot find a convenient way to type it on a normal UK keyboard. Martin of Sheffield (talk) 16:20, 26 March 2021 (UTC)
- I smell an XY problem. Why do you need this? If it is a one-time job you might be better off copy-pasting; if it is an infrequent but regular occurence, Unicode_input#Decimal_input might be what you need; and if you have to transcribe large chunks of text you probably need to install a keyboard layout. TigraanClick here to contact me 17:14, 26 March 2021 (UTC)
- Well if you want the background, I was involved in a discussion about medieval manuscripts and was repeatedly referring to þ, ð and ȝ. I was then copy typing from the (online) manuscript and again using the three. A compose sequence allows you to continue typing whereas a cut and paste requires you to move your hand off the keyboard and onto the mouse. Whether you regard my Y as reasonable is actually immaterial, since þ and ð have sequences it seems strange that ȝ doesn't. That's all, just convenience. Martin of Sheffield (talk) 17:31, 26 March 2021 (UTC)
- It doesn't sound that strange to me. It seems that ȝ isn't used in any modern language, but ð and þ are in regular use in Icelandic. BTW, hexadecimal input works on most Linux systems: ctrl+shift+u, 2, 1, d, space. Although it's less convenient than the compose key. PiusImpavidus (talk) 10:06, 27 March 2021 (UTC)
- Well if you want the background, I was involved in a discussion about medieval manuscripts and was repeatedly referring to þ, ð and ȝ. I was then copy typing from the (online) manuscript and again using the three. A compose sequence allows you to continue typing whereas a cut and paste requires you to move your hand off the keyboard and onto the mouse. Whether you regard my Y as reasonable is actually immaterial, since þ and ð have sequences it seems strange that ȝ doesn't. That's all, just convenience. Martin of Sheffield (talk) 17:31, 26 March 2021 (UTC)
- The file location(s) are detailed in http://manpages.ubuntu.com/manpages/trusty/man5/XCompose.5.html (man 5 XCompose). According to https://www.x.org/releases/X11R7.6/doc/libX11/Compose/en_US.UTF-8.html Yogh isn't in it by default (atleast for en-US). If you have administration rights on your box, then it shouldn't be difficult to update the compose table to add Yogh. LongHairedFop (talk) 12:34, 27 March 2021 (UTC)