Wide hat is not above character [on hold]Insert `hfill` after each character“Same as above”...
What is brightness?
How to kill a localhost:8080
Is there a way to find out the age of climbing ropes?
Has Wakanda ever accepted refugees?
Why doesn't "adolescent" take any articles in "listen to adolescent agonising"?
Ahoy, Ye Traveler!
Deal the cards to the players
Can a Trickery Domain cleric cast a spell through the Invoke Duplicity clone while inside a Forcecage?
What kind of inflection is occuring in passive vb + かかった?
How can I be pwned if I'm not registered on the compromised site?
Is every open circuit a capacitor?
Why can't we use freedom of speech and expression to incite people to rebel against government?
Did Amazon pay $0 in taxes last year?
An Undercover Army
“I had a flat in the centre of town, but I didn’t like living there, so …”
What is the meaning of "notice to quit at once" and "Lotty points”
Why are special aircraft used for the carriers in the United States Navy?
Where is this quote about overcoming the impossible said in "Interstellar"?
Misplaced tyre lever - alternatives?
Caulking a corner instead of taping with joint compound?
Book about a time-travel war fought by computers
If nine coins are tossed, what is the probability that the number of heads is even?
What is better: yes / no radio, or simple checkbox?
How do I deal with being envious of my own players?
Wide hat is not above character [on hold]
Insert `hfill` after each character“Same as above” representationone character macrosUTF-8 (but not in current font) character in newcommandPutting hat over first character of subscripted variableCommand which replaces all occurrences of a certain character with another character?A more elegant version of the ifnot macroRotate the hat by 180 degreePassing next character to commandisdefempty not working for multiple macros
I've setup a new command VH
to specify a bold vector with a wide hat above it. Below is the code
documentclass{article}
usepackage{geometry}
geometry{
a4paper,
margin=20mm,
}
usepackage{bm}
usepackage{amsmath}
newcommand{VH}[1]{mathbf{widehat{#1}}}
begin{document}
section*{Question 1}
This is a vector $VH{d}=10$
end{document}
Here is what is looks like when rendered:
When I'm looking for
macros
put on hold as off-topic by JouleV, Mico, Steven B. Segletes, Phelype Oleinik, Kurt 22 hours ago
- This question does not fall within the scope of TeX, LaTeX or related typesetting systems as defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.
|
show 1 more comment
I've setup a new command VH
to specify a bold vector with a wide hat above it. Below is the code
documentclass{article}
usepackage{geometry}
geometry{
a4paper,
margin=20mm,
}
usepackage{bm}
usepackage{amsmath}
newcommand{VH}[1]{mathbf{widehat{#1}}}
begin{document}
section*{Question 1}
This is a vector $VH{d}=10$
end{document}
Here is what is looks like when rendered:
When I'm looking for
macros
put on hold as off-topic by JouleV, Mico, Steven B. Segletes, Phelype Oleinik, Kurt 22 hours ago
- This question does not fall within the scope of TeX, LaTeX or related typesetting systems as defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.
3
I get the proper output from your MWE.
– Steven B. Segletes
22 hours ago
Ok, I've been using Overleaf. The output I cut and pasted from the preview window, but if I go to download the PDF, it shows the correct result. So, this must be an overleaf problem then...
– whitelined
22 hours ago
2
Off-topic: I think the expressionnewcommand{VH}[1]{mathbf{widehat{#1}}}
doesn't look quite right from a syntactic point of view; I thinknewcommand{VH}[1]{widehat{mathbf{#1}}}
looks more natural. Why? Becausemathbf
affects only#1
, but not the appearance ofwidehat
.
– Mico
22 hours ago
6
I'm voting to close this question as off-topic because it is an Overleaf issue. You should contact the Overleaf staff for this. (Btw I also get your wrong result when I use Overleaf.)
– JouleV
22 hours ago
3
(I'm on support staff at Overleaf.) While this has been closed as off-topic, I want to add a comment here for anyone who may find this question while searching. We know about this problem and our developers are working on a fix. The problem is specific to Chrome 72 and newer. In the meantime, the PDF download is still rendered correctly, and other browsers are also working. You can also work around this by switching to the "native" PDF previewer in the project settings menu, or using the XeLaTeX compiler. Sorry about the inconvenience while we look into a fix for this.
– Paul Gessler
21 hours ago
|
show 1 more comment
I've setup a new command VH
to specify a bold vector with a wide hat above it. Below is the code
documentclass{article}
usepackage{geometry}
geometry{
a4paper,
margin=20mm,
}
usepackage{bm}
usepackage{amsmath}
newcommand{VH}[1]{mathbf{widehat{#1}}}
begin{document}
section*{Question 1}
This is a vector $VH{d}=10$
end{document}
Here is what is looks like when rendered:
When I'm looking for
macros
I've setup a new command VH
to specify a bold vector with a wide hat above it. Below is the code
documentclass{article}
usepackage{geometry}
geometry{
a4paper,
margin=20mm,
}
usepackage{bm}
usepackage{amsmath}
newcommand{VH}[1]{mathbf{widehat{#1}}}
begin{document}
section*{Question 1}
This is a vector $VH{d}=10$
end{document}
Here is what is looks like when rendered:
When I'm looking for
macros
macros
asked 23 hours ago
whitelinedwhitelined
273
273
put on hold as off-topic by JouleV, Mico, Steven B. Segletes, Phelype Oleinik, Kurt 22 hours ago
- This question does not fall within the scope of TeX, LaTeX or related typesetting systems as defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as off-topic by JouleV, Mico, Steven B. Segletes, Phelype Oleinik, Kurt 22 hours ago
- This question does not fall within the scope of TeX, LaTeX or related typesetting systems as defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.
3
I get the proper output from your MWE.
– Steven B. Segletes
22 hours ago
Ok, I've been using Overleaf. The output I cut and pasted from the preview window, but if I go to download the PDF, it shows the correct result. So, this must be an overleaf problem then...
– whitelined
22 hours ago
2
Off-topic: I think the expressionnewcommand{VH}[1]{mathbf{widehat{#1}}}
doesn't look quite right from a syntactic point of view; I thinknewcommand{VH}[1]{widehat{mathbf{#1}}}
looks more natural. Why? Becausemathbf
affects only#1
, but not the appearance ofwidehat
.
– Mico
22 hours ago
6
I'm voting to close this question as off-topic because it is an Overleaf issue. You should contact the Overleaf staff for this. (Btw I also get your wrong result when I use Overleaf.)
– JouleV
22 hours ago
3
(I'm on support staff at Overleaf.) While this has been closed as off-topic, I want to add a comment here for anyone who may find this question while searching. We know about this problem and our developers are working on a fix. The problem is specific to Chrome 72 and newer. In the meantime, the PDF download is still rendered correctly, and other browsers are also working. You can also work around this by switching to the "native" PDF previewer in the project settings menu, or using the XeLaTeX compiler. Sorry about the inconvenience while we look into a fix for this.
– Paul Gessler
21 hours ago
|
show 1 more comment
3
I get the proper output from your MWE.
– Steven B. Segletes
22 hours ago
Ok, I've been using Overleaf. The output I cut and pasted from the preview window, but if I go to download the PDF, it shows the correct result. So, this must be an overleaf problem then...
– whitelined
22 hours ago
2
Off-topic: I think the expressionnewcommand{VH}[1]{mathbf{widehat{#1}}}
doesn't look quite right from a syntactic point of view; I thinknewcommand{VH}[1]{widehat{mathbf{#1}}}
looks more natural. Why? Becausemathbf
affects only#1
, but not the appearance ofwidehat
.
– Mico
22 hours ago
6
I'm voting to close this question as off-topic because it is an Overleaf issue. You should contact the Overleaf staff for this. (Btw I also get your wrong result when I use Overleaf.)
– JouleV
22 hours ago
3
(I'm on support staff at Overleaf.) While this has been closed as off-topic, I want to add a comment here for anyone who may find this question while searching. We know about this problem and our developers are working on a fix. The problem is specific to Chrome 72 and newer. In the meantime, the PDF download is still rendered correctly, and other browsers are also working. You can also work around this by switching to the "native" PDF previewer in the project settings menu, or using the XeLaTeX compiler. Sorry about the inconvenience while we look into a fix for this.
– Paul Gessler
21 hours ago
3
3
I get the proper output from your MWE.
– Steven B. Segletes
22 hours ago
I get the proper output from your MWE.
– Steven B. Segletes
22 hours ago
Ok, I've been using Overleaf. The output I cut and pasted from the preview window, but if I go to download the PDF, it shows the correct result. So, this must be an overleaf problem then...
– whitelined
22 hours ago
Ok, I've been using Overleaf. The output I cut and pasted from the preview window, but if I go to download the PDF, it shows the correct result. So, this must be an overleaf problem then...
– whitelined
22 hours ago
2
2
Off-topic: I think the expression
newcommand{VH}[1]{mathbf{widehat{#1}}}
doesn't look quite right from a syntactic point of view; I think newcommand{VH}[1]{widehat{mathbf{#1}}}
looks more natural. Why? Because mathbf
affects only #1
, but not the appearance of widehat
.– Mico
22 hours ago
Off-topic: I think the expression
newcommand{VH}[1]{mathbf{widehat{#1}}}
doesn't look quite right from a syntactic point of view; I think newcommand{VH}[1]{widehat{mathbf{#1}}}
looks more natural. Why? Because mathbf
affects only #1
, but not the appearance of widehat
.– Mico
22 hours ago
6
6
I'm voting to close this question as off-topic because it is an Overleaf issue. You should contact the Overleaf staff for this. (Btw I also get your wrong result when I use Overleaf.)
– JouleV
22 hours ago
I'm voting to close this question as off-topic because it is an Overleaf issue. You should contact the Overleaf staff for this. (Btw I also get your wrong result when I use Overleaf.)
– JouleV
22 hours ago
3
3
(I'm on support staff at Overleaf.) While this has been closed as off-topic, I want to add a comment here for anyone who may find this question while searching. We know about this problem and our developers are working on a fix. The problem is specific to Chrome 72 and newer. In the meantime, the PDF download is still rendered correctly, and other browsers are also working. You can also work around this by switching to the "native" PDF previewer in the project settings menu, or using the XeLaTeX compiler. Sorry about the inconvenience while we look into a fix for this.
– Paul Gessler
21 hours ago
(I'm on support staff at Overleaf.) While this has been closed as off-topic, I want to add a comment here for anyone who may find this question while searching. We know about this problem and our developers are working on a fix. The problem is specific to Chrome 72 and newer. In the meantime, the PDF download is still rendered correctly, and other browsers are also working. You can also work around this by switching to the "native" PDF previewer in the project settings menu, or using the XeLaTeX compiler. Sorry about the inconvenience while we look into a fix for this.
– Paul Gessler
21 hours ago
|
show 1 more comment
0
active
oldest
votes
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
3
I get the proper output from your MWE.
– Steven B. Segletes
22 hours ago
Ok, I've been using Overleaf. The output I cut and pasted from the preview window, but if I go to download the PDF, it shows the correct result. So, this must be an overleaf problem then...
– whitelined
22 hours ago
2
Off-topic: I think the expression
newcommand{VH}[1]{mathbf{widehat{#1}}}
doesn't look quite right from a syntactic point of view; I thinknewcommand{VH}[1]{widehat{mathbf{#1}}}
looks more natural. Why? Becausemathbf
affects only#1
, but not the appearance ofwidehat
.– Mico
22 hours ago
6
I'm voting to close this question as off-topic because it is an Overleaf issue. You should contact the Overleaf staff for this. (Btw I also get your wrong result when I use Overleaf.)
– JouleV
22 hours ago
3
(I'm on support staff at Overleaf.) While this has been closed as off-topic, I want to add a comment here for anyone who may find this question while searching. We know about this problem and our developers are working on a fix. The problem is specific to Chrome 72 and newer. In the meantime, the PDF download is still rendered correctly, and other browsers are also working. You can also work around this by switching to the "native" PDF previewer in the project settings menu, or using the XeLaTeX compiler. Sorry about the inconvenience while we look into a fix for this.
– Paul Gessler
21 hours ago