I have to admit, I didn't expect a further response questioning my experience with the app - this is more assumptive then needed, I've been doing this for some time, feel free to Google:). Unfortunately, me being critical of a critical response seems to have moved this conversation less on helping with the problem, and more on a character attack.
> I didn't take it that way at all. (Note, Rich even included a > smiley face.) In fact, I wasn't really able to assist with your > first query due to the misleading (or confusing) details > supplied. And speaking for myself, as soon as I'm confused about > what the OP is asking or what they did to get where they are, I > move on. Otherwise I'm doing mind-reading and enough past > experience has taught me that is a waste of my time (as well as > the OPs). > > Rich actually took the next step and asked for some > clarification so that he could assist. That is only combative to > someone looking for combat. And in your follow-up reply you have > given some info that makes the situation more clear and may even > point to some specific things to look at. (suggestions below) > Fair enough - I saw the smiley face, but that was in the beginning, the last comment seemed traditional brush off - and again I read the tone as less listening. > <rant relevance="medium"> > As a coder I expect clear explanations; zap gremlins is a > different issue from fixing line-endings (again, confusing). And > "clean code"?? You must be joking to think that was any sort of > decent problem description; does that mean code that was > indented properly, or code that compiles without errors, or code > that is easy to read by others, or ... no, you mean files with > valid line-endings; how silly of me not to read your mind. Now, > if you were talking about designers; sure, they work in a > different creative area; they may need assistance getting to the > core of an issue like this (and plenty of designers use & love > BBEdit, please don't take my comment as derogatory). But > "coders"; they should know better when explaining problems. > Anyway, in order to be helpful... > </rant> It was a good rant:) I dabble in both worlds, and understand very well the comparison between the designer and the coder stereotype, but it doesn't fit for all modes of people, and it especially doesn't fit here. Clean code, from everyone I've talked of, simply meant code without errors in interpretation. In fact, my email to BBEdit support this afternoon didn't have any problems with this wording.... and, zap gremlins can fix malformed line endings. > > >Saving out a file from BBEdit, for example, an html file type. File is > >uploaded via transmit to web server, and, depending on the browser, > >often shows a ? in an area of a space or a line ending. > > Is the FTP upload being done in binary or text mode? SFTP set to auto binary or ascii > > Which indicates the file has mis-matched line endings (& yes > there is a more technical term for that which I forget right > now). Try the Text -> Normalize Line Endings command; that > should fix the file so that both BBEdit and Coda can open it > with consistent line endings. Note, zapping gremlins is the not > the same as fixing the line endings. I know the difference, as I mentioned above we have issues with both, and zapping gremlins does fix malformed line endings. Normalizing the line endings doesn't fix the space issues, you are correct (although you didn't get there yet). > I have seen on more than one occasion when *some* coders used > sub-standard tools that didn't handle line-ending gracefully; > the files ended up with "corrupt" line endings. Until I fixed > (normalized) the line endinings in those files, the "corruption" > persisted. One reason I use/like BBEdit is due to how easily it > can identify and fix issues like that. But you do have to use > the tool (BBEdit) properly. I've been using BBEdit since 3, right around when there was still a BBEdit lite in my younger days, so I'm comfortable with this. Regardless, my concern is if something has changed since the recent update, as I never had a problem for this on almost a decade of using BBEdit. ...and Coda, albeit in some ways inferior to BBedit in some areas, doesn't sit as substandard - especially running the Subethaedit engine. > > And issues like this are an excellent example of when turning > the superb manual can really help. Eg. open the manual and type > "convert line ending" and the first hit is "Normalize Line > Endings". Trying that search before coming to this list for > help, and certainly before switching other developers in your > office to a different program, would have been a great time-saver. Now you're being rude:) - I came here for help after I looked in every avenue; from google to manual, and as I noted above I normalized the line endings, that isn't the problem here. > > Also note the following in the footer of each message on this list: > > >If you have a feature request or would like to report a > >problem, please email "[email protected]" rather than > >posting to the group. > > If you continue having problems, I would bet you can send an > example problem file to support and they would be happy to help > find the cause of the problem so you know how to fix others like it. > > Or keep coming back to this list by all means. But please know > that when someone on this list asks for more info; it's because > they are taking time out of *their* busy day to help *you*. It > is not due to some desire for combat. There are lots of friendly > and helpful people here if you let them. > > Charlie Obviously you took yours far from friendly, and although I appreciate the time, not very helpful. Like most of you, I've spent my time on forums for most of my developer life; preaching appreciation is an old hat that most of us have gone through, but you've taken it a little further then simply helping. I do indeed appreciate the help, as others have thanked me for helping them, like all of you have gone through... but if you want help, feel free to spend less time on the traditional rants, as your day is quite busy.
-- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/bbedit?hl=en If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group.
