search for: key_enter

...See above> Ctrl-M _is_ Enter, in some sense. > -- > Regards, > Feri. Please forgive my ignorance (I am not a developer). Where in the Syslinux code we can find that [Ctrl-M] is "CR"? For example, in "./com32/elflink/ldlinux/cli.c", line 219, we can see: case KEY_ENTER: case KEY_CTRL('J'): ret = cmdline; done = true; break; So I can see that [Ctrl-J] has the same effect as [Enter] in the Syslinux CLI. But I can't find [Ctrl-M], or rather, I don't know how to find it. As with other keystroke combinations that are not listed or...

...am not a developer). Where in the > Syslinux code we can find that [Ctrl-M] is "CR"? Read http://en.wikipedia.org/wiki/ASCII: the CR ASCII control character is typed in as Ctrl-M. > For example, in "./com32/elflink/ldlinux/cli.c", line 219, we can > see: > case KEY_ENTER: > case KEY_CTRL('J'): > ret = cmdline; > done = true; > break; > > So I can see that [Ctrl-J] has the same effect as [Enter] in the > Syslinux CLI. > > But I can't find [Ctrl-M], or rather, I don't know how to find it. > > As with o...

Ady <ady-sf at hotmail.com> writes: >> On Sat, Sep 6, 2014 at 8:18 AM, Ady <ady-sf at hotmail.com> wrote: >> >>> What actions are _supposed_ to be triggered by each of: >>> >>> [Ctrl-J] >>> [Ctrl-M] >>> >>> in the Syslinux command line in version 6.03-pre20? >> >> They should do nothing special but

...m->curentry; int prev_entry = -1; volatile int top = cm->curtop; @@ -854,7 +855,12 @@ static const char *run_menu(void) } this_timeout = min(min(key_timeout, timeout_left), (clock_t) CLK_TCK); - key = mygetkey(this_timeout); + + if (hotkey && me->commit) + key = KEY_ENTER; + else + key = mygetkey(this_timeout); + hotkey = 0; if (key != KEY_NONE) { timeout_left = key_timeout; @@ -1071,7 +1077,7 @@ static const char *run_menu(void) if (cm->menu_hotkeys[key]) { key_timeout = 0; entry = cm->menu_hotkeys[key]->entry; - /* Shou...

...the command: g++ -L/usr/lib64 -lGL -lGLU -lglut -lX11 -lXi -lxcb-glx -lxcb-xlib -ldl glut_gamma_bug.cpp Start it with: ./a.out It will open a small window with an image composed of vertical strips. Press the enter key (it apply a gamma correction of 3 to the image): a) it will print a message: KEY_ENTER b) it will print another message: current error GL: no error c) the same image will be brightness d) at the second message: current error GL: no error, it will crash Crash in: ==17340== Invalid read of size 4 ==17340== at 0xE5D4ABE: set_sampler_views.isra.2 (u_atomic.h:62) ==17340== by 0xE...

Guys. How and which tools to use to load test an asterisk install? Say for example, you need to see how many calls can be routed thru before losing quality and making the cpu jump to the roof?

> On Sat, Sep 6, 2014 at 8:18 AM, Ady <ady-sf at hotmail.com> wrote: > > Hello Syslinux Team, > > > > What actions are _supposed_ to be triggered by each of: > > > > [Ctrl-J] > > [Ctrl-M] > > > > in the Syslinux command line in version 6.03-pre20? > > They should do nothing special but either might be interpreted like an

From: Matt Fleming <matt.fleming at linux.intel.com> These patches are based on the elflink branch. This set of patches is my attempt at moving the command-line interface functionality out of the core and into an ELF module to reduce the size of the core. The most interesting patch is [PATCH 4/4] which moves the cli code out of core/elflink and into com32/elflink/modules. [PATCH 4/4] is

From: Matt Fleming <matt.fleming at linux.intel.com> This is a series of patches that, * shrink the core by moving things into an ldlinux ELF module * begin wiring up some of the C versions of various functions The core now only contains essential code and loads the ldlinux module to do everything else, like providing a command line interface and loading kernels. The config file parsing

From: Matt Fleming <matt.fleming at linux.intel.com> This series fixes some bugs and switches the elflink branch to be entirely ELF modules. It applies on top of, http://syslinux.zytor.com/archives/2011-April/016369.html The deletions in the diff stat below are mainly from deleting com32/elflink/modules (finally!). Now there should be no duplicate code because we don't need COM32 and

The following series of 10 patches is a merge of the xenfb and xenconsoled functionality into the qemu-dm code. The general approach taken is to have qemu-dm provide two machine types - one for xen paravirt, the other for fullyvirt. For compatability the later is the default. The goals overall are to kill LibVNCServer, remove alot of code duplication and/or parallel impls of the same concepts, and