This is an old bug that did not gain substantial momentum after being
marked 'needs-progress' for a considerable amount of time.

The bug is closed as 'dead'.

If someone is actually working(!) on this issue again feel free to
reopen it, so the progress can be monitored within the BTS.

This is an old bug that did not move for a considerable amount of
time. Therefore this issue is marked as 'needs-progress'. We will be
monitoring this issue for the period of a month. If it does not gain
substantial momentum up to that time, the bug will be closed as 'dead'.

What about this issue?

The problem, which the actual issue-title talks about should be fixed
in recent versions of grml-etc-core.

I didn't look at what the rest of the patches do.

An update about the status of this would be good.

Regards, Frank - who sets 'status' to 'chatting' for now

* Michael Prokop <bts@bts.grml.org> [2008-02-13 15:57]:
> > Some settings are done twice. First in /etc/vim/vimrc and again in
> > /etc/skel/.vimrc. Is that intended for e.g. user who just get .vimrc
> > on another distribution?
> No, we should sort out what should be placed in the global and what
> in user's file.
So, 'important' settings should go into /etc/vim/vimrc, I guess. But
deciding which ones are 'important' and which not, may be a though
call.

> The patch looks fine to me, but I'll adjust the:
> [...]
> => too many people contributed to the vimrc already and I don't want
> to flood the header with several names. My name is there just
> because of historical reasons (I often forget to remove it from my
> default header when the file is being team-maintained, sorry),
> should be dropped as well of course.
That was just my function vimrc_grmlHeader[1] speaking. Normally I
check for such not necessary changes. Sorry. I guess, I should rewrite
that function. .oO( I'm so lazy!!!1! )
Didn't mean to cause unnecessary work.


                   ---------- Footnotes ----------

[1] http://bts.grml.org/grml/issue314

* Alexander Steinböck <bts@bts.grml.org> [20080213 15:52]:

> As I was working on /etc/skel/.vimrc, I took the liberty to make this
> config a little more readable.
> I provided the long forms of the mentioned settings plus a short
> description - because it was done in /etc/vim/vimrc as well - and
> integreated foldings.

Great.

> A question though.
> Some settings are done twice. First in /etc/vim/vimrc and again in
> /etc/skel/.vimrc. Is that intended for e.g. user who just get .vimrc
> on another distribution?

No, we should sort out what should be placed in the global and what
in user's file.

The patch looks fine to me, but I'll adjust the:

> -" Authors:       grml-team (grml.org), (c) Michael Prokop <mika@grml.org>
> +" Authors:       grml-team (grml.org), (c) Michael Prokop <mika@grml.org>,
> +"                Alexander Steinb�<z3ttacht@grml.org>

=> too many people contributed to the vimrc already and I don't want
to flood the header with several names. My name is there just
because of historical reasons (I often forget to remove it from my
default header when the file is being team-maintained, sorry),
should be dropped as well of course.

thx && regards,
-mika-

As I was working on /etc/skel/.vimrc, I took the liberty to make this
config a little more readable.
I provided the long forms of the mentioned settings plus a short
description - because it was done in /etc/vim/vimrc as well - and
integreated foldings.

A question though.
Some settings are done twice. First in /etc/vim/vimrc and again in
/etc/skel/.vimrc. Is that intended for e.g. user who just get .vimrc
on another distribution?

* Alexander Steinböck <bts@bts.grml.org> [2008-02-13 15:33]:
> Prevent setting the title for e.g. screen's hardstatus by vim - as
> recently implemented[1] - when editing mails.
Thanks go to ft (Frank Terbeck) for pointing me to `set notitle'.

Prevent setting the title for e.g. screen's hardstatus by vim - as
recently implemented[1] - when editing mails. Otherwise the window
name may get very long and may screw up screen's hardstatus line. On
the other hand renaming the window to `&shell'[1] after editing the
mail is prevented.

                   ---------- Footnotes ----------

[1] http://hg.grml.org/grml-etc-core/rev/acfecae478bc