You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- 1i would advise you to never suggest any sort of terminal text editor, just use textedit.app in the command instead of nano, because terminal text editors are just barbaric.Alexander– Alexander2012-03-10 20:28:35 +00:00Commented Mar 10, 2012 at 20:28
- 12Nano is quite user-friendly, IMO, and it's really annoying to try to edit something with root privileges from the GUI.NReilingh– NReilingh2012-03-10 21:22:30 +00:00Commented Mar 10, 2012 at 21:22
- 13@XAleXOwnZX: I'm sorry but that's just bad advice. If anything, you'll find it next to impossible to edit these files in TextEdit.app because a lack of privileges, as NReilingh also pointed out. Also, it is not unreasonable to expect some aquaintance with the console from any (aspiring) web developer.Gerry– Gerry2012-03-11 21:08:55 +00:00Commented Mar 11, 2012 at 21:08
- generally works if u sudo itAlexander– Alexander2012-03-12 13:47:08 +00:00Commented Mar 12, 2012 at 13:47
- 9@XAleXOwnZX: With all due respect, that is arguably the worst advice I have ever seen on a Stack Exchange property. I agree that a GUI text editor is probably a better approach for people who are not programmers or who don't have much unix experience, however, TextEdit is the wrong application to advise using simply because it defaults to a variable-width font and rich text. This can cause all sorts of problems (beyond the simple usability nightmare of writing code in variable-width) that will be extremely difficult or impossible for this person to debug.lightyrs– lightyrs2012-05-13 00:35:10 +00:00Commented May 13, 2012 at 0:35
| Show 6 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. macbook-pro), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you