Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: William Henderson <wmhenderson@freeshell.org>
To: info-gnus-english@gnu.org
Cc: "Adam Sjøgren" <asjo@koldfront.dk>
Subject: Re: Emacs 26.3
Date: Sun, 24 Nov 2019 11:28:29 -0700	[thread overview]
Message-ID: <87d0dhb036.fsf@sdf.org> (raw)
In-Reply-To: <87pnhhw6m5.fsf@tullinup.koldfront.dk> ("Adam =?iso-8859-1?Q?Sj=F8gren?= via info-gnus-english"'s message of "Sun, 24 Nov 2019 18:01:54 +0100")

Adam Sjøgren via info-gnus-english <info-gnus-english@gnu.org> writes:

> William writes:
>
>> emacs <filename> no longer works
>> emacs -f gnus  no longer works
>> they give simply emacs
>>
>> Or have I done something stupid??
>
> They work for me with GNU Emacs 26.3 on Debian.
>
> What happens if you go:
>
>   emacs -Q <filename>
>
> ? To rule your configuration out...

The same happens.

But the problem was that I had changed "emacs" in /usr/local/bin to
read: 'emacs-26.3 -fn "DejaVu Sans Mono-16"'

Changing my emacs  in /usr/local/bin back to a simple pointer to
emacs-26.3 fixes the problem.

BUT I am 80 and cannot read the default type face any more and although
C-x C-+/-/0 work it is necessary to apply that to every file called -
the commands are nor persistent.

-- 
William Henderson
aka Slackrat
http://billh.sdf.org/slackware.jpg

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  reply	other threads:[~2019-11-24 18:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-24 16:52 William Henderson
2019-11-24 17:01 ` Adam Sjøgren via info-gnus-english
2019-11-24 18:28   ` William Henderson [this message]
2019-11-24 18:58     ` Adam Sjøgren via info-gnus-english
2019-11-26  8:03     ` Fraga, Eric

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

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

  git send-email \
    --in-reply-to=87d0dhb036.fsf@sdf.org \
    --to=wmhenderson@freeshell.org \
    --cc=asjo@koldfront.dk \
    --cc=info-gnus-english@gnu.org \
    /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.
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 NNTP newsgroup(s).