Note that there are some explanatory texts on larger screens.

plurals
  1. USpeterph
    primarykey
    data
    text
    plurals
    1. COI'd be rather sceptical about summing the lengths "manually", you'd have to take care about padding/margins/borders, and it would probably derail completely on a `position` property (if it appeared there, of course). Letting the layout engine do the reflow seems more straightforward, complete and less error prone. For separate elements in the div you might try to play with CSS `display` property instead of taking moving elements around.
      singulars
    2. CO@Hossein depends on whether you want to purge it from the history or not. If not, then just deleting the file on next commit will probably be better. If you want to remove it from the whole history, because e.g. you had some private data inside (like passwords), you're probably out of luck anyway if someone already fetched your commits - see this [Mercurial FAQ](http://mercurial.selenic.com/wiki/FAQ#FAQ.2FCommonProblems.I_committed_a_change_containing_nuclear_launch_codes.2C_how_do_I_delete_it_permanently.3F) which applies to all DVCSs.
      singulars
    3. COIf you end up using `expect`, please remember that it will have security implications: either you store the root password in the script and you should therefore do your best to make the script unreadable for anyone except you, or you will be giving the password as command line argument in which case it might show clearly in the list of running processes (I'm not sure how MacOS handles this but on many UNICes this is the mode of operation).
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload