Notes: lower in column 2 than column 1
See original GitHub issue> Column 1 starts here (insert column break)
> Column 2 starts here
I can only drop column 1 to match column 2 - I can’t find a way to raise column 2.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Two-Column Note-Taking | Facing History and Ourselves
The Two-Column Note-Taking strategy encourages students to identify important information in a lecture, film, or reading and to then respond ...
Read more >How to drop one or multiple columns in Pandas Dataframe
To Delete a column from a Pandas DataFrame or Drop one or more than one column from a DataFrame can be achieved in...
Read more >Using and formatting columns in Microsoft Word
How to insert multiple columns into your Microsoft Word document, plus navigating between columns and starting-and-stopping columns mid-document.
Read more >Insert a column break - Microsoft Support
Place your cursor where you want the column to break. Click Layout > Breaks. In Word 2013 or Word 2010, click Page Layout...
Read more >Column 1 / Column 2 / MFN / NTR - Countries that does ...
Currently, the countries with Column Two status are Cuba, North Korea, Russia and Belarus.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oddly the default CSS adds a 13-pixel top margin for
pre+blockquote
, i.e. for notes after a column break. I assume that’s there for a reason, so I’m reluctant to disable that bit of the default style; instead, you could drop the note in the first column by a matching amount. Add this to the beginning of your brew:Fixed in V3. Won’t fix in Legacy since it requires a lot of refactoring that would break a lot of old brews.