Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The vt100 terminal that Screen (and just about every other terminal emulator) emulates has two modes, normal mode and application mode. Normal mode is used for line-by-line applications and application mode for full-screen applications. Amongst the differences between the modes is that the arrow keys send <a href="http://www.gnu.org/software/screen/manual/screen.html#Input-Translation">different control sequences</a> (I don't know why): e.g. <code>ESC O A</code> in full screen mode and <code>ESC [ A</code> in normal mode. It seems that when you press <kbd>Ctrl</kbd>+<kbd>Z</kbd>, Emacs switches the terminal back to normal mode, but when you return it to the foreground, it doesn't switch to full screen mode again, or Screen does not react to Emacs's commands properly.</p> <p>One possible workaround is to <a href="http://www.gnu.org/software/screen/manual/screen.html#Bindkey">bind the same character sequences</a> in both modes in your <code>.screenrc</code>, e.g.</p> <pre><code>bindkey -k ku stuff ^[OA bindkey -k kd stuff ^[OB bindkey -k kr stuff ^[OC bindkey -k kl stuff ^[OD </code></pre> <p>Another possible workaround is to tell Emacs to interpret both key sequences regardless of what the terminal says. Although this is in principle a bad idea since some terminals might use these key sequences for different keys, I've never encountered such an incompatible terminal, and I suspect none have been made in the last 20 years or more.</p> <pre><code>(define-key function-key-map "\eOA" [up]) (define-key function-key-map "\e[A" [up]) (define-key function-key-map "\eOB" [down]) (define-key function-key-map "\e[B" [down]) (define-key function-key-map "\eOC" [right]) (define-key function-key-map "\e[C" [right]) (define-key function-key-map "\eOD" [left]) (define-key function-key-map "\e[D" [left]) </code></pre> <p>A true solution would involve finding what's causing the problem. It could be a bug in Screen, a bug in Emacs, a bug in the terminal (emulator) that Screen is running in, a bug or misconfiguration in your termcap or terminfo database. If you want to investigate this, start by mentioning your operating system, what terminal (emulator)(s) Screen is running in, where you obtained Screen (or how you compiled it, if that's what you did) and what version, ditto for Emacs, whether you've observed the same problem outside Screen, the output of <code>echo $TERM</code> and <code>echo -E "$TERMCAP"</code> inside Screen.</p>
    singulars
    1. This table or related slice is empty.
    1. PO"screen" somehow unmaps my arrow keys in emacs after a ^Z
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USGilles
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO"screen" somehow unmaps my arrow keys in emacs after a ^Z
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload