Re: To Drew Adams?: `dired-get-marked-files' returns error when not onfile

[mafeusek]

"Drew Adams" <drew.adams@oracle.com> writes:

> However, the particular error you are concerned about is not distinguished 
> from
> any other errors this way: any error condition here will return nil instead of
> raising an error.

Hallo Drew.

The above is what concerns me most. I'd consider pointer not on file is not
an error, esspecialy not in non-interactive invocations.

What I am trying to do:
I am going to write a function that invokes command on:
a) files marked explicitly (ie. by `m')
or,
b) all files in directory if there are not marked files.

while acting non-interactivelly, it is hard to do it, unless I want to
hide all the errors with `condition-case' which I think is not reasoanble.

On the other hand in interactive invocation, error is helpful, thus maybe
 good enough choice would be to have optional pointer-away-no-error flag?

best regards,
Pawel