Issue Prelude

Please complete these steps and check these boxes (by putting an x inside
the brackets) before filing your issue:

• I have read and understood YCM's [CONTRIBUTING][cont] document.
• I have read and understood YCM's [CODE_OF_CONDUCT][code] document.
• I have read and understood YCM's [README][readme], **especially the
  [Frequently Asked Questions][faq]

Some users have been asking me for simple usage instructions for ctags and I couldn't find them. It would be nice to have a "getting started" guide that shows how to run ctags on a tree of sources, to turn on/off languages, kinds and fields and maybe how to hook everything up with an editor. It should be pretty short and condensed with eventual pointers to more information for deeper understandin

Environment

• Credo version: 0.8.5
• Erlang/Elixir version: 1.5.0
• Operating system: Windows 10 (build 15063)

Special characters (arrows, edge) display as garble

My presumption is that there should be a way to do this automatically as part of the release process.

I'm not 100% how best to achieve this, so before running with it I'd like to open it out for discussion.

To start things off, this SO question has a few answers/suggestions.

One suggestio

Returns:

Invalid config file: Unexpected token } in JSON at position 210

for

{
  "threshold": 30,
  "identifiers": true,
  "literals": true,
  "color": true,
  "minInstances": 2,
  "ignore": "test|spec|mock",
  "reporter": "json",
  "truncate": 100,
}

should be:

{
  "threshold": 30,
  "identifiers": true,
  "literals": true,
  "color": true,
  "minI

Hi Coala maintainers,

Can you help clarify AGPL coverage in Coala's case? Specifically, are the modifications made by Coala, which would get put into the input source code, covered by AGPL?

Your clarification will help evaluate the technology selection. I'd be helpful If you could clarify your interpretation in the Q&A page.

Thanks,

Brian

Affects PMD Version:
All.

Rule:
ImmutableField

Description:

"Identifies private fields whose values never change once object initialization ends either in the declaration of the field or by a constructor. This helps in converting existing classes to becoming immutable ones."

Immutability, by defini

1. Summary

It would be nice, if HTMLHint documentation will contain arguments, why HTMLHint users must use specific rules.

2. Argumentation

“Must” in The script tag can not be used in head., Id and class value must meet some rules: underline, dash, hump. is not argument. The documentation does not show the reasons. Users should know “Why must”?

3. Example of expected behavior

Inspired by comment spotbugs/spotbugs#797 (comment) on #797
implement a new detector which finds faulty regex patterns.

The detector should find faulty regexes in standard library methods
Pattern.compile(String regex)
Pattern.compile(String regex, int flags)
String.replaceFirst(String regex, String replacement)
String.replaceAll(String regex, String re

In particular, the if add_extra_clang_flags: branch in PrepareFlagsForClang function in file ycmd/ycmd/completers/cpp/flags.py. Otherwise, the result when complete headers is super noisy when somebody uses g++ rather than clang on macOS

Description

The class ZipEntry describe one file inside a Zip archive. getName() return the file name from this file. It could contain a malicious string such as "../../../". If the value is used to build a file path, it could lead to a

I have a syntax error in a file that is involves an error message with a curly bracket:

The msg here: https://github.com/rubik/radon/blob/8db8eac6b93aca1eea818060b62350a7cf6a7d36/radon/cli/__init__.py#L353

I imagine contains the curly bracket which causes an issue at the format call here:

https://github.com/rubik/radon/blob/8db8eac6b93aca1eea818060b62350a7cf6a7d36/radon/cli/__init__.py#L3

inline templates:

• with anonymous classes
• with lambda

I am using the vscode extension and there is no autocompletion for $path = $_SERVER['DOCUMENT_ROOT']."/directory".

Can I somehow specify the document root?

Environment data

VS Code version: 1.34.0
Extension version (available under the Extensions sidebar): 2019.4.12954
OS and version: Ubuntu 19.04
Python version (& distribution if applicable, e.g. Anaconda): 3.6
Type of virtual environment used: virtualenv

Problem

The type hints in the stub file for the current module aren't used for autocompletion.

I have a foo.pyi file as

Current view of ellipse:

If move title parameter of ellipse into ellipse tag, then text field change to tooltip (show title on mouse hover):

Hi,

I realize this may be more of a Docker question than an issue specific to this repo, but I would love an example in the documentation for how to pass a local file to the parse command.

On the Getting Started you list the following command to run an example file included in the container:

docker exec -it bblfshd bblfs

The link for the coala-bears usage further navigates to this which has no information about how to use coala. One can do either of the following:

• Update the link so that it navigates to the coala documentation.

• Add usage information in the README.rst file located here.

Backreferences referencing a (named) capture group declared after the reference always expand to an empty string. They are in fact forwardreferences.

/^\1(.)$/.test('aa'); // doesn't match
/^\k<name>(?<name>.)$/.test('a'); // matches only a single character

Related: #615

I ran into problems with the extremely long APP_CLASSPATH variable in joern-parse.bat when running joern-cli on Windows. The command was too long and the script would die when trying to set the classpath. I got around it by simply passing a wildcard (%APP_LIB_DIR%/*) to the -cp argument at the end of the script.

I'd file a PR but I can't find the script in this repo.

It would be great if anyone using code-forensics in a Windows OS could take a little time to write a little page to explain the main gotchas required to get the tool running in Windows. If you can contribute let me know and I will be happy to include your documentation in the current wiki.

This does not mean I intend to fully support Windows in the future, my intent is just to provide some hint