Perhaps the most useful command: EOF. No need to use "exit" / "logout" ever again, works in anything using deadline, any shell, and things like cat when using it to create files cat - > file.

• Category
  • fzf binary
  • Key bindings
• Shell
  • bash
  • zsh
  • fish

Eg, I would like to have the second item highlighted on startup.

It would be nice to call fzf as in:

echo -e 'abc\ndef' | fzf --bind 'start:down'

For reference, this is the tool I'm develop

The BSDs let you pass path names longer than sizeof(s.sun_path), they read past the end when socklen > sizeof(struct sockaddr_un) up to a limit¹. Let's support that.

¹ I'm 80% sure it's 255 on all BSDs but it certainly is on Darwin and FreeBSD.

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]

It would be nice if lynis would gather (and report in the portal/reports) information about user-accounts:

• Expired or soon to expire passwords (passwd -e)
• Locked accounts (passwd -S )
• Expired accounts (chage -E / chage -l )

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

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

Someone asked on IRC how if Elvish supported vi mode editing. I couldn't find any mention in the documentation and greping the source didn't return any promising results. It turns out that doing

edit:insert:binding[Ctrl-'['] = $edit:command:start~

will enable a very limited vi editing mode. See also #730 for why the features are currently limited. The currently support vi commands

也算一个总结, 提醒后来人少走弯路.

• 写入 socket 时的内存管理
  uv_write 函数写网口时, 写入数据的内存必须由你管理, 在 回调函数 uv_write_cb 内部释放. 如果你不信邪, 在 uv_write 执行完以后马上释放, 恭喜你掉坑里了. 我就在这坑里呆了一星期. 因为这么干的结果是, 在 Windows 下一切正常, 在 Linux 下会随机写失败. 估计 Windows 对这块写内存复制了一份以增加安全性, 类 unix 平台就不管你死活了. 这点差异性就足以逼你发疯痛不欲生了.

• 接收数

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,

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

FTP OS: Unix

FTP Server: ProFTPD

Computer OS: Windows 10

Many functions result in Socket-related issues.

Logs :

<paste logs here but DO 

It'd be good to state publicly the oldest kernel and glibc (or even other libc versions) we support.
This would allow us to remove some legacy code or force support for legacy code.

This shouldn't require test to be functional (e.g. for some cases like module drivers it could be hard),
but LTP to be compiled and when difficult/impossible to achieve this functionality, it could resulted in TCO

I would find it useful to be able to customize the help message more than just adding a header to it.

recvfrom(2) takes an integer flags parameter, but it is missing from nix's version:

pub fn recvfrom( sockfd: RawFd, buf: &mut [u8] ) -> Result<(usize, Option<SockAddr>)>

The implementation of recvfrom unconditionally passes 0 to libc::recvfrom's flags parameter. This means I can't do something like MSG_PEEK w

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