`port edit`, local/console vs. remote use

[Rainer Müller]

On 2016-12-07 12:20, René J.V. Bertin wrote:
>> What does that achieve that setting $EDITOR doesn't?
> 
> For one thing it would also provide a convenient way to use a simple,
> lightweight editor when you want or have to avoid the usual editor
> for a few quick changes. The standard vi fallback also has certain
> power-user features that aren't always available in otherwise more
> convenient GUI editors. Evidently you can do `env EDITOR=foo port
> edit bar` or `vi `port file bar`` but 1) `port -f edit bar` is much
> quicker to type and 2) you have to remember the priorities among the
> 3 supported env. variables.

This is really not a problem of port(1). As said before, configure
MP_EDITOR, VISUAL or EDITOR according to your environment.

If you need to override the environment, port(1) already supports the
parameter 'port edit --editor ...' for that. You can already shorten
that to 'port ed --e ...'.

If you still need something shorter, think about a shell function or alias.

Rainer