When exporting Org-mode content like this to HTML (i.e. C-c C-e h h)...
* Some project
** DONE Some final work
CLOSED: [2016-03-30 Wed]
Received final report blah blah...
** DONE Final tests
CLOSED: [2016-03-28 Mon]
...
...the CLOSED timestamps are not shown in the HTML output. To see if I can see exported timestamps at all, I manually went and changed the DONE entry to this:
* Some project
** DONE Some final work [2016-03-30 Wed]
CLOSED: [2016-03-30 Wed]
Received final report blah blah...
...and then the timestamp does indeed show, in the HTML TOC output (in light gray).
Even though I can use my editing foo to do this automatically, I'd rather not, if I can avoid it. Is there a way to force CLOSED timestamps to show in the Org-mode exported HTML output?
To include CLOSED timestamps in your exported file, add the following line at the top of your org file:
#+OPTIONS: p:t
Please refer to Export Settings for detailed information.
Related
This question already has answers here:
Automatically hard wrap lines at column in VSCode
(11 answers)
Closed 3 years ago.
In Visual Studio Code, when you press ALT SHIFT F to format HTML document, VS Code would wrap a line that is too long into multiple lines.
I think VS Code let the line grow too long before wrapping. Is there a setting in VS Code to tell it to wrap after certain line length?
This question is NOT a duplicate of the hard wrap question. This is about wrapping during format document process.
Open user settings: File - Preferences - Settings
Then add/edit this item:
"html.format.wrapLineLength": 80
FYI the new settings are in effect after you save the changes.
If you are formatting HTML and are annoyed that VScode formats your long lines into multiple lines, go to:
File > Preferences > Settings
Search for:
HTML › Format: Wrap Line Length
and set it to 0
How can we highlight SQL code in some log files, with Emacs?
Sample log file:
[DEBUG][2016-05-26 09:04:51,714][FileHelper] - [realContextPath=[/server.xml]]
[DEBUG][2016-05-26 10:24:22,369][DbConnectionImpl] - [DELETE FROM xct_log]
[DEBUG][2016-05-26 11:00:46,925][DataSourceRestrictionConverter] - [parseRestrictions]
[DEBUG][2016-05-26 10:24:22,476][DbConnectionImpl] - [UPDATE hlpdsk_step_log
SET table_name= 'hxct_log' WHERE
table_name='xct_log' AND pkey_value = 247296]
The goal would be to put a light yellow background behind SQL code, that is:
code found between the last [...] (can be on multiple physical lines, as shown in the last line of the log sample), and
code found on lines where the "source" (3rd bracket pair) is "DbConnectionImpl".
If possible, the yellow background should only be between those last 2 brackets, on the right lines.
Since it is Emacs, I am sure what you want is possible,but it seems like it would require a lot of custom elisp code, that I won't be able to provide.
What I have done in similar situations, is just use M-x sql-mode to put the whole buffer in sql-mode. This way all your SQL keywords will be highlighted and most everything else will remain the default text color. All your SQL code should stand out when you are scanning your log files (which I assume is your end goal).
I doing some formatting from copy/paste. When I copy a table from Word, and I want to insert it in my program, I need to edit the table formatting to show the info like I want.
When I copy from word I can view whats copy in clipboard magic:
Is there a way to get the formatting, or do I need to create a new table for scratch with the data listed in clipboard magic?
I Clipdiary the "copy" is read as HTML
This makes me wounder, is it possible to get the html code?
Yes, the HTML is present as CF_HTML. See reference on MSDN: http://msdn.microsoft.com/en-us/library/aa767917(v=vs.85).aspx
If you just want to SEE it, ClipMate has a Binary display that will show you a binary dump of the data. It's available in the trial version. If you don't see the Binary tab in the display window, turn it on in the Tools | Options | Editor dialog.
I'm quite new to cc-mode and I'd like to configure it to allow me to freely format and use tabs in multiline comments. This is important to me because I want to use cog.py in my source file and need to be able to format the python source in the comment correctly. I'd be ok with comments not beeing autoindented at all, however I'd like to keep auto indenting the rest of the source code.
Example:
...
/*
[[[cog
import cog
for x in ['a','b','c']:
>cog.outl(x)
]]]
*/
...
In the line marked with > I'd like to press TAB to indent the line. cc-mode simply does nothing at all if i do so. I could use spaces there (which is inconvenient) but every (semi-)automatic re-indentation of this block would cause the spaces to vanish and therefore the python code to be incorrectly indented (which is what happens if i happen to press tab somewhere on this line after indenting it with spaces).
I tried to start emacs without my .init to be sure this is default behavior and not modified by my configuration so far. I've done google searches and read the documentation of the cc-mode variables / functions I stumbled upon (cc-mode online docs) while searching for a solution (i.e. c-indent-comments-syntactically-p, c-indent-command, c-tab-always-indent,...) but none of these seemed to solve my question.
EDIT1:
Thanks to abo-abo's idea of a "multi-major-mode" setup i've stumbled upon mmm-mode and have set up automatic switching to python mode for a cog section, which fixes most of my problems.
The only remaining problem is reindenting the whole file or a region containing a cog section. Can I somehow tell cc-mode to not change anything in comments while reindenting the file? mmm-mode + that would be a perfect solution for me.
You can use M-i to force a tab indent on the lines that you want, so you can use it to indent your comments.
You can also change your comments to use // instead. Just select your python code snippet, and do M-x comment-region:
// def foo(x):
// print 'hi'
Then the autoindent won't mess up your indentation.
With BC2, when i click the Show differences... option in SourceGear Vault. It allow me to copy from the repository to the working version and save but I can't do this with BC3. It doesn't allow copying to the otherside (right) and have the editing disabled showing at the bottom of the BC3. It is even the same with DiffMerge. What am I not understanding here?
Can someone explain to me why the changes in BC3 and is there a workaround?
Beyond Compare will disable editing of a file for any of the following reasons:
It's one of the input files in a 3-way merge
The comparison was cancelled
The comparison encountered an error (corrupt file, invalid character encoding, out of memory, gamma rays, etc)
The file format's conversion settings don't support converting back to the original format (MS Word, PDF)
The file is on a read-only "filesystem" (7zip/RAR/CHM archives, CD/DVD-ROMs)
A file or parent folder had editing explicitly disabled by the user in the session settings or using the /ro command line switches
The viewer itself doesn't support editing (eg, Hex Compare prior to v4)
Also, the Full Edit (F2) toggle in the Text Compare View menu switches between inline editing and line-based mode. If it's disabled you can copy/delete whole lines and type in the line details edits at the bottom of the window, but the main windows won't have a cursor, typing is disabled, and it will always select whole lines. Unlike the above items, this doesn't show "Editing Disabled" in the status bar.
there must be a flag on the command line to call BC such as /ro# or /#ro or /(side)readonly (where side is left or right), it prevents editing.
these flags are there because differs are often called with temporary files to diff, in particular from SCC. and Vault probably has a single "external diff" command, thus you have to choose whether the flags are always there, it protects you from unexpectly editing a temporary file and loose this work when closing the diff tool, or not.
The few reasons I have found are:
If the encoding of the file is different than the default. In this case change the encoding to the expected one. (Japanese-ShiftJIS in my case)
If a refresh of files is in progress.