One Paragraph of project description goes here
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
Slack doesn't provide an easy way to extract custom emoji from a team. (Especially teams with thousands of custom emoji) This Gist walks you through a relatively simple approach to get your emoji out.
If you're an admin of your own team, you can get the list of emoji directly using this API: https://api.slack.com/methods/emoji.list. Once you have it, skip to Step 3
HOWEVER! This gist is intended for people who don't have admin access, nor access tokens for using that list.
Follow along...
// Run this in the F12 javascript console in chrome | |
// if a redirect happens, the page will pause | |
// this helps because chrome's network tab's | |
// "preserve log" seems to technically preserve the log | |
// but you can't actually LOOK at it... | |
// also the "replay xhr" feature does not work after reload | |
// even if you "preserve log". | |
window.addEventListener("beforeunload", function() { debugger; }, false) |
http { | |
log_format bodylog '$remote_addr - $remote_user [$time_local] ' | |
'"$request" $status $body_bytes_sent ' | |
'"$http_referer" "$http_user_agent" $request_time ' | |
'<"$request_body" >"$resp_body"'; | |
lua_need_request_body on; | |
set $resp_body ""; | |
body_filter_by_lua ' |
This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.
I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.
Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.
Install s3fs on Mac OS X | |
1 - Install Homebrew - http://brew.sh/ | |
ruby -e "$(curl -fsSL https://raw.github.com/Homebrew/homebrew/go/install)" | |
2 - Use Homebrew to install s3fs + dependencies | |
brew install s3fs | |
3 - Do some custom stuff. I only used the first step from here -> https://gist.github.com/fukayatsu/3910097 | |
sudo /bin/cp -rfX /usr/local/Cellar/fuse4x-kext/0.9.2/Library/Extensions/fuse4x.kext /Library/Extensions |
.search-bar-suggestions-dropdown-menu.dropdown-menu { | |
border-radius: 0; | |
border-width: 1px; | |
box-shadow: 0; | |
} | |
.search-bar-suggestions-dropdown-menu | |
.search-bar-suggestions-results-list | |
.dropdown-subheader { | |
color: var(--color-brand-primary); |
import com.liferay.mail.kernel.model.MailMessage; | |
import com.liferay.mail.kernel.service.MailServiceUtil; | |
import javax.mail.internet.InternetAddress; | |
MailMessage mailMessage = new MailMessage(); | |
mailMessage.setHTMLFormat(true); | |
mailMessage.setBody("set body here"); | |
mailMessage.setFrom(new InternetAddress("fromAddress","fromName")); |
package com.liferay.document.library.web.internal.frontend.data.set.view; | |
import com.liferay.frontend.data.set.view.FDSView; | |
import com.liferay.frontend.data.set.view.table.BaseTableFDSView; | |
import com.liferay.frontend.data.set.view.table.FDSTableSchema; | |
import com.liferay.frontend.data.set.view.table.FDSTableSchemaBuilder; | |
import com.liferay.frontend.data.set.view.table.FDSTableSchemaBuilderFactory; | |
import java.util.Locale; |