I am using the glossaries package and wonder if it is possible to customize the appearance of the output. For example I want to make the spaces between the entries smaller or changing the style of the page and line numbers (from 6-20 to 6.20). There is nothing to be found in the manual on such things.
In the header I have:
\usepackage{glossaries}
\makenoidxglossaries
\newglossaryentry{entry}{name={entry},description={Bla Bla Bla}}
and in the document I am using:
bla bla \edgls{entry} bla bla
It is possible to set the appearance via \setglossarystyle{<style>} But I would like to change the spacing by hand.
There are some good answers here on spacing and glossary style and more documentation on the glossaries package and usage here.
The pagestyle and linespacing are not controlled by the glossaries, that is dependent on what you have those set to separately.
Related
I am writing a man page. I am displaying only with man -l filename.man.
I am running into an issue where my text is displaying as:
file/path/[ option ]
Where I would like it to display as:
file/path/[option].
The offending lines of text (code?) look like:
.\" filename.man
The filepath is /file/path/[
.I option
], and it contains files.
I am extremely new to formatting with [gnt]roff, and appreciate any pointers or recommended readings.
A definite guide to groff is gnu.org. I recommend the pdf for easy searching. It includes chapter 5.17.1 Changing Fonts that explains \f. Note there are at least 2 alternatives. The first uses \c to stop further output at the end of a line:
The filepath is /file/path/[\c
.I option\c
], and it contains files.
but the following is the preferred method, using a macro RI (roman-italic) provided specially for the purpose of joining "words" in an alternating roman then italic font:
The filepath is
.RI /file/path/[ option ],
and it contains files.
See the pdf chapter 4.1.3 Macros to set fonts, or the man page for groff_man (the man macros, also at gnu.org)
This can be achieved using the \fI <text> \fR in line style tags in place of the .I tags at the start of the line. In your code,
.\" filename.man
The filepath is /file/path/[\fIoption\fR], and it contains files.
I don't know why, and would appreciate comments or edits explaining the difference or linking to useful documentation.
So basically I am trying to rewrite a bash script which uses dialog --radiolist for choosing locale,keyboard,time. At the moment the tag is a number that corresponds to a local (I created a hashtable for it). But because I have, and want to keep it that way for now, around 100 locales it gets messy at the end.
What I wanna achieve is to make it more compact without having to add or add an artificial, non visible item that might easily translate to its tag. (as a tag I would put the locale name)
What I have tried:
1. Noobish thing but I though that there might be some way to include empty like NULL in ASCII or 0, blank space etc, but dialog would always make it visible.
2. Exclude the item at all and finish on on/off but instead on/off takes place of item (not surprisingly if options are as follow --radiolist text height width list-height [ tag item status ])
3. Instead of letting the dialog on exit write to the output the name of the chosen locale I created an output statement myself.
I had red a lot about dialog and whiptail(http://linux.die.net/man/1/dialog, http://linuxcommand.org/lc3_adv_dialog.php) but always end up with having to add tag and an item. Would appreciate any suggestions and maybe some info if there is easily plug-gable dialog/whiptail compatible libs.
Thank You in advance
Perhaps you overlooked the --no-tags option (see manpage):
--no-tags
Some widgets (checklist, inputmenu, radiolist, menu) display a
list with two columns (a "tag" and "description"). The tag is
useful for scripting, but may not help the user. The --no-tags
option (from Xdialog) may be used to suppress the column of tags
from the display. Unlike the --no-items option, this does not
affect the data which is read from the script.
The question mentions whiptail and consistency, which could refer to consistency across dialog and whiptail. There is none, since
whiptail provides fewer options than dialog (inevitably, there will be differences, since there is no one-one mapping possible)
consistency as such between the two is done in dialog occasionally to help with compatibility (the reverse is not true).
I am using the markdown editor and I have loaded Mathjax in all pages of my website.
I have realized that this line of latex works well:
$(u_1)$
However, this one does not work (basically latex does not work):
$(u_1,u_2)$
In order to make this work, I have to write something like this:
$(u\_1,u\_2)$
I have a similar problem here. This does not work:
$$M=\left(\begin{array}{cc}
a & b \\
c & d \\
\end{array}\right)$$
But this works:
$$M=\left(\begin{array}{cc}
a & b \\\\
c & d \\\\
\end{array}\right)$$
This is a common issue of mixing LaTeX-input with Markdown. From the MathJax documentation:
There cannot be HTML tags within the math delimiters (other than <br>) as TeX-formatted math does not include HTML tags.
And later:
Another source of difficulty is when MathJax is used in content management systems that have their own document processing commands that are interpreted before the HTML page is created. For example, many blogs and wikis use formats like Markdown to allow you to create the content of you pages. In Markdown, the underscore is used to indicate italics, and this usage will conflict with MathJax’s use of the underscore to indicate a subscript. Since Markdown is applied to the page first, it will convert your subscripts markers into italics (inserting tags into your mathematics, which will cause MathJax to ignore the math).
As other answers on SO (see the link at the top) point out, some markdown parsers are more aware of TeX-like syntax than others.
When I type sup then TAB in Sublime Text 3, I get <sup>. That isn't what I want; I only want tab completions based on what is in my current file.
How can I limit tag style tag-completions to just HTML files?
I was hoping to find a setting called tag_complete_file_extensions or similar.
I don't currently understand the implications of these default preference settings, but they don't look like what I want:
{
// Controls what scopes auto complete will be triggered in
"auto_complete_selector": "source - comment, meta.tag - punctuation.definition.tag.begin",
// Additional situations to trigger auto complete
"auto_complete_triggers": [ {"selector": "text.html", "characters": "<"} ],
}
At the least, I'd appreciate an answer pointing me in the right direction. I don't mind forking a package or writing some custom code.
I believe this behaviour is provided by the Emmet (formerly ZenCoding), or similar package and not sublime directly.
Are you sure syntax is set accordingly for the files you get html tag completion?
By default Emmet detects that you are working on html files and enables tag completion (in my case I did not have to configure anything to get this functionality). You should have a closer look at your packages and your configuration and possibly update existing ones.
If you need any further help with the configuration files, I'm happy to help!
Cheers!
My thesis is written in b5j documentclass style.
\documentclass[b5j,twoside,12pt]{report}
I have a paper that is appended at the end. However this is written in b5paper style as an article.
\documentclass[12pt,b5paper,twoside]{article}
How do I get the paper to follow the japanese style? Havent found any b5paperj options in the geometry package.. :-/
It is possible to build the paper that must be appended separately and input it in your document using pdfpages. This way you don't have to control both styles and the package provides enough flexibility to make it look like you want to.