unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alex <agrambot@gmail.com>
Cc: 35058@debbugs.gnu.org
Subject: bug#35058: [PATCH] Use display-graphic-p in more cases
Date: Tue, 02 Apr 2019 21:39:52 +0300	[thread overview]
Message-ID: <838swsfdzb.fsf@gnu.org> (raw)
In-Reply-To: <878swsp9wh.fsf@gmail.com> (message from Alex on Tue, 02 Apr 2019 11:57:50 -0600)

> From: Alex <agrambot@gmail.com>
> Cc: 35058@debbugs.gnu.org
> Date: Tue, 02 Apr 2019 11:57:50 -0600
> 
> >> Hmm, it seems that my terminal Emacs accepts the super modifier but not
> >> the hyper modifier; is this a bug in Emacs?
> >
> > I don't know.  What do you mean by "accept"?
> 
> I can get terminal Emacs to recognize the super modifier (it shows up in
> C-h l as a `s-' prefix), but not the hyper modifier (all input is
> treated as if it wasn't used at all).

That might mean your terminal is unable to _generate_ the modifier.
What happens if you use the "C-x @ h" prefix, does it produce
hyper-modified keys?

> > If it is very inconvenient to use hyper on text terminals, then I
> > think we shouldn't require users to do that.
> 
> It wouldn't be a matter of requiring, but instead forcing the modifier
> back to 'meta if both in terminal Emacs and cua-rectangle-modifier-key
> is 'hyper.

Sorry, I don't understand.  Can you show how would you like to remove
the condition?

> > You mean, C-m/RET on the one hand and [return] on the other, right?  I
> > think a new predicate could be beneficial, because the function keys
> > are supported on some text terminals, for example on MS-Windows.  How
> > about display-function-keys-p?
> 
> [return] is another example, but I believe C-m and RET can be different
> in graphical Emacs. In my config I do:
> 
>   (define-key input-decode-map "\C-m" [C-m])
> 
> This allows me to use the control modifier with m separate from both RET
> and [return], as `C-h c' on the return key outputs:
> 
>   RET (translated from <return>) runs the command newline
> 
> However, doing the same in terminal Emacs makes the return key use my
> custom [C-m] prefix. This is an example of the behaviour the predicate
> should be covering.

I think [return] the function key is a much more frequent case for the
distinction.  TTY frames generally don't have function keys as
symbols, they have escape sequences which we translate to function
keys.

> I'm not sure about display-function-keys-p. That would seem to imply
> behaviour surrounding the `Fn' key on many keyboards.

A doc string will explain what we mean.

> >> What about using display-multi-frame-p? Could there be some system
> >> that allows multiple frames, but no way to select between them?
> >
> > Text terminals can support multiple frames, so display-multi-frame-p
> > is not what we want here.
> 
> If that's the case, then why is display-multi-frame-p currently an alias
> for display-graphic-p?

I don't remember.  But maybe I'm splitting hair here, and we can use
this predicate for iconifying etc. as well.





  reply	other threads:[~2019-04-02 18:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-30 23:38 bug#35058: [PATCH] Use display-graphic-p in more cases Alex
2019-03-31 12:45 ` Basil L. Contovounesios
2019-03-31 15:37 ` Eli Zaretskii
2019-04-01  4:15   ` Alex
2019-04-01  5:21     ` Eli Zaretskii
2019-04-02 17:05       ` Alex
2019-04-02 17:23         ` Eli Zaretskii
2019-04-02 17:57           ` Alex
2019-04-02 18:39             ` Eli Zaretskii [this message]
2019-04-03  5:14               ` Alex
2019-04-03  5:29                 ` Eli Zaretskii
2019-04-03 20:26                   ` Alex
2019-04-05  7:29                     ` Eli Zaretskii
2019-04-05 16:35                       ` Alex
2019-04-05 18:51                         ` Eli Zaretskii
2019-04-07  5:11                           ` Alex
     [not found]     ` <<83a7hagv11.fsf@gnu.org>
2019-04-01 14:32       ` Drew Adams
2019-04-06  7:18         ` Eli Zaretskii
2019-04-07 13:50     ` Stefan Monnier
     [not found] <<8736n4ndav.fsf@gmail.com>

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=838swsfdzb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=35058@debbugs.gnu.org \
    --cc=agrambot@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).