Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "Adam Sjøgren" <asjo@koldfront.dk>
To: info-gnus-english@gnu.org
Subject: Re: on automatic gnus-summary-insert-new-articles after posting
Date: Sun, 29 Jul 2018 20:03:06 +0200	[thread overview]
Message-ID: <87in4xly1x.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <864lginhl8.fsf@dev.null>

Robert writes:

> Adam Sjøgren <asjo@koldfront.dk> writes:
>
>> How did you get the clear idea with slrn?
>
> I think the explanation to this psychology is that simpler is easier to
> understand.  I haven't used slrn in a while so I hardly remember the
> complaints I had there.  It's coming to me now that I could only edit
> one article at a time there because slrn doesn't have the window
> concept.  I had to draft an article, edit another.

Ok, I was fishing after what behaviour you would like to see, for you to
get the overview you are lacking.

I am so used to previously read articles not being shown that it feels
very natural to me, but I know that it's different for different people
:-)

[Delayed sending]

> I'm using it now.  Trying it out.  I tried offline mode, but it seemed
> not very easy to understand how to really use it, so I'm back at online
> mode with some caching and using delayed articles.  Thanks for suggesting.

You're welcome - for what it's worth I've never had use for
offline-mode/the agent.


  Best regards,

    Adam

-- 
 "I pragmatically turn my whims into principles!"             Adam Sjøgren
                                                         asjo@koldfront.dk


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

      reply	other threads:[~2018-07-29 18:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-28 15:35 Robert Girault
2018-07-28 16:13 ` Eric Abrahamsen
     [not found] ` <mailman.4364.1532794430.1292.info-gnus-english@gnu.org>
2018-07-28 19:54   ` Robert Girault
2018-07-28 20:42 ` Winston
2018-07-28 20:59   ` Eric Abrahamsen
     [not found]   ` <mailman.4365.1532811610.1292.info-gnus-english@gnu.org>
2018-07-29  0:19     ` Robert Girault
2018-07-29  6:52       ` Eric Abrahamsen
2018-07-29  8:07         ` Adam Sjøgren
2018-07-29 16:42           ` Eric Abrahamsen
2018-07-29 18:04             ` Adam Sjøgren
2018-07-29  8:03       ` Adam Sjøgren
2018-07-29 14:37       ` Winston
     [not found]       ` <mailman.4370.1532847194.1292.info-gnus-english@gnu.org>
2018-07-29 16:00         ` Robert Girault
2018-07-29 16:15           ` on continuing from where left off (Was: Re: on automatic gnus-summary-insert-new-articles after posting) Robert Girault
2018-07-29 17:17           ` on automatic gnus-summary-insert-new-articles after posting Eric Abrahamsen
2018-07-30  1:26           ` Robert Girault
     [not found]       ` <mailman.4372.1532851440.1292.info-gnus-english@gnu.org>
2018-07-29 16:04         ` Robert Girault
2018-07-29 18:03           ` Adam Sjøgren [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

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

  git send-email \
    --in-reply-to=87in4xly1x.fsf@tullinup.koldfront.dk \
    --to=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).