I am trying to add custom fields to Phabricator, particularly Maniphest, and even the example given in the documentation does not work (there is an open quote in it, but even correcting that still does not help.
I have made sure that the config is a valid JSON, using Firefox's console and I have trimmed all tabs and spaces and yet it does not accept it. Any idea what am I doing wrong or if it is a bug? If so, is there a workaround?
I fixed the documentation. The example also had an incorrect trailing comma at the end. The best way to report bugs to us is to file them against the upstream, here:
https://secure.phabricator.com/maniphest/task/create/
Related
Various things are different in 1.0.136, e.g. running code with ctrl-enter has all sorts of strange behavior in an RMarkdown document, running code that has a syntax error somehow leads to all of the code being run in a block above (below?) the wrong code, etc. Sorry for not posting an MWE, but at the moment I just want to know if anyone is aware of these new "features" and if so how they can be turned off or better yet how I can just downgrade to the previous version of RStudio (which I can't currently find on the website).
Yes they changed some default settings that were present in the old interface.
Change the setting in markdown next to the knit button, from:
Chunk Output Inline -> Chunk Output in Console
Pictured here.
You can probably mess with the the Global Setting->Rmarkdowns under Tools to get it back the way it was before, but this was the fastest way for me.
(this is on a OSX latest 10.9.x)
Some of the shortcuts work with the tab, others not..
for example:
.class>ul>li*5>a
when tabbing gives
.class>ul>li*5>
while
div.class
gives correctly
<div class="class"></div>
Also html:5, input:radio expansion doesn't work (only on CTRL+E).
Should I look my key mappings? Could something from OSX be interfering? (I use OPTION+TAB to switch windows with the help of Karabiner...
Glad that helped.
Rather than looking at all plugins installed, you may want to first try entering sublime.log_commands(True) in the ST console. Then try inserting as normal. If it's another ST plugin performing an action, the command name will be listed. If you don't recognize the name of the command, you can use something like FindKeyConflicts to see what package it's associated with. The above is a plugin I wrote, but I'm sure there are other plugins that do the same thing. In most cases, the name of the command is enough to find the offending plugin.
Also adding your solution here to make it a bit more clear.
I found my answer there: https://github.com/sergeche/emmet-sublime/issues/363. Conflict with ST's autocomplete. Commented it out, and we're good. I guess now I'm missing some out of the box snippets but well.
If you would like to see the default snippets, without having to search/extract them manually, you can try using https://sublime.wbond.net/packages/PackageResourceViewer. Another plugin I wrote to help with viewing those packaged files/plugins.
How to remove this features from my JomSocial? I don't know what is that but looking ugly. Thanks for answers
That's an untranslated language string. Either you have an incomplete language file or the developers forgot to add the translation. Contact the developers to help get your issue resolved.
When I try to use Google Prettify to syntax highlight my code, I notice that it causes code to become one line ... why is that? When I remvoe prettify, it works
This is a well-known issue that someone's still trying to track down. Hang on, I've got the bug favourited somewhere...
Yeah, there we go, here's the link to the issue in the Google Code issue tracker, assuming you're using IE, or one of the other affected browser/versions.
I always used to be able to see NSString values in the debugger, without problem. Since updating to 3.2.5 all I see is the format string {(char *)Xcode_CFStringSummary($VAR, $ID)}:s
I can't see anything wrong with that. Can anybody please tell me what the correct formatter should be?
I'm having this same problem and haven't found a solution. But at least I did figure out you can still view the strings by right clicking on the string variable and selecting "Print Description to Console".
I also had this problem and at the same time I noticed a couple of errors about missing symbols for xcode debug libraries (see here). Fixing the errors as described in the link also made my strings start working again. I realise you are talking about a different version of the SDK, but maybe the problem is the same.