how do i put different headers on serten pages
for over a freakin month now i have ben trying to get libra office headers to do a few things. 1 stop putting the header from 1 place on every single other page. i want every header of every page to be different. or at least do something like first 5 page headers are named vengeance and the next aft…
header, footer and other page attributes are stored against “sections” and not individual pages. each section can be one page, several pages or the entire document. inserting a manual page break starts a new section. i am new to libreo and was also frustrated by its behaviour till the penny dropped …
use sections. the first page should be section 1. you can assign the master page elements to that section only. then all other pages will be in section 2, with a different master page with different elements. each section can pick up page numbering from the last or start at a new number. try this and try to modify accordingly -



```
<?
//content is the array of titles which comes from the content.php page or the entire code can be put in the content.php
$content = array('title1 - This is the Homepage','title2 -Find new friends','title3 - Get your visa cleared now','title4 - bark about your wife here','title5 - Dont have kids yet','some other page');

$arr = explode('/',$_SERVER['PHP_SELF']);

$current_page = $arr[count($arr)-1];
//list your pages here
$pages  = array("1=>index.php","2=>friends.php","3=>nicks.php","4=>rent.php","5=>test.php");
for($i = 0; $i<count($pages);$i++)
{
	if($pages[$i] == trim($current_page))
		$pages_index = $i;
	else $pages_index = 6;
}
//This will echo the title
echo $content[pages_index];
?>
```

ask,if you stuck up somewhere. [image] sgenter:

is there another way to zip off a chapter with the new version of bookdown? alternatively, how would i revert to the previous version?

this is a pretty specific use case and don't know yet about. so i don't think you can "zip" the way you want

[image] sgenter:

i do reali… edit this class:

.swiper-pagination

you can inspect and style it to be whatever you want with the command:

ionic serve as i had the time, thought i would tidy things up, just one custom query needed, no view required. just change the office names and copy/paste into a custom query 
have a great christmas party! 
select sum(office1) as office1,sum(office2) as office2,sum(office3) as office3,hours from 
((select 
cou… <p>a h1 tag is still the recommended way by w3 to headline a page:</p>
<p><a href="http://www.w3.org/qa/tips/use\_h1\_for\_title">http://www.w3.org/qa/tips/use\_h1\_for\_title</a></p>
<p><a href="http://www.w3.org/qa/tips/headings">http://www.w3.org/qa/tips/headings</a></p>
<p><a href="http://www.w3.org/tr/rec-html40/struct/global.html#h-7.5.5">http://www.w3.org/tr/rec-html40/struct/global.html#h-7.5.5</a></p>
<p>i still find that by following w3 recommendations it makes a good step in creating a well optimised page. obviously you aren't going to rank by having a h1 tag alone, but it will always never harm the page to have a well crafted one. one thing i do recommend is having a different h1 tag to the page title.</p> This depends a lot on what you mean by "revert".


Temporarily switch to a different commit



If you want to temporarily go back to it, fool around, then come back to where you are, all you have to do is check out the desired commit:



```
# This will detach your HEAD, that is, leave you with no branch checked out:
git checkout 0d1d7fc32

```

Or if you want to make commits while you're there, go ahead and make a new branch while you're at it:



```
git checkout -b old-state 0d1d7fc32

```

To go back to where you were, just check out the branch you were on again. (If you've made changes, as always when switching branches, you'll have to deal with them as appropriate. You could reset to throw them away; you could stash, checkout, stash pop to take them with you; you could commit them to a branch there if you want a branch there.)


Hard delete unpublished commits



If, on the other hand, you want to really get rid of everything you've done since then, there are two possibilities. One, if you haven't published any of these commits, simply reset:



```
# This will destroy any local modifications.
# Don't do it if you have uncommitted work you want to keep.
git reset --hard 0d1d7fc32

# Alternatively, if there's work to keep:
git stash
git reset --hard 0d1d7fc32
git stash pop
# This saves the modifications, then reapplies that patch after resetting.
# You could get merge conflicts, if you've modified things which were
# changed since the commit you reset to.

```

If you mess up, you've already thrown away your local changes, but you can at least get back to where you were before by resetting again.


Undo published commits with new commits



On the other hand, if you've published the work, you probably don't want to reset the branch, since that's effectively rewriting history. In that case, you could indeed revert the commits. With Git, revert has a very specific meaning: create a commit with the reverse patch to cancel it out. This way you don't rewrite any history.



```
# This will create three separate revert commits:
git revert a867b4af 25eee4ca 0766c053

# It also takes ranges. This will revert the last two commits:
git revert HEAD~2..HEAD

#Similarly, you can revert a range of commits using commit hashes (non inclusive of first hash):
git revert 0d1d7fc..a867b4a

# Reverting a merge commit
git revert -m 1 <merge_commit_sha>

# To get just one, you could use `rebase -i` to squash them afterwards
# Or, you could do it manually (be sure to do this at top level of the repo)
# get your index and work tree into the desired state, without changing HEAD:
git checkout 0d1d7fc32 .

# Then commit. Be sure and write a good message describing what you just did
git commit

```

The [`git-revert` manpage](https://schacon.github.com/git/git-revert.html) actually covers a lot of this in its description. Another useful link is [this git-scm.com section discussing git-revert](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging#_undoing_merges).


If you decide you didn't want to revert after all, you can revert the revert (as described here) or reset back to before the revert (see the previous section).


You may also find this answer helpful in this case:  

[How can I move HEAD back to a previous location? (Detached head) & Undo commits](https://ask4knowledgebase.com/questions/34519665/how-can-i-move-head-back-to-a-previous-locationdetached-headundo-commits) If all you want to change is a single file, do that and commit it.


Then you can use `git rebase -i` to rearrange commits. In particular, you can move the change to the license file to the beginning of history, as if it had always been there. have to be ready to change your mindset. then you must do new shit to distract you. 1. to connect ideas
2. due to
3. too and further
4. to keep the reader interested and to make the ideas clear
5. consequently