multiple moving

multiple moving

[Paul Stevenson]

Doing 'B m' on multiple files can be achieved by setting a region, but
not process marks.  This seems odd to me.  Should the latter be the
normal behaviour, rather than the former?

-- 
.  Dr Paul Stevenson   .   Research Fellow   .   University of Surrey   .
.     phone: +44 (0) 1483 876795     .     fax +44 (0) 1483 876781      .
.    p.stevenson@surrey.ac.uk  .  http://www.ph.surrey.ac.uk/~phs3ps    .
.                           I dream in beige                            .

Re: multiple moving

[Kai Großjohann]

`# # # B m' works for me.
kai
-- 
The arms should be held in a natural and unaffected way and never
be conspicuous. -- Revised Technique of Latin American Dancing

Re: multiple moving

[Paul Stevenson]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> `# # # B m' works for me.
> kai

yes. hmm. It didn't work 20 minutes ago, but now I have posted to the
list a bogus problem, it does work. damn those pesky imps.

moving problem

[Jeff Senn]

Here's a nit that has been around for awhile:

When I move a message from an IMAP folder (B m), leave the group (q),
and then re-enter the group in a way that would try to "fetch" that
message (for example if it were within the last 10 messages: C-u 10 SPC)

I get the infamous "Wrong type argument: number-char-or-marker-p, Re:"
error.

A 'g' will rectify the problem.

-- 
-Jas

Re: moving problem

[Kai Großjohann]

On 09 Nov 2000, Jeff Senn wrote:

> When I move a message from an IMAP folder (B m), leave the group
> (q), and then re-enter the group in a way that would try to "fetch"
> that message (for example if it were within the last 10 messages:
> C-u 10 SPC)
> 
> I get the infamous "Wrong type argument: number-char-or-marker-p,
> Re:" error.

Whee.  This sounds as if nnimap didn't clear the server buffer.  When
you set debug-on-error to t, then look at the " *nnimap foo*" buffer
(note the leading space!), do you see anything suspicious?  Also (setq
imap-debug "*imap-debug*") and (setq nnimap-debug "*nnimap-debug*"),
then have a look at those two buffers.

Note that the last two buffers get large extremely fast, so you should
try to reproduce the error soon after setting the variables.

kai
-- 
The arms should be held in a natural and unaffected way and never
be conspicuous. -- Revised Technique of Latin American Dancing

Re: moving problem

[Jas]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> > When I move a message from an IMAP folder (B m), leave the group
> > (q), and then re-enter the group in a way that would try to "fetch"
> > that message (for example if it were within the last 10 messages:
> > C-u 10 SPC)
> > 
> > I get the infamous "Wrong type argument: number-char-or-marker-p,
> > Re:" error.
> 
> Whee.  This sounds as if nnimap didn't clear the server buffer.  When
> you set debug-on-error to t, then look at the " *nnimap foo*" buffer
> (note the leading space!), do you see anything suspicious?  Also (setq
> imap-debug "*imap-debug*") and (setq nnimap-debug "*nnimap-debug*"),
> then have a look at those two buffers.

Nope, nothing in the connection buffer...

Weird -- first error doesn't correctly enter the debugger...
But on the second try th traceback looks like this (the moved message
in question was probably 10423):

Signaling: (wrong-type-argument number-char-or-marker-p Re:)
  gnus-sorted-complement((10421 10422 Re: MB ANN: Announcing Multimedia) (10414 10415 10416 10417 10418 10419 10420 10421 10422 10423))
  gnus-select-newsgroup("INBOX" 10 nil)
  gnus-summary-read-group-1("INBOX" 10 nil nil nil nil)
  gnus-summary-read-group("INBOX" 10 nil nil nil nil nil)
  gnus-group-read-group(10 nil nil)
  gnus-topic-read-group(10)
  call-interactively(gnus-topic-read-group)

and something seems to be wrong with the debug tracing (current
CVS)....  

...arghpssfft... I don't have time to track down the meta-problems at
the moment -- more later unless you can replicate the problem and
want to take a shot...  

(The problem doesn't happen *all* the time on moves and deletes ... I
haven't quite narrowed it down to when...)

-- 
-Jas