unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Dr. Michael L. Dowling" <Mike.Dowling@t-online.de>
To: Stefan Kangas <stefan@marxist.se>
Cc: Alan Mackenzie <acm@muc.de>, 29357@debbugs.gnu.org
Subject: bug#29357: Cut and paste problems on Linux on a text virtual console no longer works
Date: Mon, 17 Aug 2020 11:53:31 +0200	[thread overview]
Message-ID: <20200817095331.GA723@moocow> (raw)
In-Reply-To: <CADwFkm=-HZbFVkChp4pBpXLhLw1W5ie_NgwBng=M=WwcDVhJHw@mail.gmail.com>

Hello, Stefan!

On Sun, Aug 16, 2020 at 01:48:30PM -0700, Stefan Kangas wrote:
> "Dr. Michael L. Dowling" <Mike.Dowling@t-online.de> writes:
> 
> > If I can be of any further assistance I would be willing to try, but I'd
> > need somebody to suggest how.
> 
> My idea was simply to test e.g. vim (or some $FOO text editor) and see
> how well it works with regards to split screen support.  But I guess
> they would have to do something similar to us according to what Alan has
> reported.  So I'm actually not sure that testing it will help much...

I've just downloaded vim, and, yes, cut-and-paste works with vim.

Personally, I prefer vi  as it is POSIX conforming.  You  can use the vi
on any  UNIX machine, and  cut-and-paste works with  the vi on  my Linux
computers.

The  trouble  with  the  vi  is  that  it  screws  up  indentation  with
cut-and-paste.  So I've used nano  instead, and cut-and-paste works with
that, too.

For me, the  burning question is whether or not  others can replicate my
experience with emacs.

The great thing  about Arch Linux is that we  configure stuff ourselves.
But the danger is that a  configuration that is continually being copied
with every  new computer  might well  propagate problems  resulting from
incompatibilities between various software releases.

I  try to  be cautious.   On this  machine, I  copied my  old /etc  to a
subdirectory  of /root,  and  inspected every  file  before copying  and
editing.

The problem  cannot lie with  individual user configuration, as  my user
"joe" only has a .bash_logout that deletes everything except itself, and
"joe" suffers  from the  same problem.  ("joe"  doesn't have  a ~/.emacs
file

> > I  had come  to the  conclusion  that I  was  one of  the last  die-hard
> > Linux/text-mode/command line users.
> 
> (You might enjoy hearing that RMS also uses Emacs on the Linux console.)

Interesting!  I have always had a great deal of respect for RMS.

Cheers,

Mike

-- 
Dr. Michael L. Dowling
Gaußstr. 27
38106 Braunschweig
Germany





      reply	other threads:[~2020-08-17  9:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-19 16:09 bug#29357: Cut and paste problems on Linux on a text virtual console no longer works Dr. Michael L. Dowling
     [not found] ` <CADwFkmm6hze_2h1fTDiqOFB2At1edfp=oJX5EQdxRidK8XWq0Q@mail.gmail.com>
     [not found]   ` <20200814195252.GA2819@moocow>
2020-08-14 23:16     ` Stefan Kangas
     [not found] ` <mailman.2142.1597447084.2739.bug-gnu-emacs@gnu.org>
2020-08-15  8:52   ` Alan Mackenzie
2020-08-16 15:46     ` Stefan Kangas
2020-08-16 19:36       ` Dr. Michael L. Dowling
2020-08-16 20:48         ` Stefan Kangas
2020-08-17  9:53           ` Dr. Michael L. Dowling [this message]

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=20200817095331.GA723@moocow \
    --to=mike.dowling@t-online.de \
    --cc=29357@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=stefan@marxist.se \
    /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).