create table xyz_new as select * from xyz where rownum < 0;
In Oracle SQL Developer
- use the menu-function (maybe right-click) on the table you want to operate on (i.e. that you want to copy),
- “Table“,
- “Copy…“,
- w/o checking “Include Data“.
create table xyz_new as select * from xyz where rownum < 0;
In Oracle SQL Developer
kill-ring-save is actually remapped to *table--cell-kill-ring-saveThat “feature” (marking the buffer as changed) is terribly annoying!!! You try to copy (AKA kill-ring-save) text from a table, and from now on something “tells” you, you “changed” the table – but actually you did not. You may be tempted to think, saving a file is a cheap operation, but what if the file is actually located on a remote machine and you are operating on the file through tramp and you cannot reach the machine for a couple of hours?!!
Why not change the buffer to read-only and kill-ring-save than? if you try to kill-ring-save in read-only mode, emacs shouts at you:
apply: Buffer is read-only: #<buffer …>
But yes, although emacs shouted at you, you succeeded copying the text in question to the kill-ring, and now you can paste it into wherever you want.
Rendering an emacs table as HTML table, possible for further intermediate processing – like splitting … – quite useful!
So far I have always printed an emacs table as fixed-font text document – sort of ugly, but still useful.
I find it very useful and necessary to know immediately, that a table got recognised by emacs as such. Emacs shows it in colours then.
With the default settings I find the background blue1 (together with foreground gray90) sometimes / often “far too heavy”, let’s say: a contrast far too exhausting for my eyes. Really!
But what is a “less heavy” pair of foreground / background settings for table-cell? “For the time being” I am using plain “black” for the background through emacs customisation (“table-cell” in my “custom-file“).
The StackExchange article explains you everything, you need to know, and also points you to the related customisation buffer.
| foreground | background | |
| default | black | |
| “light grey” | “dark blue” | |
| 2019-08-27: too difficult | snow1 | gray70 |
| 2019-08-27: works | black | white |
| 2019-08-27: works | tomato | white |
I know, there is a shortcut for “Save Draft” in “basic mode” (Accesskey D) – but my preferred mode is “dynamic mode” – and Accesskey D does something else in Chrome on the Mac – it deletes a character on the right side of the text cursor.
In file editors I save the current state using a keyboard shortcut, in horde I can not do that, that’s a pity – it’s quite important for me – every now and then horde logs me out and I loose the e-mail I have been writing.
At least there is an advanced feature to get drafts auto-saved every minute.
What a surprise! I would have liked to use that functionality for a long, long time – not only in the context of a file under VC. How often did my symlinks get disconnected erroneously / accidentally from their link targets?
Why didn’t I know of such a basic and useful feature for so many years???
I enjoyed a few very delicious sweet ones, that got prepared by the late Konstantin Münz.
MediaWiki lets me do that, GitLab does not.
If you switch back and forth between several tasks, sometimes you need a tool showing you the differences between the original text (you started with) and your current text.
If I try to abandon such an editor window (resp. browser tab), MediaWiki asks me, whether I really want to do so. I like that very much.