Some markdown bold syntax is incorrectly displayed.

• 예를 들면 **alt-.**같은 경우
• ctrl-v **[Tab]**키를 누르거나

It should be modified as follows.

• 예를 들면 alt-. 같은 경우
• ctrl-v [Tab] 키를 누르거나

• Category
  • fzf binary
  • fzf-tmux script
  • Key bindings
  • Completion
  • Vim
  • Neovim
  • Etc.
• OS
  • Linux
  • Mac OS X
  • Windows
  • Windows Subsystem for Linux
  • Etc.
• Shell
  • bash
  • zsh
  • fish

It would be useful to get a better understanding of the context of th

Hello,

could you please provide a VS 2019 compatible vcbuild.bat?

Regards
Martin

Node version (or tell us if you're using electron or some other framework):

12.1.0

ShellJS version (the most recent version/Github branch you see the bug on):

0.8.3

Operating system:

Windows

Description of the bug:

sed is applied only once by line:
original archive:
import [COMPONENTNAME]Base from './[COMPONENTNAME]Base';
`const [COMPONENTNAME] = styled( [COMPONENTNAME]

I'm using OpenNTPD instead of the default ntp on my FreeBSD server - when lynis analyses the ntp settings it tries to query information with ntpq which is (to my knowledge) is not possible with OpenNTPD.

Lynis will slow down as ntpq takes a while fail.

OS: FreeBSD 10.4
Lynis: 2.6.1 (768446e4)

[ Lynis 2.6.1 ]

####################################################################

The documentation for glfwSetKeyCallback at https://www.glfw.org/docs/latest/input_guide.html#input_key offers little guidance on what will cause a GLFW_REPEAT action, which can cause confusion such as in the forum post Key Callback Not Registering Every Key Press
.

I think we should consider modifyi

In every pull request I make, I end up getting told by @awesomekling to swap a piece of code with an existing one from the AK library. Wouldn't it be cool to have a Doxygen like documentation in which someone can search for something to see if it already exists in AK? I know I can grep the project to see if something exists but a documentation is always useful I think, especially if it documents a

I attach an example RPM SPEC file (dumb-init.spec) that can be used to build an RPM of this application. The user should change the version number for the 'this_ver' macro to match the downloaded version number before building the RPM. This one has coded in it version 1.1.2
dumb-init.spec.txt

We have an elvdoc tool that can extract comments like the following from Go sources:

//elvdoc:fn name-of-function
// Doc body

//elvdoc:var name-of-variable
// Doc body

And it is being used to generate parts of https://elv.sh/ref/edit.html. However, we do not have such a mechanism for Elvish sources yet, and as a result https://elv.sh/ref/epm.html is still written "by hand"

The opening code example is given as:

$ echo 'foo\nbar\nfoo' | sort | uniq -c | sort -nr
2 foo
1 bar
$ echo 'foo\nbar\nfoo' | sort | uniq -c | sort -nr |

but should be:

$ echo -e 'foo\nbar\nfoo' | sort | uniq -c | sort -nr
2 foo
1 bar
$ echo -e 'foo\nbar\nfoo' | sort | uniq -c | sort -nr |

-e switch is required for interpolating escaped \n. Without it, the example

we have a help option where users can specify help on inputs which is cool. I wonder if we should add an additional help text on all selects/multi-selects that gives users information about the possible keys they can use.

e.g. to describe

• cursor keys or vim mode j,k for moving selection
• space to select/unselect on multi-selections
• letters and numbers for filtering large selects

Upon loading the latest version (2.6.1) of the player a warning appears in the console that states:

[Deprecation] document.registerElement is deprecated and will be removed in M80, around February 2020. 
Please use window.customElements.define instead. See https://www.chromestatus.com/features/4642138092470272 and https://developers.google.com/web/updates/2019/07/web-components-time

First of all: thanks for the amazing work and super easy install scripts. Now to my point:

The readme is well written, unfortunately not absolutely up to date. for example, it is missing completely the information about the very handy script 'change.sh' and how to use it.

Furthermore, it would make sense to me to include installation of the python-pip package in the install_ubuntu.sh script,

FTP OS: Unix

FTP Server: ProFTPD

Computer OS: Windows 10

Many functions result in Socket-related issues.

Logs :

<paste logs here but DO 

Current style guide [1] is outdated. It uses legacy API examples, but contains some valid info (avoid including kernel headers due bugs in UAPI on older distros, mentioned in [2]). We also have style guide for new API [3].

I propose delete [1] and move valid content from it to [3] (probably just UAPI on older distros).
We also need to document how to deal with backward compatibility that cover

currently, any password supplied using --ssl-passwd when creating a makeself archive is exposed in the header --info block with the build commands. problem can be sidestepped by using --ssl-pass-src and a temporary file instead. should probably either rework the build info to drop/redact that argument or stop supporting --ssl-passwd

I tried Oh, and it seems interesting. Certainly the programmability aspect is cool, and I like the idea of the type system. However, there's no documentation about how to customize anything (your prompt, for instance). I could read the source code, but I decided to try the shell on a whim at work, and I can't reasonably spend the time. I think it would be pretty easy to put together some guidance

https://github.com/nix-rust/nix/blob/70cce1a384ec21c6ba0ef38d64d2f67333e4b7d7/src/unistd.rs#L381-L397

This means that using it in multithreaded applications results in races even on platforms where a proper dup3 is supported.

I think it would be best if it used dup3 if it is available and only falls back to dup2 if dup3 is not available.