similar to: syslinux ansi <-> vesa color mapping

Hello all, First off, thanks for the great work. I have recently added "more submenus" to a functioning advanced menu that only had one "submenu off of the main menu before" The addition of the new submenus has caused the main menu to not function correctly and I have been pouring over the code for several weeks and I just cannot see the error that I have introduced. This

fansi provides counterparts to the base string manipulation functions substr, strwrap, strtrim, strsplit, and n(z)char that account for ANSI CSI SGR control sequences.? ANSI CSI SGR control sequences [1] can be used to format text in terminals that support them. For example the control sequence "\033[31m" causes text that follows to render in red, and the control sequence

From: Randy Dunlap <randy.dunlap at oracle.com> Fix sparse warning for non-ANSI function declaration: arch/x86/xen/irq.c:129:30: warning: non-ANSI function declaration of function 'xen_init_irq_ops' Signed-off-by: Randy Dunlap <randy.dunlap at oracle.com> Cc: Jeremy Fitzhardinge <jeremy.fitzhardinge at citrix.com> --- arch/x86/xen/irq.c | 2 +- 1 file changed, 1

From: Randy Dunlap <randy.dunlap at oracle.com> Fix sparse warning for non-ANSI function declaration: arch/x86/xen/irq.c:129:30: warning: non-ANSI function declaration of function 'xen_init_irq_ops' Signed-off-by: Randy Dunlap <randy.dunlap at oracle.com> Cc: Jeremy Fitzhardinge <jeremy.fitzhardinge at citrix.com> --- arch/x86/xen/irq.c | 2 +- 1 file changed, 1

From: Randy Dunlap <randy.dunlap at oracle.com> Fix sparse warning for non-ANSI function declaration: arch/x86/xen/irq.c:129:30: warning: non-ANSI function declaration of function 'xen_init_irq_ops' Signed-off-by: Randy Dunlap <randy.dunlap at oracle.com> Cc: Jeremy Fitzhardinge <jeremy.fitzhardinge at citrix.com> --- arch/x86/xen/irq.c | 2 +- 1 file changed, 1

Hi, I'd like to use the compiler flags -ansi -pedantic -Wno-long-long in my project but some llvm headers cause errors with them. I tried to compile llvm with these flags but it proved to be quite difficult. The headers, however, seemed easier to fix. Almost all of the errors were commas at the ends of enum lists or extraneous semicolons after namespaces. I went ahead and hunted down

I ran across one file in the openbsd-compat directory, strmode.c, that was not using an ANSI C function declaration. One compiler (HPUX's cc -Ae) wouldn't let it pass. Here's a patch. - Dave Dykstra *** openbsd-compat/strmode.c.O Wed Jun 6 17:32:44 2001 --- openbsd-compat/strmode.c Wed Jun 6 17:32:59 2001 *************** *** 43,51 **** #include <string.h> void !

Hi folks, does anybody know how to get a DOS executable to run that relies heavily on ansi.sys to simulate a text-based user interface? My wine version is "Wine release 20010305". Any help appreciated. Regards Lothar -- Lothar Birk -- Institute of Naval Architecture and Ocean Engineering E-mail L.Birk@ism.TU-Berlin.DE S-Mail TU Berlin Phone +49 (0)30 314 26010 (direct line) or

Hey all, I could have sworn I saw it done once, and it seems to make perfect sense that someone might want to colour code the NoOp() lines so that the console logging messages stand out more. If anyone has done this and wouldn't mind sharing the secret, I'd be much appreciative! Thanks! Leif Madsen.

Have you tried starting asterisk with the "-n" param? -n Disable console colorization On Thu, Jul 23, 2020 at 5:11 PM Andrew Yager <andrew at rwts.com.au> wrote: > Hi, > > Is there a way to drop the ANSI colour strings from log files? In > particular, I've got JSON logging throwing logs over to ES, but they have > the ANSI colour escape

You can post process the logs with something like sed. See: https://superuser.com/questions/380772/removing-ansi-color-codes-from-text-stream On 7/23/20 5:10 PM, Andrew Yager wrote: > Hi, > > Is there a way to drop the ANSI colour strings from log files? In > particular, I've got JSON logging throwing logs over to ES, but they > have the ANSI colour escape sequences. >

From: Colin Ian King <colin.king at canonical.com> Give function nouveau_pmops_runtime a void argument to make it an ANSI function declaration. Fixes sparse warning: warning: non-ANSI function declaration of function 'nouveau_pmops_runtime' Signed-off-by: Colin Ian King <colin.king at canonical.com> --- drivers/gpu/drm/nouveau/nouveau_drm.c | 2 +- 1 file changed, 1

Anyone have a script or utility to convert an RTF file to ANSI? The main idea here is to preserve the color codes that are specified in the RTF file, so they can be displayed easily in a terminal window.

Hi All: It appears that the terminfo ansi-m file is no longer distributed with the CentOS 6.2 (along with many others). Can anyone advise how I can obtain this file? As a work around I have copied the file from a CentOS 4 box but that is probably not the "proper" way to do it. TIA Regards, Hugh -- Hugh E Cruickshank, Forward Software, www.forward-software.com

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

fansi provides counterparts to the base string manipulation functions substr, strwrap, strtrim, strsplit, and n(z)char that account for ANSI CSI SGR control sequences.? ANSI CSI SGR control sequences [1] can be used to format text in terminals that support them. For example the control sequence "\033[31m" causes text that follows to render in red, and the control sequence

Hi, So far with the latest changes the projects I am trying to port works fine, except for a mismatch on what is considered the ansi behaviour of islower() in ctype.h: ----- i = 220 islower (i) = 0, ISLOWER (i) = 0 toupper (i) = 220, TOUPPER (i) = 220 i = 221 islower (i) = 0, ISLOWER (i) = 0 toupper (i) = 221, TOUPPER (i) = 221 i = 222 islower (i) = 0, ISLOWER (i) = 0 toupper (i) = 222, TOUPPER

Aaron Plattner (1): Don't disable FB access when it's already disabled. Adam Jackson (9): Remove all trace of mfb Bug #10004: Fix palette initialization in 8bpp modes. Fix boolean inversion in VBE screen clear. Remove some useless module loading cruft. Prefer a more modern depth/bpp selection. Add semi-reasonable mode validation. Clean up

Bug #2150: Don't call VBEGetSetDACPaletteFormat when in direct colour or YUV modes. (David Sterratt) CVS tag: xf86-video-vesa-1_2_1 http://xorg.freedesktop.org/releases/individual/driver/xf86-video-vesa-1.2.1.tar.gz: MD5: 1bf4a36af8422245bcdd99c2aa2f8f4f xf86-video-vesa-1.2.1.tar.gz SHA1: 92323676608ff9ec357c8d94f14133794943b542 xf86-video-vesa-1.2.1.tar.gz

_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel