Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Hikaru Ichijyo <ichijyo@macross.sdf.jp>
To: info-gnus-english@gnu.org
Subject: Re: alt-tab? really? you're joking...
Date: Sat, 24 Jan 2015 17:40:53 -0600	[thread overview]
Message-ID: <8xxegqj692y.fsf@village.keycorner.org> (raw)
In-Reply-To: <mailman.18502.1422100844.1147.info-gnus-english@gnu.org>

asjo@koldfront.dk (Adam Sjøgren) writes:

> Hikaru writes:
>
>> "The suggested workarounds are to rebind the ispell key (the BBDB
>> binding is not configurable at this time)."
>
> I don't know what "configurable" means here - when I type the beginning
> of an email address in, say, the To: line and press TAB, I get
> completion. This is with BBDB version 2.36.
>
> Where in BBDB was this M-TAB business annoying you?

Well, it's not anymore!  As I've said, I'm on v3 now.  I'm not going
back to v2 to look more at its behavior, because it's moot to me now.
Problem solved!  The "configurable" comment above is quoted from the
BBDB v2 manual.


Now, I do have another question of course (us Gnus newbies like me have
those without end, I'd imagine...):

Is there a way I can make messages that I have already expired from the
Summary buffer really disappear from view?  If I run expiry on them,
the "E" expiry marks are replaced with "G" cancelled marks.  If I run
any of the various "really delete" commands on them (such as
gnus-summary-delete-article), same thing, "G" cancelled, but still
there, even though it points to nothing.

Most surprisingly, if I run gnus-summary-reselect-current-group, a
command that's described in the manual as being just like leaving the
group and re-entering it without having to actually do that, it does
exactly the same thing -- all expired articles are still visible with
cancelled marks on them, even though if I had truly left and re-entered,
they'd be gone from my display.

Is there any way I can make cancelled messages just go away?  (After
all, they don't even exist anymore...)

-- 
He that would make his own liberty secure must guard even his enemy from
oppression; for if he violates this duty, he establishes a precedent
that will reach to himself.
					--Thomas Paine
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  parent reply	other threads:[~2015-01-24 23:40 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23  3:50 Hikaru Ichijyo
2015-01-23  4:17 ` Charles Philip Chan
2015-01-23  5:34 ` Pascal J. Bourguignon
2015-01-23 14:38   ` Hikaru Ichijyo
2015-01-23 14:50     ` Pascal J. Bourguignon
2015-01-23 22:20     ` Charles Philip Chan
2015-01-23 10:26 ` Tassilo Horn
     [not found] ` <mailman.18427.1422008816.1147.info-gnus-english@gnu.org>
2015-01-23 14:47   ` Hikaru Ichijyo
2015-01-26  8:12     ` Tassilo Horn
     [not found]     ` <mailman.18637.1422259999.1147.info-gnus-english@gnu.org>
2015-01-26 21:18       ` incal
2015-01-26 21:34         ` incal
2015-01-27  9:51           ` Tassilo Horn
     [not found]           ` <mailman.18727.1422352295.1147.info-gnus-english@gnu.org>
2015-01-27 20:24             ` more keys in a Linux VT (was: alt-tab? really? you're joking...) Emanuel Berg
2015-01-24  0:12 ` alt-tab? really? you're joking incal
2015-01-24  4:40   ` Hikaru Ichijyo
2015-01-24 10:34     ` incal
2015-01-24 12:00     ` Adam Sjøgren
     [not found]     ` <mailman.18502.1422100844.1147.info-gnus-english@gnu.org>
2015-01-24 23:40       ` Hikaru Ichijyo [this message]
2015-01-25  2:07         ` Winston
2015-01-25  2:55           ` Hikaru Ichijyo
2015-01-25  8:38             ` Glyn Millington
2015-01-25  8:40             ` Glyn Millington
2015-01-25  8:59         ` Immediate expiration Damien Wyart
2015-01-25 20:32           ` Hikaru Ichijyo
2015-01-25 12:41         ` alt-tab? really? you're joking incal
2015-01-25 13:00           ` new subject (was: alt-tab? really? you're joking...) Peter Münster
     [not found]           ` <mailman.18547.1422190826.1147.info-gnus-english@gnu.org>
2015-01-25 13:37             ` incal
2015-01-25 13:42               ` incal
2015-01-25 19:58               ` new subject Peter Münster
2015-01-25 20:36                 ` Clemens Schüller
     [not found]                 ` <mailman.18582.1422218214.1147.info-gnus-english@gnu.org>
2015-01-25 20:53                   ` Emanuel Berg
2015-01-26  8:04                     ` Peter Münster
     [not found]                     ` <mailman.18636.1422259506.1147.info-gnus-english@gnu.org>
2015-01-26 19:35                       ` Emanuel Berg
     [not found]               ` <mailman.18578.1422215928.1147.info-gnus-english@gnu.org>
2015-01-25 20:51                 ` Emanuel Berg
2015-01-25 22:19         ` alt-tab? really? you're joking Adam Sjøgren
2015-01-26  8:15           ` Tassilo Horn
2015-01-26 10:12             ` Adam Sjøgren
     [not found]             ` <mailman.18642.1422267150.1147.info-gnus-english@gnu.org>
2015-01-26 19:48               ` Emanuel Berg
2015-01-27  0:15               ` Hikaru Ichijyo
2015-01-27  1:21                 ` spam (was: alt-tab? really? you're joking...) incal
2015-01-27  2:51                   ` spam Hikaru Ichijyo
2015-01-27  3:11                     ` spam incal
2015-01-25 12:32       ` alt-tab? really? you're joking incal

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=8xxegqj692y.fsf@village.keycorner.org \
    --to=ichijyo@macross.sdf.jp \
    --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).