On removing /set reverse_status_line

[Jeremy Nelson]

Zlonix suggested we should remove /set reverse_status_line in epic5. I am
not (necessarily) against this suggestion because I have a standing policy
to remove retarded /set's.

Generally when we've removed /set's in epic5, BlackJac (or myself) have
created scripted re-implementations and put them in 'builtins' script, so
those who are loading that script have some expectation of backwards
compatability.

We tried to remove this /set but we were unable to (properly) reimplement it
in a script. That means if we remove this /set, it would break backwards
compatability with all epic5 users. All epic5 users would have to ensure
that their /set status_format's start with ^V if they want them reverse.
This would not be required for epic4 users, and in fact, they must not do so.

Comments/thoughts/suggestions?

Thanks,
Jeremy

[Erlend Bergsås Mikkelsen]

Post by Jeremy Nelson
Zlonix suggested we should remove /set reverse_status_line in
epic5. I am
not (necessarily) against this suggestion because I have a standing policy
to remove retarded /set's.

I see no reason not to remove that set. Adding a ^v to the status line
doesn't seem like too worse a operation. And any /set made redundant, is
a good /set in my mind.

Med vennlig hilsen / Best regards
Erlend Bergsås Mikkelsen
Student ved Filosofisk institutt, NTNU
***@ebm.no
[phone]

[River Tarnell]

Post by Jeremy Nelson
We tried to remove this /set but we were unable to (properly) reimplement it
in a script. That means if we remove this /set, it would break backwards
compatability with all epic5 users. All epic5 users would have to ensure
that their /set status_format's start with ^V if they want them reverse.
This would not be required for epic4 users, and in fact, they must not do so.

this seems like a fairly small change compared to some other things in
epic5; i'd suggest removing it.

- river.

[Jason Brand]

I vote to remove. Adding ^V to the beginning of STATUS_FORMAT shouldn't
be a big deal for anyone.

-Jason

Post by Jeremy Nelson
Zlonix suggested we should remove /set reverse_status_line in epic5. I am
not (necessarily) against this suggestion because I have a standing policy
to remove retarded /set's.
Generally when we've removed /set's in epic5, BlackJac (or myself) have
created scripted re-implementations and put them in 'builtins' script, so
those who are loading that script have some expectation of backwards
compatability.
We tried to remove this /set but we were unable to (properly) reimplement it
in a script. That means if we remove this /set, it would break backwards
compatability with all epic5 users. All epic5 users would have to ensure
that their /set status_format's start with ^V if they want them reverse.
This would not be required for epic4 users, and in fact, they must not do so.
Comments/thoughts/suggestions?
Thanks,
Jeremy
_______________________________________________
List mailing list
http://epicsol.org/mailman/listinfo/list

[Jonas Trollvik]

I vote for remove aswell for the reasons already stated
//kreca

Post by Jason Brand
I vote to remove. Adding ^V to the beginning of STATUS_FORMAT shouldn't
be a big deal for anyone.
-Jason

Post by Jeremy Nelson
Zlonix suggested we should remove /set reverse_status_line in epic5. I am
not (necessarily) against this suggestion because I have a standing policy
to remove retarded /set's.
Generally when we've removed /set's in epic5, BlackJac (or myself) have
created scripted re-implementations and put them in 'builtins' script, so
those who are loading that script have some expectation of backwards
compatability.
We tried to remove this /set but we were unable to (properly) reimplement it
in a script. That means if we remove this /set, it would break backwards
compatability with all epic5 users. All epic5 users would have to ensure
that their /set status_format's start with ^V if they want them reverse.
This would not be required for epic4 users, and in fact, they must not do so.
Comments/thoughts/suggestions?
Thanks,
Jeremy
_______________________________________________
List mailing list
http://epicsol.org/mailman/listinfo/list

_______________________________________________
List mailing list
http://epicsol.org/mailman/listinfo/list

[Jeremy Chadwick]

Remove it.
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

Post by Jeremy Nelson
Zlonix suggested we should remove /set reverse_status_line in epic5. I am
not (necessarily) against this suggestion because I have a standing policy
to remove retarded /set's.
Generally when we've removed /set's in epic5, BlackJac (or myself) have
created scripted re-implementations and put them in 'builtins' script, so
those who are loading that script have some expectation of backwards
compatability.
We tried to remove this /set but we were unable to (properly) reimplement it
in a script. That means if we remove this /set, it would break backwards
compatability with all epic5 users. All epic5 users would have to ensure
that their /set status_format's start with ^V if they want them reverse.
This would not be required for epic4 users, and in fact, they must not do so.
Comments/thoughts/suggestions?
Thanks,
Jeremy
_______________________________________________
List mailing list
http://epicsol.org/mailman/listinfo/list

[Ben Winslow]

On Sun, 13 May 2007 12:28:54 -0500

Post by Jeremy Nelson
Zlonix suggested we should remove /set reverse_status_line in epic5. I am
not (necessarily) against this suggestion because I have a standing policy
to remove retarded /set's.

I vote to kill it.

--
Ben Winslow <***@bluecherry.net>