Sometimes when I'm viewing existing code, some fragments appear very odd: one symbol per row with alignment to left. For example, I have opened some code of some framework and I saw that weird formatting in some fragments. I have checked that those lines do not contain tabs or spaces. So, what might be a cause? I would be cool to hear from you that you have experienced that too, so please mark a question or post to comments.
UPDATE: here's the screen:
That looks like a bug that you need to report to Apple.
Related
I have seen that the comments I write at the top of my Python methods and and classes is the same text that pops up when I am using them in my code. I have also seen that some formatting hints can be made in the comments, and that will translate into pretty rendering in the popup text (for instance, putting a bunch of "-"'s under a heading makes the font bigger and bolder). What other formatting is there and what are the hints? Specifically, is there "code" formatting that renders in monospace? I like to put code samples in my comments sometimes and that would look great.
Finally, does this all have a name? I tried googling what I was trying to do and it was hard because I didn't know what it was called.
In GitHub it's possible to suggest code changes through inline comments in pull requests. But I always get the following error message: "suggestions cannot be applied while viewing a subset of changes".
Is there also a way to manually suggest changes in a comment?
Example: screenshot of problem
Besides the button you can also actually use syntax to make a suggestion. You can do it like:
```suggestion
this is my new suggestion
```
How-to code suggest to multiple lines
Apply a code suggestion to multiple lines by highlight dragging the code lines. Starting drag to the right of the line numbers where the comment plus icon appears.
Verify by seeing "Commenting on lines +129 to +145" (or similar) text indicating the multiple line range you are commenting on.
Now the code suggestion will replace more than one line!
I've been working on a website and from time to time some elements are disappearing from the document. I've figured out that it's because in CSS document the early lines are not fully commented. I would like to ask why if even such a tiny thing like Skeleton's default version text is not fully commented or some of the classes or id's don't have a closing bracket then the whole website has layout problems. What skeleton's version has to do with page's body color ? This is really confusing.
Here is the HTML and CSS :
http://codepen.io/anon/pen/vIchA
I would be glad with any help. Yours truly,
D.
Browsers have to guess how to render bad code. Sometimes they will guess and render it correctly, other times it will look weird.
Different browsers are likely to render it differently (though error handling standards are improving)
In this case, your demo lacks a "/" at the start, which means it is trying to render the comments as css. The comments are not css, so it gets confused and does the best it can.
A quick way to find any bugs in the css is to use this:
http://jigsaw.w3.org/css-validator/
I do not know if this is a bug or rather stems from any customizations. I would like to know how to tackle this problem:
If I click on "add image" or "Link" in Plone's "Content Browser" the default view mode is "Album". In this mode the items are layed above each other, i.e. after 4 items the next items do not seem to be put into a new column.
See the screenshot:
Plone version is 4.3.2. How can I fix this? Pointers (relevant files, parts of code) welcome.
I have seen this happen too, depending on what I did with styling and skins. TinyMCE uses a grid system for showing these images and this needs the columns.css file from plonetheme.sunburst. I only now realize that this actually already goes wrong in the way you describe when you use standard Plone 4.3.2 and choose the classic theme as skin.
Ah, but it only fails because there is a typo in the columns.css that is shipped with plonetheme.classic, which actually includes the grid css as well. You can customize this file in portal_skins and fix the error. The problem is a line that is meant as a comment.
Change this line:
The 16-column Deco Grid System.
into this line:
/* The 16-column Deco Grid System.
im working on a CMS it is almost finished
but im struggling serious unfamiliar problems in WYSIWYG editor.
i was first using ckeditor but after experiencing problems with it i switched to tinymce.
some problems are solved but this time someother problems showed up.
problems occuring especially on tables.
1-Anchor element underline removal not working
2-Duplicating Phone numbers
--->might be due to skype phone number converting toolbar
3-too many s how to clean those why even those are there?
4-how to convert
<p>text</p>
back into just
text
because tinymce converting some texts into p element *automatically if it's not the client doing it unknowingly.
*=even though i did that force_paragraph:false setting.
5-As client reports : sometimes cursor turns into loading cursor and wysiwyg editor causes browser to stuck.not even allowing to click links outside of the editor.
6-as i experience sometimes it really does stuck and not allow you to edit anything at all.
here is that problematic page created with tiny_mce and causing lots of errors in process of editing:
Here some answers
2-Duplicating Phone numbers --->might be due to skype phone number converting toolbar
Might be - this cannot ba a tinymce related problem.
3-too many & nbsp;s how to clean those why even those are there?
Browsers will show several spaces (character code 32) as a single one. Thus & nbsp;s are inserted alternating instead of natural spaces.
4-how to convert
text
back into just text
Tinymce is a rte editor and will generate html code. In order to be able to style editor content, the content need to be wrapped inside a block element - eighter ps or divs. You may use server side code to remove tags.
6-as i experience sometimes it really does stuck and not allow you to edit anything at all.
Please describe a bit more in detail - there needs to be a reason for this.