[bug #48464] term in IUCLC aka ILCASE mode does not treat backslash as escape

[Kalle Olavi Niemitalo]

URL:
  <http://savannah.gnu.org/bugs/?48464>

                 Summary: term in IUCLC aka ILCASE mode does not treat
backslash as escape
                 Project: The GNU Hurd
            Submitted by: kon
            Submitted on: Mon Jul 11 11:37:52 2016
                Category: Hurd Servers
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Hardware Support
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
         Reproducibility: Every Time
              Size (loc): None
         Planned Release: None
                  Effort: 0.00
Wiki-like text discussion box: 

    _______________________________________________________

Details:

If the IUCLC (also known as ILCASE) input mode is enabled and an upper-case
letter comes from the terminal, then the term translator replaces it with the
lower-case equivalent.  I believe this is intended to let the user type
lower-case characters even on terminals that support only upper case.

The term translator also supports the LAST_SLASH flag to temporarily suspend
this translation.  It however never sets that flag.  A comment in term/term.h
says LAST_SLASH means the last input character was a backslash.  In
term/munge.c (input_character), the part that checks the LAST_SLASH seems to
assume that the backslash was also stored to the rawq, and erases it from
there.  I don't know whether the backslash was also supposed to be echoed back
to the terminal.

The symbol IUCLC was removed in Open Group Base Specifications Issue 6. 
NetBSD and Linux do not implement it.  The GNU C Library manual does not
document it.  Upper-case-only terminals are not common nowadays.  I suggest
removing this feature from the Hurd.





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?48464>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/