Features that i miss in Sigil

[DiapDealer]

Version of Sigil, please?

[KevinH]

As sigil's user's guide explains:

Sigil's has an Insert->Closing Tag menu.

In Sigil's Preferences you can assign it a shortcut key sequence.
So instead of typing "</" you just use the key sequence you assigned at the same point.

Originally Posted by abraum

what menu? what i mean is when i have this code

<h1>text

and i enter '</' at the end of the line calibre completes this to '</h1> automatically. i like this very much.

[phillipgessert]

Sigil’s ability to launch an external editor is also really useful for stuff like this. Anytime I find myself wishing Sigil had some feature found in a dedicated text editor/IDE, I remind myself that’s probably the exact reason the feature exists. I use it anytime I want multicursor, for example. Glad for this topic though as I hadn’t realized Sigil had this closing tag feature.

[KevinH]

Originally Posted by phillipgessert

Sigil’s ability to launch an external editor is also really useful for stuff like this. Anytime I find myself wishing Sigil had some feature found in a dedicated text editor/IDE, I remind myself that’s probably the exact reason the feature exists. I use it anytime I want multicursor, for example. Glad for this topic though as I hadn’t realized Sigil had this closing tag feature.

It is smart enough to properly handle nested tags as well.

Kevin

[phillipgessert]

Originally Posted by KevinH

It is smart enough to properly handle nested tags as well.

Kevin

That’ll come in handy! And come to think of it, assigning some arbitrary shortcut seems less error-prone than the usual autocomplete approach. I’ve definitely gone into autopilot and wound up with more </div>div>s than I care to admit.

[Tex2002ans]

Originally Posted by phillipgessert

That’ll come in handy! And come to think of it, assigning some arbitrary shortcut seems less error-prone than the usual autocomplete approach. I’ve definitely gone into autopilot and wound up with more </div>div>s than I care to admit.

I hate the auto-closing tag while typing. My brain/fingers are already miles ahead, and then I only notice the broken </div>div> while skimming, running epubcheck, or Prettifying and thinking: "wtf happened here?".

Which reminds me, it's frustrated me for so long in Calibre's Editor, I finally decided to do something about it.

In Calibre, the setting is in:

Edit > Preferences > Editor Settings > "Auto close tags while typing </"

Now that I've unchecked it, I'll be at peace!

Note: The auto-close in Calibre is helpful though in the one case of trying to debug seriously nested spaghetti code.

I sometimes click deep between the mess, then type "</" to try to spot what dang tag wasn't closed (and then easy to click inside + see opening tag by the highlight tag feature).

[BetterRed]

Originally Posted by abraum

. . .
i don't use windows, i use linux. there is no anti-virus or firewall or backup software running in background. i only use calibre editor and not calibre library. i open all books with the "open with" menu of the file manager in sigil or calibre editor.

On your linux system, where do the calibre editor and Sigil unpack the epub?

BR

[abraum]

Originally Posted by BetterRed

On your linux system, where do the calibre editor and Sigil unpack the epub?

it /tmp and /tmp is on the same ssd where the linux is booting.

Originally Posted by DiapDealer

Version of Sigil, please?

its 1.6

Originally Posted by KevinH

Sigil's has an Insert->Closing Tag menu.

this works. i'll test it in "normal work".

[BetterRed]

Originally Posted by BetterRed

On your linux system, where do the calibre editor and Sigil unpack the epub?

Originally Posted by abraum

it /tmp and /tmp is on the same ssd where the linux is booting.

Interesting - on Windows the calibre editor keeps its working copy of the unpacked EPUB files in a directory named Cache in its Configuration folder, and it uses the equivalent of /tmp to interoperate with external editors invoked via its Open With. The linux version must use a different mechanism to prevent data loss if the two editors make changes to the same file concurrently.

BR

[Notjohn]

>Saving a file is never slow on my system

Instantaneous, it seems to me!