disowned not the job expected

[Dan Jacobson]

Another disown adventure.
# suspend
[1]+  Stopped                 su
$ emacs -f gnus fileA &
[2] 4865
$ disown
bash: warning: deleting stopped job 1 with process group 3457
$ jobs
[2]-  Running emacs -f gnus fileA &

$ help disown
disown: disown [-h] [-ar] [jobspec ...]
    By default, removes each JOBSPEC argument from the table of
    active jobs. If the -h option is given, the job is not removed
    from the table, but is marked so that SIGHUP is not sent to the
    job if the shell receives a SIGHUP. The -a option, when JOBSPEC is
    not supplied, means to remove all jobs from the job table; the -r
    option means to remove only running jobs.

But you don't mention what should happen if given no arguments!

I thought it would delete the last job but it instead had different
ideas this time. Certainly in the past I only had experience with one
job. OK, must always use jobspec to be sure.

Also pstree shows job 1 still alive. There should be a command to somehow
reattach it.

That was a big blow. No way to get back into my su session.

Also, on the man page also please add the word JOBSPECS here:

     JOBSPECS
       There are a number of ways to refer to a job in the shell.  The  
character  %  intro-
       duces a job name.  Job number n may be referred to as %n.  A job may 
also be referred
       to using a prefix of the name used to start it, or using a substring 
that appears  in

Else it is very hard to find where the definition of jobspec, so often
talked about on the man page, is.

Anyway, I was looking for a sure fire way to do
$ bla& disown
and always disown bla. But it seems I will have to do
$ bla& disown %bla
or how does one guarantee no mishaps? disown %what not hardwiring bla?