store and display view as wildcards, not as a list of files

[Juanma Barranquero]

It would be useful if the view command supported specifying wildcards (both inclusive and exclusive) to select files; in particular when the view must affect many files (there are 302 .el files on the emacs lisp/ directory, not counting subdirectories, for example), or files with similar names in many directories (58 ChangeLog* files in 24 directories).

Another benefit is that

  C:\emacs\trunk> bzr status
  Using 'ChangeLogs' view: */ChangeLog*

is a bit less hostile that

  C:\emacs\trunk> bzr status
  Ignoring files outside view. View is ChangeLog, admin/ChangeLog, doc/emacs/ChangeLog, doc/lispintro/ChangeLog, doc/lispref/ChangeLog, doc/man/ChangeLog, doc/misc/ChangeLog, etc/ChangeLog, leim/ChangeLog, lib-src/ChangeLog, lisp/ChangeLog, lisp/ChangeLog.1, lisp/ChangeLog.10, lisp/ChangeLog.11, lisp/ChangeLog.12, lisp/ChangeLog.13, lisp/ChangeLog.14, lisp/ChangeLog.2, lisp/ChangeLog.3, lisp/ChangeLog.4, lisp/ChangeLog.5, lisp/ChangeLog.6, lisp/ChangeLog.7, lisp/ChangeLog.8, lisp/ChangeLog.9, lisp/erc/ChangeLog, lisp/erc/ChangeLog.01, lisp/erc/ChangeLog.02, lisp/erc/ChangeLog.03, lisp/erc/ChangeLog.04, lisp/erc/ChangeLog.05, lisp/erc/ChangeLog.06, lisp/erc/ChangeLog.07, lisp/erc/ChangeLog.08, lisp/gnus/ChangeLog, lisp/gnus/ChangeLog.1, lisp/gnus/ChangeLog.2, lisp/mh-e/ChangeLog, lisp/mh-e/ChangeLog.1, lisp/org/ChangeLog, lisp/url/ChangeLog, lwlib/ChangeLog, msdos/ChangeLog, nextstep/ChangeLog, nt/ChangeLog, oldXMenu/ChangeLog, src/ChangeLog, src/ChangeLog.1, src/ChangeLog.10, src/ChangeLog.2, src/ChangeLog.3, src/ChangeLog.4, src/ChangeLog.5, src/ChangeLog.6, src/ChangeLog.7, src/ChangeLog.8, src/ChangeLog.9, test/ChangeLog

[Martin Pool (mbp)]

The view command already supports wildcards on the command line. This bug is asking for two more things, which could be done separately:

1- if there are multiple files in the view, show them more concisely in 'bzr status'
2- support storing the actual wildcard as the view configuration

[Juanma Barranquero (lekktu)]

On Mon, Jan 4, 2010 at 02:36, Martin Pool <email address hidden> wrote:

> The view command already supports wildcards on the command line.

To be pedantic, it is not true that "the view command supports
wildcards on the command line", because it does not even see them. The
unixy shells support wildcard expansion on the command line, which is
not the same. "bzr view mywildcard*" on Windows does not work because
Windows command shells usually do not expand wildcards.

> This bug is asking for two more things, which could be done separately:
>
> 1- if there are multiple files in the view, show them more concisely in 'bzr status'
> 2- support storing the actual wildcard as the view configuration

1 is nice, though not what I asked; if I used "bzr view file1...
file100" I would expect bzr status to show them all; but in "bzr view
file*", where file* affects 100 files, definitely no. So I asked for:

1.- In 'bzr status', show files as passed to 'bzr view' (taking into
account that wildcards will have to be passed quoted, or somesuch).
2.- support storing wildcards in the view configuration
3.- the wildcards in 2 should allow also excluding files, for example
(syntax irrelevant) "bzr view *.el !myfile.el" to exclude myfile.el.

    Juanma

[Aliaksei Vasileuski (sagara1337)]

>"bzr view mywildcard*" on Windows does not work because
>Windows command shells usually do not expand wildcards.
BTW "bzr shell" won't expand wildcards on any platform, so it is easier to implement at least for the shell.

[Martin Pool (mbp)]

2010/1/6 Nishi <email address hidden>:
>>"bzr view mywildcard*" on Windows does not work because
>>Windows command shells usually do not expand wildcards.

iiuc bzr 2.1 expands the wildcard itself on Windows

> BTW "bzr shell" won't expand wildcards on any platform, so it is easier to implement at least for the shell.

that's a separate bug in bzr shell.

--
Martin <http://launchpad.net/~mbp/>

[Juanma Barranquero (lekktu)]

On Wed, Jan 6, 2010 at 04:59, Martin Pool <email address hidden> wrote:

> iiuc bzr 2.1 expands the wildcard itself on Windows

I stand corrected. I haven't installed the 2.1 betas.

Though useful, that does not help in the case that somewildcard* is a
large number of files.

    Juanma