similar to: [Bug 3765] New: Escape sequences are accepted more than documented

This implements a few useful escape sequences: ><rescue> ^]? virt-rescue escape sequences: ^]? - print this message ^]h - print this message ^]i - print inspection data ^]q - quit virt-rescue ^]u - unmount filesystems ^]x - quit virt-rescue to send the escape key to the rescue shell, type it twice ^]i root device: /dev/sda3 product name: Fedora 25 (Twenty Five) type: linux

https://bugzilla.mindrot.org/show_bug.cgi?id=2478 Bug ID: 2478 Summary: Escape sequences (starting with ~) don't work when remote shell is BusyBox ash Product: Portable OpenSSH Version: 7.1p1 Hardware: ix86 OS: Linux Status: NEW Severity: minor Priority: P5

http://bugzilla.mindrot.org/show_bug.cgi?id=1331 Summary: ControlClient escape sequences non-functional Product: Portable OpenSSH Version: 4.6p1 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: bitbucket at mindrot.org ReportedBy: dwmw2

While preparing a function that contained non-ASCII characters for inclusion into a package, I replaced all non-ASCII characters with UTF-8 escape sequences (using \uxxxx) in order to make the package portable (and adhere to "R CMD check"). What I didn't expect: when one uses UTF-8 escape sequences in function arguments, one needs to use UTF-8 escape sequences when calling the

I guess that R does not know about ANSI sequences, and it calculates the width of the prompt including the characters in the sequences. You cannot do much about this, except maybe use a prompt that has two lines. You can put the colored text and whatever you like in the first line, and the second line can be non-ANSI. Note that this works in the terminal, but does not work in RStudio. RStudio

Dear list, I would like to know if there is any way to include xterm escape sequences in R's prompt using options( prompt= XXX, continue= XXX ), where XXX can contain, for example, "\033[1;31mRed" for chancing text color to red (see http://www.frexx.de/xterm-256-notes/). If you do this, the color escape sequences work (with an appropriate terminal emulator, e.g., xterm under Linux),

Hello, I'm using openssh-4.3p2 compiled for sparc-sun-solaris2.8. I'm trying to use the IdentityFile option with the escape sequences for the remote host name (%h) and remote user name (%r) as documented in ssh-config <http://www.openbsd.org/cgi-bin/man.cgi?query=ssh_config&sektion=5&arch=&apropos=0&manpath=OpenBSD+Current>. It seems the escape sequences do not

OpenSSH 5.1p1 was just installed on Linux machines here. It appears that escape sequences are not being passed to the underlying terminal for in- terpretation and control. I am now seeing \033[H and \033[2J. This will not bode well for users expecting classic escape sequences to be painting and controlling their terminal screens. Is there a magical incantation to restore proper behavior? Or

When R is run interactively in a terminal which supports colors, it is possible to use ANSI escape sequences in order to put colors in the prompt, such as options(prompt = "\033[0;31mThis is red\033[0m> ") Unfortunately, something goes wrong because for long command lines, the line continuation override the prompt instead of being written in the next line. The problem gets worse

https://bugzilla.mindrot.org/show_bug.cgi?id=2520 Bug ID: 2520 Summary: ssh-keygen: sanitize ANSI escape sequences in key comment Product: Portable OpenSSH Version: 7.1p1 Hardware: amd64 OS: Linux Status: NEW Severity: minor Priority: P5 Component: ssh-keygen

unfortunately, we keep getting this warns into the system log by puppet masters: " [...] Unrecognised escape sequence ''\<CHAR>'' in file <PATH> [...] " but then everything works fine; also, without using escapes, catalogs dont work on agents. What can we do to avoid these kind of errors in master syslogs? Please ,let us know ASAP and tell us if this

Hi, Today I fiddled around a bit with my OpenSSH public key files, and I noticed that ssh-keygen prints most non-printable characters in the comment as-is when showing the fingerprint of a key. This can lead to confusing output on the terminal when the comment contains ANSI escape characters which are interpreted by the terminal. The attached public key file serves as an example, which, when

R 4.2.1 OS X Colleagues I am using XOJO (formerly known as RealBasic) to create a GUI -- R code generates the text that appears in the GUI. Recently, VT-100 terminal control escape sequences appeared in the text, e.g.,: [?25h TEXT [?25h[?25h TEXT It is not clear to me if the problem is generated by R or by XOJO. And I did not track whether this began following installation of a

Hello, I would like to create a matrix with one of the columns named $\delta$. I have also created columns $\beta_1$ , $\beta_2$, etc. However, it seems like \d is an escape sequence which gets automatically removed. (Using these names such that they work right in xtable -> latex) colnames(simpleReg.mat) <- c("$\beta_1$","$SE(\beta_1)$", "$\beta_2$",

I've pushed this patch in response to a user request to make it easier to write newlines and other characters in guestfish: http://git.annexia.org/?p=libguestfs.git;a=commitdiff;h=617e7f6bafa7de2303c08e1715004aae3141c389 This lets you write: ><fs> write /file "this is a line\n" and have it do what you'd expect. (With current guestfish, this writes backslash

Hi Str1<-"hai " Str2<-"hru" I want to write these 2 strings in a file separated by newline. How can I get this. Thanks K.Ravichandra [[alternative HTML version deleted]]

I hate asking questions like this, but I swear I''ve been looking for the answer for the better part of the morning. I want to execute some javascript onChange for a select box, so I have: :onchange=>"for (var x=1; x <= this.options.length; x++) {....}" The problem is that the <= is being translated into &lt;= and I don''t want that :-/. Nothing

> assuming that a shell is being used is invalid I never made this assumption. I looked directly at the source code and I stated that "I feel that this function should also handle backslash escapes." I think the assumption that splitting the command works the same way as (all?) major shells, is not inappropriate given the circumstances, and it seems like you agree. > but

Hello! The question is simple: What is the escape sequence for a new line when using Hershey fonts? I obviously tried '\n' but it didn't work (see the sample below). I looked at 'demo(Hershey)' but all it only shows escape sequences for printable characters. The sample I've been using to try to find the escape sequence is below. You can comment or un-comment the

Full_Name: Volkmar Klatt Version: 2.6.2 OS: linux Submission from: (NULL) (84.147.0.178) Hello, the documentation article ?Quotes from package:base could be improved by discussing the meaning of "\0" escape sequence. In R (currently used: R-2.6.2), a "\0" in a string will silently terminate that string, just as it would in C code. There is no warning about an unknown escape