[
https://issues.apache.org/jira/browse/CASSANDRA-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745215#action_12745215
]
Eric Evans commented on CASSANDRA-373:
--------------------------------------
>Who seriously uses a vt100 rather than remoting in these days? You can always
>use a larger terminal and/or an editor that handles wrapped lines sanely.
You have to wrap somewhere; the point of 80 chars is that it is the minimum you
could expect to see in use.
This is pretty much best practice among projects with hand edited configuration
files. A quick survey of the files under /etc on any *nix box should confirm
this.
> storage-conf.xml reformatting
> -----------------------------
>
> Key: CASSANDRA-373
> URL: https://issues.apache.org/jira/browse/CASSANDRA-373
> Project: Cassandra
> Issue Type: Bug
> Reporter: Eric Evans
> Assignee: Eric Evans
> Attachments:
> v1-0001-CASSANDRA-373-re-format-factor-conf-storage-conf.xml.txt,
> v2-0001-CASSANDRA-373-re-format-factor-conf-storage-conf.xml.txt
>
>
> Our sample config (conf/storage-conf.xml) is the canonical source of
> configuration documentation. As such readability should be a priority, and it
> should serve as the best possible basis for customization.
> I propose the following:
> 1. Wherever possible, lines should wrap at 75 chars. The file will be edited
> post-installation by operational personnel, who are often confined to
> standard 80 character terminals.
> 2. Indention of 2 spaces to make maximum use of horizontal real estate.
> 3. More distinctive multi-line comments.
> 4. Path locations that conform to the FHS.
> Patch to follow...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
