I have an account on an SMTP server. The server has a storage quota. I'd like the delete stuff from the server but keep it locally in case I need it. Just in case.

I'd like to be able to access the mail somehow on other computers and hopefully mobile devices on my network so that it can be searched when needed. I'm not sure what the best interface for that would be. A webmail client?

One option would be to use Thunderbird or another client to download the mail once in a while but disable deleting local messages when they are removed from the server. Would Thunderbird store the messages in a format I can use readily with other applications? Or should I use something else to download the mail?

What about situations where messages are moved from one folder to another on the server? Would I get a duplicate locally of the message appearing in both locations? Not sure how the storage and metadata actually are.

Also, is it possible in such a situation to put a message back on the server if I realize it was deleted in error?

Any idea would be welcome. I am a bit stuck.

I can use the command line comfortably but ideally I'd have a solution that doesn't rely on the terminal to find find messages and such. I don't really like terminal mail clients.

Since Geany 2.0 has recently been released I decided to switch back to it from Kate. I used to like Geany but it had some problems I couldn't quite remember.

So I quickly remembered the problem. I can't figure out how to configure it to properly comment and comment blocks of code. Say you have the following in a file of type shell script:

	# a comment
	echo $variable

I want to be able to select the above lines and use a keybinding to comment them out, so the result would be:

	## a comment
	#echo $variable

Edit > Format > Comment Lines works as anticipated.

But if I decide I want the lines back, how do that with the same keybinding? Using Comment Lines again adds a second level of comments, which is what I would expect (but not what I want):

	### a comment
	##echo $variable

Edit > Format > Toggle Line Commentation works and the file returns to the original state. But if you reselect the original lines and run it again, you get

	 a comment
	#echo $variable

Which would obviously lead to unpredictable results.

There doesn't seem to be a way for Geany to look at the block of text and decide whether it should be commented or uncommented and act accordingly.

Kate editor has this functionality in Selection > Toggle Comment as do other editors I've encountered. If there is a mix of commented and uncommented text, it will never remove comments. It only removes comments when the entire block has commenting, and then it removes only 1 level of comments. Perfect. Of course if you really want to force the matter, there are the more aggressive Comment and Uncomment.

Using the Geany Toggle Line Commentation leads to strange results, especially if you are starting with multiple levels of comments. Is there a way to duplicate the standard comment toggle in Geany? I tried to train myself to use Comment Line(s) and Uncomment Lines(s) instead of a single command but I just made a lot of mistakes where I didn't realize there were multiple levels of comments or whatever and things became uncommented that shouldn't have and it created a giant mess.

I'm not a professional IT person, just someone who enjoys text files in their spare time. I do a lot of commenting and uncommenting trying to find out how things work. I thought it was a pretty normal thing to do. There must be a way to do it right?

I recall digging around a bunch in the Geany repo/docs and it ended up that some problem I was having was a limitation of the Scintilla lexer and there wasn't much Geany could do about it. But I am not sure if it was this issue or something else.

about 50% content is like this, no matter what view you select. I think /r/pics has the right idea; it is so dominating. Other subs should change their post to be like this (with their own messages) I think.

Also, what sub did spez mod in 2008?

Submitted an hour ago by SarahAGilbert Moderator

A few days ago we shared a post outlining our thoughts around API uncertainty. The tldr: changes negatively impact our ability to moderate. These changes are part of a larger pattern in which Reddit’s leadership has failed to support what we believe is one of its greatest assets. Basically, our primary responsibility is making sure Reddit users are getting the best answers to your questions about history and Reddit is making that harder to do.

We understand Reddit’s need to change and evolve. For all we may harp on Reddit’s flaws, we do want to see it succeed! After all, we wouldn’t exist without it. So, if we’re expecting Reddit leadership to listen to us, we should be willing to work with them. In the days following the publication of the post, we discussed as a team what the specifics of working with Reddit would look like so we could clearly articulate it to you. We decided that compromise means:

• Updates to the API are not tied to a particular date but are, instead, rolled out once the roadmap shared here is successfully achieved.
• Accessibility tools such as screen readers are part of the native Reddit infrastructure.
• Updates are made across Android and iOS.

We think slowing down is the right thing to do. It would minimize further disruption while also generating an income stream for Reddit.

The AskHistorians’ mod team members are, functionally speaking, Reddit super-users. We have collectively invested thousands of hours into building our small corner of Reddit into a subreddit that is viable, trustworthy, and valuable, as well as something bigger. There’s our podcast, academic writing by us and about us, and our reputation as, "good history eggs on the internet." We’ve hosted two conferences, a long series of AMAs and presented about AH at other academic conferences. We even won an award! Major outlets have even covered our approach to moderation. We take all of this very seriously.

Nearly every time Reddit has asked for volunteers, we’ve stepped up. AH members help with the Moderator Reserves project, sit on council meetings and phone calls, host Reddit administrators who want to shadow moderators, and participate in surveys. Due to our commitment to the subreddit, we’ve built positive relationships with many admins who have been open to our feedback. But over the last couple of days—most notably during Spez’s AMA—it’s become clear to us that Reddit’s leadership is not interested in finding common ground; rather, it seems to us like they're hell-bent on pursuing a course that damages us and them alike.

We feel we are left with no choice but to join the protest. On June 12, starting at 7am ET, we will take our sub private. We will remain private on June 13 as well.

We’ll open the sub again on June 14th but will pause participation. This means you will be able to access existing content, such as the Trans History Megathread in Celebration of Pride Month, but will not be able to ask or answer questions. We will be delaying or holding off AMAs, limiting our newsletter, and will not be recording any new podcast episodes. As of today, we do not know how long this pause will last.

We cannot put this letter out into the world without thanking you for the immense support you’ve shown us over the last week. We’ve received support across platforms, in public and in private. We’ve been a community for nearly 12 years and that would not have happened without you and our other 1.8 million subscribers. We know we’re not the easiest community to post in, and deeply appreciate the people who ask dozens of thoughtful, rule-abiding questions every day, the people joining in on April Fools Day, those who anonymously report trolls and low effort answers, support the podcast via Patreon, and those who provide honest, thoughtful feedback on how we’re faring in general. We don’t take lightly the idea of shutting down this place and the community that we all build together, and we understand how frustrating it will be to not be able to find out, for example, why GPS is free.

We are all, at heart, historians. Studying the past requires a fair amount of optimism and confidence in humanity and as such, we are hopeful and confident a resolution can be found.