Re: console vs ^X

[Thomas Wolff <towo at towo dot net>]

Christopher Faylor schrieb:
> On Tue, Sep 29, 2009 at 05:05:04PM +0200, Corinna Vinschen wrote:
>   
> > On Sep 29 10:50, Christopher Faylor wrote:
> >     
> > > On Tue, Sep 29, 2009 at 03:34:15PM +0200, Corinna Vinschen wrote:
> > >       
> > > > > I assume the only safe approach is to ignore the keypress entirely
> > > > > if it's not in the current charset.
> > > > >           
> > > > We could also just replace the char with a question mark.  That's what
> > > > cmd does in border cases, AFAICS.  Sometimes it replaces the character
> > > > with a base character (in 1251, for instance, a-umlaut with just a),
> > > > but that's not something we can do in a simple way.
> > > >
> > > > So, ignore the key or question mark?
> > > >         
> > > How about a question mark and a beep, or just a beep?
> > >       
> > What concerns me a bit is, if a copy/paste into the console contains
> > lots of invalid chars.  It's not fair to the user's ears ;)
> >
> > OTOH, it's probably not fair to the user to ignore these chars silently.
> >
> > Hmm.
> >
> > Maybe beep+question mark is the best.
> >     
>
> Maybe a beep+question mark+popup dialog would be best.  We could call this
> Unknown Alternate Character processing.
>
> cgf
>   
I would ignore and beep, i.e. let the terminal beep but don't insert 
anything, so there's no beep that could be copied.
I think that's what most other terminals do, can check tomorrow.

Thomas