How to reset “Replace Toner” warning on Brother MFC-L2710DW Printer and print ~100 more pages without replacing the toner!
Open the front cover.
Press Clear and Stop/Exit button simultaneously and press Clear button once.
It will show the following on the display:
Reset Menu
K.TNR-STR
Press UP arrow once. It will show “K.TNR-HC”. Press OK.
Press UP arrow for reset.
Close the cover. DONE!
NOW ENJOY!
What's harder than choosing a variable name? IMO its composing a perfect code comment and commit message. Today we will discuss some bad commit messages, why they are bad and what we can do to improve those?
You made all the code updates, wrote tests and now its time to commit them with a commit message. Is "Code Updated" a sufficient? What about "Issue fixed"? Just imagine yourself reading the commit message some time later. Just like code comment, commit message should add context about why the code update was necessary?
A good commit message helps a future developer(it might be you) to reestablish the context around a piece of code whenever the developer needs to dig through the history to find out why the code was changed. It also helps the code reviewer to what to expect on the code.
Unless your team follows squash merge (where all the individual commits in the PR are combined and the person merging the PR can put a single/meaningful commit message) you should pay extra attention when choosing. Commit messages like the following add no value. A good developer should never write these kind of commit messages.
"Issue fix" doesn't indicate which issue number and what was the cause of issue? "Logic updated" is super obvious and serves no purpose. "updated dialog box UI" doesn't indicate which dialog box and why it was updated. "added import function" doesn't indicate which data type does it import?
All the code changes should be followed by a Jira/Story created by someone. Noone should just go ahead and make a arbitrary code change. Most of the git providers (github, bitbucket, gitlab etc) support hyperlinking of Jira/Issue number from commit message. eg: UI_APP:4555 Fixed broken button on IE9 caused by unsupported JS function
Its good to do a new commit per logical change. eg: do a commit once the functional piece is working:
For bigger update, use a heading and bullet points. The header can be short.
Imagine you are working on a BIG feature where you modified several files. At some point you are able to make few things working (point X). But when you work on additional changes the things that worked earlier started breaking. Later you are in a position where you don't know how to revert the new changes to get back to the point X where few things were function. If you had committed your changes at point X, it would have made it super easy to revert local changes to that point.
How to delete merged branches from local copy:
When you work on a project for a while, there is a good chance that you will have a list of old/already merged branches showing on your local git.
When you run $git branch it will show all the branches since you started working on the project including the ones that are not currently active.
$git branch
PROJX-1024-add-new-button
PROJX-1026-add-another-button
PROJX-1027-titleupdates
build-fix
develop
release
master
Here's how you can find the merged branches: It will only list a branch if it exists in local but not in remote(deleted from remote after merging).
$git branch --merged
PROJX-1024-add-new-button
build-fix
develop
release
$git branch --merged | egrep -v "(^\*|develop|release)" | xargs git branch -d
You can add any number of branches to the skip list separated by pipe |
$git branch --merged | egrep -v "(^\*|develop|release|another_branch|yet_another_branch)" | xargs git branch -d
<catalog>
<book id="001" lang="ENG">
..
</book>
<book id="002" lang="ENG">
..
</book>
...
</catalog> <book id="001" lang="ENG">
..
</book>
<book id="002" lang="ENG">
..
</book>
<book id="003" lang="ENG">
..
</book>
<book id="004" lang="ENG">
..
</book> MIN : [ Textbox ]
MAX: [ Textbox ]
User Guess [ Textbox ]
[ Play ]
eg:
DATE_TIME, WINNER, WINNING_NUM, LOSING_NUM
2020-05-10 20:01:50, USER, 5, 10
2020-05-10 20:02:50, USER, 3, 4
2020-05-11 20:05:50, COMPUTER, 7, 9
GUI mockup:
User A's Guess [ Text Box ]
User B's Guess [ Text Box ]
[ PLAY ]
int a = read()
int b = 1000
if(a > 18 && b > 50)
println("Entry allowed")
int age = readMemberAge()
int balance = 1000
if(age > 18 && balance > 50)
println("Entry allowed")
DB.allRecords().read().toCsv("file.csv");
 |
| Hyper-V not compatible - VMWare Error |
options: {
proxy: "local.server-URL"
}
module.exports = function(grunt) {
// Task configuration will go here
grunt.initConfig({
watch: {
},
browserSync: {
bsFiles: {
src: [
"css/*.css", "js/.js", "./*.html" //search file/folders
]
},
options: {
proxy: "local.server-URL" // NEEDS TO BE CONFIGURED
}
}
});
// Load tasks dependencies
grunt.loadNpmTasks('grunt-contrib-watch');
grunt.loadNpmTasks('grunt-browser-sync');
// Setup default task
// both browserSync and watch will run when running >grunt command
grunt.registerTask('default', ['browserSync', 'watch']);
};
 |
| Enabling Annotation Processing on IntelliJ IDEA |
Ynaxdh in Yeoman generator| Git task | Notes | Git commands |
|---|---|---|
| Tell Git who you are | Configure the author name and email address to be used with your commits.Note that Git strips some characters (for example trailing periods) from user.name. | git config --global user.name "Sam Smith" git config --global user.email sam@example.com |
| Create a new local repository | git init | |
| Check out a repository | Create a working copy of a local repository: | git clone /path/to/repository |
| For a remote server, use: | git clone username@host:/path/to/repository | |
| Add files | Add one or more files to staging (index): | git add <filename>git add * |
| Commit | Commit changes to head (but not yet to the remote repository): | git commit -m "Commit message" |
| Commit any files you've added with git add, and also commit any files you've changed since then: | git commit -a | |
| Push | Send changes to the master branch of your remote repository: | git push origin master |
| Status | List the files you've changed and those you still need to add or commit: | git status |
| Connect to a remote repository | If you haven't connected your local repository to a remote server, add the server to be able to push to it: | git remote add origin <server> |
| List all currently configured remote repositories: | git remote -v | |
| Branches | Create a new branch and switch to it: | git checkout -b <branchname> |
| Switch from one branch to another: | git checkout <branchname> | |
| List all the branches in your repo, and also tell you what branch you're currently in: | git branch | |
| Delete the feature branch: | git branch -d <branchname> | |
| Push the branch to your remote repository, so others can use it: | git push origin <branchname> | |
| Push all branches to your remote repository: | git push --all origin | |
| Delete a branch on your remote repository: | git push origin :<branchname> | |
| Update from the remote repository | Fetch and merge changes on the remote server to your working directory: | git pull |
| To merge a different branch into your active branch: | git merge <branchname> | |
| View all the merge conflicts:View the conflicts against the base file:Preview changes, before merging: | git diffgit diff --base <filename> git diff <sourcebranch> <targetbranch> |
|
| After you have manually resolved any conflicts, you mark the changed file: | git add <filename> | |
| Tags | You can use tagging to mark a significant changeset, such as a release: | git tag 1.0.0 <commitID> |
| CommitId is the leading characters of the changeset ID, up to 10, but must be unique. Get the ID using: | git log | |
| Push all tags to remote repository: | git push --tags origin | |
| Undo local changes | If you mess up, you can replace the changes in your working tree with the last content in head:Changes already added to the index, as well as new files, will be kept. | git checkout -- <filename> |
| Instead, to drop all your local changes and commits, fetch the latest history from the server and point your local master branch at it, do this: | git fetch origingit reset --hard origin/master | |
| Search | Search the working directory for foo(): | git grep "foo()" |
find command is one of the most important and much used command in Linux systems. find
command is used to search and locate list of files and directories
based on conditions you specify for files that match the arguments. In
this article we will get familier with linux find command.
First things first, to get more knowledge on any linux command we can use linux manual page using man <command_name>. For more information about find you can use man find and you'll get in depth description on how we can use linux command.
Basic use of find looks somewhat like below
find .Let's get familier which the syntax of find. In above example we have two parts
find : find is the command itself. : . (dot) represents the path from where
we want to search. We can pass any path here and find will start to
look from the path what was provided.If you run the command, you will get list of all the files and directories that is inside the path that was given as argument.
But I assume you don't want to search for all files. You may want to search for file from / directories that has specific name. To seach for specific file / directories we can use -name option. Here's an example of find which search for the file / directories with the name .gitignore
find . -name '.gitignore'
# OUTPUT
./.gitignoreYou can see that we are using . here. If you wanted to start search from root you are free to pass / as you seach directory.
Did you notice that I kept on saying search for file or directories. By default find will try to match the option of -name on both directories and files. If you want to limit your search for file or directories you can use -type option.
find . -type d -name 'img'
# OUTPUT
./_site/img
./imgIf you pass d argument on -type option your search will limit to directories only.
find . -type f -name '.gitignore'
# OUTPUT
./.gitignoreIf you pass f argument on -type option your search will limit to files.
Linux system are case sensitive. What if you want to seach file ignoring the case. -iname can be use to do just that.
find . -iname '.gitignore'You can also search file with certain extention. Let's search file with .css extention
find . -type f -name '*.css'
# OUTPUT
./css/bootstrap-theme.css
./css/pygment_highlights.css
./css/main-minimal.css
./css/bootstrap.css
./css/bootstrap.min.css
./css/normalize.css
./css/bootstrap-theme.min.css
./css/main.cssWe can use * to indicate any character. We can also search files with multiple extention. Suppose you want to search file with .css and .html. You can do that with
find . -name '*.css' -or -name '*.html'
# OUTPUT
./_layouts/post.html
./_layouts/default.html
./_layouts/page.html
./_layouts/base.html
./index.html
./css/bootstrap-theme.css
./css/pygment_highlights.css
./css/main-minimal.css
./css/bootstrap.css
./css/bootstrap.min.css
./css/normalize.css
./css/bootstrap-theme.min.css
./css/main.cssNotice how we are joining the option -name in above syntax using -or. -or can be used with its alias -o You may have guessed that we can use -and too. Here's an example of find using -and.
# find . -name 'm*' -name '*.css'
find . -name 'm*' -and -name '*.css'
# OUTPUT
./_site/css/main-minimal.css
./_site/css/main.css
./css/main-minimal.css
./css/main.cssNow that you know about -or and -and, you may have imagined endless possibilities of search patterns. Just a quick note, if you use two -name without -and on above example it would act as -and. Quick hint !! you have -not option too. -not can be used with its alias !. -or , -and and -not can be used with other option too.
You can also control how deep you want to search usign -maxdepth
find . -maxdepth 1 -name '*.html'
# OUTPUT
./index.htmlYou can use find to search the files / directories based on modified, changed or accessed days and minutes.
For days you have -mtime, -atime, -ctime and for minutes you have -mmin, -amin, -cmin. Option prefixed with m denotes modified, a denotes accessed and c denotes changed.
find . -mtime 20
find . -atime 20
find . -ctime 20
find . -mmin 20
find . -amin 20
find . -cmin 20We can also use + and - symbol number provied. For example
find . -mtime +5Above command find the file which was not modified in last 5 days.
find . -mtime -5Above command find the file which was modified within last 5 days.
You can also go for range of days and minutes. Here's an example
find . -mtime +5 -mtime -10Above command finds the files / directories that are modifined between 5 to 10 days
find . -mmin +5 -mtime -10Above command finds the files / directories that are modifined between 5 to 10 minutes.
To search the file that has specific size you can use -size option
find . -type f -size 2MAbove command search file that has exactly 50M. We can also use + and - symbol on the number here. For example
find . -type f -size -2MThis command will find the files that has size of 2MB and less
For range you can do
find . -type f -size +2M -size -10MTo find empty file or directory you can use -empty option
find . -emptyfind also has option -user, -group and -perm which lets you search the file that is associated with specific user, group or if the file has certain permission.
You can also perform certain operation on the files / directories that are searched and found using -exec option.
For this example here is the list of files and dir that I have
-rw-rw-r-- 1 aman aman 0 Oct 7 10:30 four.html
-rw-rw-r-- 1 aman aman 0 Oct 7 10:30 one.txt
drwxrwxr-x 2 aman aman 4096 Oct 7 10:31 somedir
-rw-rw-r-- 1 aman aman 0 Oct 7 10:30 three.txt
-rw-rw-r-- 1 aman aman 0 Oct 7 10:30 two.php
To rename the two.php to two.html you can issue following command
find . -type f -name 'two.php' -exec mv -f {} two.html \;
# ls -l
-rw-rw-r-- 1 aman aman 0 Oct 7 10:30 four.html
-rw-rw-r-- 1 aman aman 0 Oct 7 10:30 one.txt
drwxrwxr-x 2 aman aman 4096 Oct 7 10:31 somedir
-rw-rw-r-- 1 aman aman 0 Oct 7 10:30 three.txt
-rw-rw-r-- 1 aman aman 0 Oct 7 10:30 two.htmlLet's explain what -exec is performing. After -exec we are writing the command that we want to execute. In our example we wanted to change two.php to two.html. Notice we are using {} placeholder in source section. To end the -exec command we are using \;.
I know on destination we used static text. What if we want to use change all html files to php now. Here's the command
find . -type f -name '*.html' -exec bash -c 'mv "$1" "${1%.html}".php' - {} \;Now that's a complex command. Let's me explain what's happening.
First we are passing bash -c '<command_to_execute_inside_bash>' - <param_to_send> on -exec. The command will execute for each entry that is found by find command. If find finds 5 files with *.html it will run the command 5 times.
Lets look at the command that we passed for execution i.e mv "$1" "${1%.html}".php.
$1 is the first argument that was passed to
command. For example if we have 2 file with html extention. It will send
1st file found to command as its 1st argument and command execution
will take place. Then, it goes for 2nd find found and will again pass
the file name as its 1st argument.So if we have two file one.html and two.html our find command will find the one.html first and it will execute our command which argument one.html. So on first execution $1 value will be one.html and on second execution $1 will be two.html
Next we have "${1%.html}".php. In a simple term if $1 represents one.html then "${1%.html}" will represent one. So "${1%.html}".php will represent one.php. Visit Bash Referrence Manural for more detail.
If we have two file one.html and two.html. When our command execute the first time ti will look like bash -c 'mv one.html one.php' and second time bash -c 'mv two.html two.php'.
Here's the output
-rw-rw-r-- 1 aman aman 0 Oct 7 10:30 four.php
-rw-rw-r-- 1 aman aman 0 Oct 7 10:30 one.txt
drwxrwxr-x 2 aman aman 4.0K Oct 7 10:31 somedir
-rw-rw-r-- 1 aman aman 0 Oct 7 10:30 three.txt
-rw-rw-r-- 1 aman aman 0 Oct 7 10:30 two.phpfind is very handy command and I hope this article helped you get an insight on how you can use find to search files and directories you need.
git config --global credential.helper cache
This caches the credentials for 15 minutes ( 900 seconds) by default. If you want a longer timeout period (say3600 seconds), you can do the following :
git config --global credential.helper 'cache --timeout=3600'