Comment 10 for bug 3780

On Thu, 2006-10-19 at 06:00 +0000, Martin Pool wrote:
> On 19 Oct 2006, Aaron Bentley <email address hidden> wrote:
> > Richard Wilbur wrote:
> > > John, Martin, et al:
> > >
> > > 2. Jules does a find of certain files he wants to ignore and notices that in a particular subdirectory of his branch a certain filetype appears. He types
> > > ``bzr ignore /absolute/path/from/find/*.filetype`` and, since it is in his branch, a branch-root-relative pattern is added to the ignore file. (Advantage: Jules can select/copy and paste the path from the find output directly into his command line without having to trim to his branch base directory.)
> >
[...]
> I'm not sure I understand. (In retrospect I'm not sure if Jules in
> Richard's example is meant to be giving a filename or a quoted pattern
> or an unquoted pattern, but since he talks of copy/pasting the output of
> find I assume it is a file.)
>
> --
> Martin
I forgot to quote the pattern. Oops! Sorry for the confusion.
``bzr ignore
'/really/miserably/obtusely/historically/extensively/long/absolute/path/from/find/pointing/into/package/*.filetype'``

I have unfortunately worked on projects with paths that wrapped on an
eighty-column terminal. So Jules sees a path that is producing, or
inhabited with, a certain filename pattern he wishes to ignore. Rather
than trim the path to 'extensively', which might be his branch root, and
add a '.' to make it relative, and then fix the other end of the
pattern, he can simply paste the whole mess in and deal with the pattern
(at the leaf end) which was the whole point after all.

This doesn't break any current functionality, and it extends it in the
same fashion as the relative path changes associated with the
specification of this bug. My suspicion is that this change offers
simpler and more expedient user interaction.

Richard