Lines Matching refs:we
85 " When gui colors are not supported, we can only guess the colors.
238 " For inverse, we always must set both colors (and exchange them)
277 " Use a different function for formatting based on user options. This way we
288 " first, get the style names we need
298 " Add normal groups and diff groups to separate lists so we can order them to
302 " (always succeeds because we pre-populate it)
381 " use strwidth, because we care only about how many character boxes are
382 " needed to size the input, we don't care how many characters (including
442 " create the function we built line by line above
503 " always be non-zero, however we don't want to use the <input> because that
584 " create the function we built line by line above
629 " For inverse, we always must set both colors (and exchange them)
705 " installed in a package or something, then we can extract the version from the
707 " is assembling their runtime piecemeal and we have no idea what versions of
781 " set the fileencoding to match the charset we'll be using
853 " if we are doing hover_unfold, use css 2 with css 1 fallback for IE6
873 " TODO: IE6 is REALLY old and I can't even test it anymore. Maybe we
892 " if we aren't doing hover_unfold, use CSS 1 only
907 " else we aren't doing any dynamic folding, no need for any special rules
982 \ " * we corrected the raw number to a line ID.",
1008 " if we're not using CSS we use a font tag which can't have a div inside
1180 " if we were making a general-purpose progress bar, we'd need to limit to a
1181 " lower limit as well, but since we always increment with a positive value
1182 " in this script, we only need limit the upper value
1188 " to process folds we make two passes through each line
1196 " so we don't accidentally start within a closed fold or something.
1202 " save the fold text and set it to the default so we can find fold levels
1206 " we will set the foldcolumn in the html to the greater of the maximum fold
1220 " open the fold so we can find any contained folds
1238 " the originally open folds will be all folds we encounter that aren't
1247 " only add the fold if we don't already have it
1252 " open the fold so we can find any contained folds
1266 " sort the folds so that we only ever need to look at the first item in the
1273 " close all folds again so we can get the fold text as we go
1276 " Go through and remove folds we don't need to (or cannot) process in the
1279 " If a fold is removed which contains other folds, which are included, we need
1283 " Note any time we remove a fold, either all of the included folds are in it,
1284 " or none of them, because we only remove a fold if neither its start nor its
1293 " range, we need to include it. Make it start on the first converted
1306 " If the entire fold lies outside the range we need to remove it.
1317 " if there is no first line we default to the first line in the buffer so
1319 " If however the entire fold lies outside the range we need to remove it.
1333 " if we've removed folds containing the conversion range from processing,
1334 " getting foldtext as we go won't know to open the removed folds, so the
1391 " If keeping tabs, add them to printable characters so we keep them when
1491 " Note that dynamic folds require using css so we just use css to take
1504 " If this is not the last fold we're opening on this line, we need
1506 " hover. If it is the last fold to open in the line, we shouldn't hide
1513 " only add extra blank space if we aren't opening another fold on the
1539 " open the fold now that we have the fold text to allow retrieval of
1548 " Note that dynamic folds require using css so we just use css to take
1584 " most of the time we won't use the diff_id, initialize to zero
1595 " Go along till we find a change in the match sequence number (ending
1604 " Go along till we find a change in hlID
1619 " Go along till we find a change in synID
1643 " immediately preceding the tab, so we can then look up the
1648 " processed, we need to get the character prior to the text,
1658 " find the tabstop interval to use for the tab we just found. Keep
1659 " adding tabstops (which could be variable) until we would exceed
1747 " Now, when we finally know which, we define the colors and styles
1772 " if we use any input elements for unselectable content, make sure they look
1805 \ ' "content:" with custom content, so we *want* the check to fail */',